Location: US
Remote: Preferred
Willing to relocate: Possibly
FT?: Open to FTE for right opportunity, but prefer contracts (PT/FT flexible, C2H)
Technologies: Ruby/Rails, Python, Ops (Heroku/AWS/Docker), CI/CD, API Design, System Architecture, thoughtful experimentation. Some: React, IoT, bit o elm, ML, LLM ops and automation.
Senior/Staff Engineer with a deep focus on backend, ops, and architecture. Can also get in there and knock out frontend features if nec, but don't prefer architechting there. I build durable, scalable systems and have a knack for mentoring teams and leading projects.
I solve problems at every level of abstraction—from the 10,000-foot view down to the code you don't have to write. My first career as a social worker and policy statistician means I never forget the 'who' and 'why' behind the technology. I've been building for the web since '95 and have worked at every stage of startup, plus solo consulting.
I have a special love for complex system design, wrangling crappy third-party APIs, and hunting down really weird bugs. I can step in as a PM in a pinch, but I'd rather work with your great PMs.
Also open to short-term engagements around a specific issue (performance bottlenecks, test suite optimization, a particular stuck feature, etc) at a weekly rate.
I'm looking for a team that genuinely believes their work is making the world a bit better (or even... a lot!)
Only if you count 1.9.2 as the beginning. What is being talked about is Unicode by default and maybe Unicode tooling (i.e. can correctly iterate over emojis and not just bytes)
Ruby has been extremely slow and deliberate in rolling out frozen string literals. They added a magic comment to opt in to them on a per-file basis all the way back in Ruby 2.3—almost a decade ago.
Most linting setups I've seen since then have required this line. I don’t expect many libraries to run afoul of this, and this warning setting will make finding them easy and safe. This will be nothing like the headache Python users faced transitioning to 3.
I hope this is corect - i do agree it has been a long and slow migration path and migrating is fairly easy - migrating python 2 to 3 code was fairly easy as well anyone could do it in their codebase, it remains a big deal and possibly very impactful to make such breaking changes to the behavior of primitives in mature ecosystems. How many gems does the average rails app have, okay they all need to be updated and they sohld be being updated for other reasons, I remain skeptical of how smooth the change is going to be over all ecosystem wise but time will tell.
I agree it has been a well advertised and loudly migration path and timeframe for it
Most of the problems in Python 3 were the string encoding changes. It was very pervasive, fixing things was often not so straight-forward, and writing programs that worked well with Python 2 and 3 was possible but somewhat difficult and error-prone.
The rest of the changes were a bit annoying but mostly boring; some things could have been done better here too, but the string encoding thing was the main issue that caused people to hold on to Python 2 for a long time.
The frozen string literal changes are nothing like it. It's been "good practise" to do this for years, on errors fixing things is trivial, there is a long migration path, and AFAIK there are no plans to remove "frozen_string_literal: false". It's just a change in the default from false to true, not a change in features.
"Learning lessons" doesn't mean "never do anything like this ever again". You're the one who failed to learn from Python 3, by simply saying "language change bad" without deeper understanding of what went wrong with Python 3, and how to do things better. Other languages like Go also make incompatible changes to the language, but do so in a way that learned the lessons from Python 3 (which is why you're not seeing people complain about it).
??? This is nothing like the Python transition. In Python there were two incompatible language versions side by side for years that made it really hard on library maintainers. Ruby is giving a 7-8 year transition period before this even hits, with years of warnings built-in to the plan. What more would you have them do?
Not to mention that in addition to the opt-in warning that came with 3.4, if you've been using any reasonable linter such as Rubocop for the past 10ish years then you're already being yelled at for lack of `# frozen_string_literal: true` magic comment.
Even if you have an incompatible codebase that you don't wish to convert, you'll be able to set `RUBYOPT="--disable-frozen-string-literal"` so it keeps running.
And since that flag really doesn't require lots of work in the VM, it's likely to be kept around pretty much forever.
FT?: Open to FTE, but prefer contracts (PT/FT flexible, C2H)
Technologies: Ruby on Rails, Python, Ops (Heroku/AWS/Docker), CI/CD, API Design, System Architecture, thoughtful experimentation. Some: React, IoT, bit o elm, ML, LLM ops and auotmation.
Senior/Staff Engineer with a deep focus on backend, ops, and architecture. I build durable, scalable systems and have a knack for mentoring teams and leading projects.
I solve problems at every level of abstraction—from the 10,000-foot view down to the code you don't have to write. My first career as a social worker and policy statistician means I never forget the 'who' and 'why' behind the technology. I've been building for the web since '95 and have worked at every stage of startup, plus solo consulting.
I have a special love for complex system design, wrangling crappy third-party APIs, and hunting down really weird bugs. I can step in as a PM in a pinch, but I'd rather work with your great PMs.
I'm looking for a team that genuinely believes their work is making the world a bit better (or even... a lot!)
Senior/Staff full-stack dev (lean more towards devops->backend than backend->frontend, but I can still sling some React components together and reduce your JS payload size). Technical Lead.
I excel at figuring out how to solve problems at all levels of abstraction (including what level of abstraction you should use), getting a solution in place, and then figuring out the feedback loops to iterate on that solution. Sometimes the most impactful code is the code you don't write.
I've been programming on the web since 1995, had a first career as a social worker and policy statistician, and have worked full-time as a coder for almost a decade now at all stages of startup as well as done solo consulting.
Especially enjoy API and system design, integrating with crappy systems, user research, and really weird bugs. Make a decent PM in a pinch, but would prefer you have great PMs. Enjoy mentoring and light mgr/people stuff.
Will give you more looks if you can tell me why what you are doing makes the world better, but you've got to really believe it.
Full on musk junta coup huh? Didnt have that on my bingo card exactly. Guess we'll really get to see if theres any rule of law in the US anymore or if its all completely as hollow as its looked for a long time.
I wish they picked different descriptors than various ox with turbo mini preview etc and some of them shockingly different (o1 preview versus o1 regular for example) just give us three or four buckets of combos of cheap and fast and good :p it’s to the point where I have to look up prices and abilities and decide on a model for every use case and realize I made a mistake in the one I was using the day before.
Senior/Staff full-stack dev (lean more towards devops->backend than backend->frontend, but I can still sling some React components together and reduce your JS payload size). Technical Lead.
I excel at figuring out how to solve problems at all levels of abstraction (including what level of abstraction you should use), getting a solution in place, and then figuring out the feedback loops to iterate on that solution. Sometimes the most impactful code is the code you don't write.
I've been programming on the web since 1995, had a first career as a social worker and policy statistician, and have worked full-time as a coder for almost a decade now at all stages of startup as well as done solo consulting.
Especially enjoy API and system design, integrating with crappy systems, user research, and really weird bugs. Make a decent PM in a pinch, but would prefer you have great PMs. Enjoy mentoring and light mgr/people stuff.
Will give you more looks if you can tell me why what you are doing makes the world better, but you've got to really believe it.
Disappointed they didn't even mention intentional data poisoning - we simply have no idea what trapdoors are being laid in training data yet to be ingested...
FT?: Open to FTE for right opportunity, but prefer contracts (PT/FT flexible, C2H)
Technologies: Ruby/Rails, Python, Ops (Heroku/AWS/Docker), CI/CD, API Design, System Architecture, thoughtful experimentation. Some: React, IoT, bit o elm, ML, LLM ops and automation.
Email: hello_from_hn@ericstiens.dev Website: https://ericstiens.dev Resume: https://cloud.wonderluxhouse.xyz/f/fd98d4cbdc104e3d8151/
Senior/Staff Engineer with a deep focus on backend, ops, and architecture. Can also get in there and knock out frontend features if nec, but don't prefer architechting there. I build durable, scalable systems and have a knack for mentoring teams and leading projects.
I solve problems at every level of abstraction—from the 10,000-foot view down to the code you don't have to write. My first career as a social worker and policy statistician means I never forget the 'who' and 'why' behind the technology. I've been building for the web since '95 and have worked at every stage of startup, plus solo consulting.
I have a special love for complex system design, wrangling crappy third-party APIs, and hunting down really weird bugs. I can step in as a PM in a pinch, but I'd rather work with your great PMs.
Also open to short-term engagements around a specific issue (performance bottlenecks, test suite optimization, a particular stuck feature, etc) at a weekly rate.
I'm looking for a team that genuinely believes their work is making the world a bit better (or even... a lot!)