llamataboot
Joined 13 years ago
Karma
7,546
Submissions
1,212
Member since
Jun 8
Recent submissions
Comment · 1 month ago
Location: US
Remote: Preferred
Willing to relocate: Possibly
FT?: Open to FTE for right opportunity, but prefer contracts (PT/FT flexible)
Technologies: Ruby/Rails, Python, Ops (Heroku/AWS/Docker), CI/CD, API Design, System Architecture, thoughtful experimentation with llm ops and visibility and steering. Some: React, IoT, bit of elm, ML
Email: [email protected] 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 leading 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!)
Comment · 6 months ago
A persistent bias in prediction markets is pricing very non likely events as slightly more likely than they are. ie; a 1% event priced at 4%, etc, because people like to bet long shots.
Whether there is enough of a predictable bias there to snag enough low return high probability bets to beat the vig and not shift the markets I have not looked into in any way,but it is a known bias with them.
The real money to be made in prediction markets is being the ones with the actual knowledge which is arguably why they are useful and why for some topics, people find them abhorrent.
Comment · 1 year ago
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.
Email: [email protected] 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!)
Comment · 1 year ago
right it was the python string transition i was talking about
Comment · 1 year ago
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
Comment · 1 year ago
just dont ask about unicode
Comment · 1 year ago
We learned nothing from Python 2->3
An obviously good change, actually massive performance improvements not hard to implement but its still gonna be such a headache and dependency hell
Comment · 1 year ago
Location: US
Remote: Preferred
Willing to relocate: No
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.
Email: [email protected] Website: https://ericstiens.dev Resume: https://cloud.wonderluxhouse.xyz/f/fd98d4cbdc104e3d8151/
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!)
Comment · 1 year ago
Location: US
Remote: Preferred
Willing to relocate: No
FT?: Open to FTE for right opportunity, very open to contracts, especially if they can fluctuate between PT/FT, or are contract to hire.
Technologies: Ruby, Rails, Ops (heroku/aws/ansible/docker), CI/CD, testing, API design, integrations/plumbing.
Some: Python, Elm, IoT stuff, machine learning Love: architecture, mentoring, useful and absurd experimentation
Email: [email protected]
Website: https://ericstiens.dev
Resume: https://cloud.wonderluxhouse.xyz/f/fd98d4cbdc104e3d8151/
--
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.
social researcher and social worker turned coder -- interested in systems science, social justice, heterodox economics, non-hierarchical decision making, game theory, poker, soccer, theories of consciousness, and magic