4,566 karma · joined August 27, 2014
Into woodworking and a (new) homelab.
jameshtimmins {at} gmail
So while going through Rust by Example, I'll paste programs into ChatGPT and have a conversation with it about how specific pieces work. I've also done LeetCode problems and then asked ChatGPT for feedback about my approach.
Unfortunately a lot of folks get promoted into management w/out skills/training, so engineers think all managers are bad. Which is understandable.
But a great manager is a huge value add who will give you what you need to succeed, help you grow, and keep politics from throwing things off track. Once you have a great manager, it's easy to see how valuable they an be.
I own several of his books (admittedly they were gifts), and have never read them. So them not showing up in the top five doesn't surprise me much.
I'd love a book on "Web Authentication Systems" that is a survey of approaches, real world examples, tradeoffs of different frameworks, core principles, etc.
Which is ... really something. https://en.wikipedia.org/wiki/List_of_unusual_deaths
1. For anyone who uses X for more than a few hours per month, a low fee is totally worthwhile.
2. This is a huge gamble that has the potential to wreck the company.
Project looks rad too, but I'm just here to appreciatively bike shed.
People who have been especially successful in their careers as e.g. software engineers, is this also a good path?
Email: jameshtimmins @ Google's email service
I'm a senior Python engineer and developer marketing content writer for data and infra companies. Most recently I wrote this piece on building an outbound email pipeline with Dagster https://dagster.io/blog/outbound-reporting-pipeline.
Remote: Yes. Hybrid or on site for the right role.
Willing to relocate: No
Technologies: Django/FastAPI/Flask, Python, React, Airflow, Postgres, Docker, Kubernetes, AWS, Redis
Résumé/CV: https://docs.google.com/document/d/1igralyB4mxyRuBfLvBNXziyW...
LinkedIn: https://www.linkedin.com/in/james-timmins/
Email: jameshtimmins @ Google's email service.
Senior backend/fullstack developer w 8.5 years experience building distributed backends, internal tooling, and as an Apache Airflow maintainer/committer. Most recently worked as a backend engineer building a highly scalable Airflow SaaS service. Especially interested in alternative data providers, fintech, enterprise integrations, but mostly care about the team and working on hard problems.
Where was this?
Contrast with my bro who studied ME where they had a toy robot competition in the first month.
Really excellent read. Very amusing to see his analysis of Apple and Microsoft, which seemed basically accurate until the iPhone came out.
"How to design good software" is a huge question, but "what are some mistakes you've seen with tool X" seems like a great way to catalogue common errors that people make while learning.
I'd love for a major framework/tool to poll its users and create an index of common design counterexamples. e.g. "common design mistakes with serializers, models, caching, etc".
+1 if that resource included ways to refactor away from the bad design. So if the counterexample is "Querying the database directly from the controller functions", there could be a list of ways to refactor a codebase away from that design in pieces, and what to consider at each step (since some problems aren't worth the effort of fixing).
I've tried the using OpenAI w embeddings (iirc), but this was slow, got expensive quickly, and it struggled to answer questions about the text accurately. Curious if there's better standard approaches now.