6 ms·

Navigating a Broken Dev Culture

60 points by lightserver 2y ago

My Current Job is a Mess—But I Won’t Let It Define Me (Disclaimer: Not here to trash my company, just sharing my experience.) I work on the AI team at my current job, meaning I get to play with cutting-edge generative AI tech. I’ve built some pretty cool things: • Designed an end-to-end image generation pipeline for a virtual friend app. • Implemented self-hosted Stable Diffusion with Automatic1111, adding sentiment-based image optimization & image retrieval. • Used Vicuna (uncensored) + VLLM for serving our text model. Sounds exciting, right? That’s about where the good part ends. The Bad: A Tech Culture Stuck in the Stone Age The engineering practices at my company are, to put it mildly, nonexistent: • Testing? None. Even revenue-generating products (~$200K/yr) are tested manually. • Deployments? Manual SSH into the server, copy the build, and pray. • CI/CD? What’s that? • Docker/Kubernetes? Not in our vocabulary. • Code Quality? Negative. I’ve tried pushing for better practices—heck, I even gave a Docker session to the team—but there’s no buy-in. The New Obsession: AI is Eating Our Jobs Management (none of whom are engineers) has fully bought into the “AI replaces devs” hype. Our CTO literally said: “Use GPT to write code. This is a one-day task; it shouldn’t take more than that.” They genuinely believe AI can replace skilled developers overnight. Meanwhile, they’ve never used GPT to write production code themselves. They just read the PR spin and assume it’s magic. Despite this chaos, I’ve refused to let the environment affect my growth. WFH helped me stay sane, but now that we’re back in the office, I know it’s time to move on. I never had a formal AI background, but I self-learned everything while on the job. Along the way: • Cleared GSoC and worked on Intel’s ML toolkit OpenVINO (JS bindings). • Discovered OpenTensor (decentralized intelligence), cold-emailed a contributor, and worked part-time on his startup. • Got my Rust PR accepted into Docify (used by Polkadot). • Built a Rust + HTMX startup backend using Rocket (signed an NDA, so can’t share details). What’s Next? I’m scrambling to find a new job. Ideally, I’d love to work on FOSS full-time rather than jumping into another corporate dev job. The problem? Finding an opportunity that matches my current compensation in India. I recently worked a contract gig for $17.35/hr—if I had a year-long commitment at that rate, I’d have left my job yesterday. I know going full-time into FOSS isn’t easy, but if you have advice—or know FOSS projects that need contributors—I’d love to connect. My stack: • Frontend: React / Next.js / TypeScript • Backend: Node.js / FastAPI / Flask • GenAI: LangChain, RAG, Stable Diffusion, Tool-Calling • DevOps: (Self-learning) I’m in a phase where I can afford to push myself to maximize my learning, but I also need to be practical. If you’ve been through something similar or have insights on making a sustainable career in FOSS, I’d love to hear from you. Thanks for reading—I appreciate any thoughts, advice, or connections!

francisofascii 2y ago
What made management decide to move back to the office?
- lightserver 2y ago
  no clear communication on that , but the back to office mail contained usual points like , collaboration is better in person etc etc , and that we're targeting to achieve big things in this AI wave so we all need to work togther and hence back to office lol ://
jonfw 2y ago
One thing I didn’t notice- what impact to the bottom line does kubernetes or docker bring? I love shiny tools and containers as much as anybody, but “this thing is shiny and new age” isn’t a great pitch. Your team needs to have problems that kubernetes can solve. If you don’t spend that much time on deployments, if outages don’t cost you much money- it is probably not worth it. When I hear 200/k a year as revenue generating- I hear that this is something that should be limped along as cheap as possible, not that this is something that should be invested into and modernized.
- the__alchemist 2y ago
  I had the same reaction. I would look more favorably on a company that doesn't use Docker or Kubernetes. These tools, by default make things complicated and slower, so there needs to be a positive benefit for their use case that balances this. It makes me wonder whether OP's desired for testing and CI is for a specific reason, (e.g. targeted test on certain algorithms, CI/CD to replace manual QC steps etc), or if it's for less-practical reasons.
  - sepositus 2y ago
    > These tools, by default make things complicated and slower, so there needs to be a positive benefit for their use case that balances this. I'm confused by this reasoning. How does Docker make things slower by default? Why would you look favorably on a company that doesn't use it? make scp mybin machine@foo.com/deploy ssh machine@foo.com -c 'systemctl restart myservice' Or docker build docker push myimage@latest ssh machine@foo.com -c 'docker-compose up' At least with the second one, you have automatic artifact tracking for easier rollbacks.

60 points by lightserver 2y ago

francisofascii 2y ago

What made management decide to move back to the office?

lightserver 2y ago
no clear communication on that , but the back to office mail contained usual points like , collaboration is better in person etc etc , and that we're targeting to achieve big things in this AI wave so we all need to work togther and hence back to office lol ://

jonfw 2y ago

One thing I didn’t notice- what impact to the bottom line does kubernetes or docker bring? I love shiny tools and containers as much as anybody, but “this thing is shiny and new age” isn’t a great pitch. Your team needs to have problems that kubernetes can solve. If you don’t spend that much time on deployments, if outages don’t cost you much money- it is probably not worth it. When I hear 200/k a year as revenue generating- I hear that this is something that should be limped along as cheap as possible, not that this is something that should be invested into and modernized.

the__alchemist 2y ago
I had the same reaction. I would look more favorably on a company that doesn't use Docker or Kubernetes. These tools, by default make things complicated and slower, so there needs to be a positive benefit for their use case that balances this. It makes me wonder whether OP's desired for testing and CI is for a specific reason, (e.g. targeted test on certain algorithms, CI/CD to replace manual QC steps etc), or if it's for less-practical reasons.
- sepositus 2y ago
  > These tools, by default make things complicated and slower, so there needs to be a positive benefit for their use case that balances this. I'm confused by this reasoning. How does Docker make things slower by default? Why would you look favorably on a company that doesn't use it? make scp mybin machine@foo.com/deploy ssh machine@foo.com -c 'systemctl restart myservice' Or docker build docker push myimage@latest ssh machine@foo.com -c 'docker-compose up' At least with the second one, you have automatic artifact tracking for easier rollbacks.