Any pronouns. 33.

Professional developer and amateur gardener located near Atlanta, GA in the USA.

I’m using a new phone keyboard, please forgive typos.

  • 22 Posts
  • 3.21K Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle

  • Assuming this is a real post and not satire, my best guess is that they don’t think it’s a bottleneck, but still believe a way to talk to the computer without disturbing others in the office is useful. Like if Tide detergent said it would save your marriage – they don’t think it really will, but the ad is humourous and likely to gain attention because of it.


  • If you’re still in college, try to get an internship. Once you have something on your resume, it’s a lot easier to get into places. Plus try to network and stuff. Getting recommended by someone is much more likely to result in an interview.

    The AI shit is really rocking the boat right now, but ultimately I don’t think it’s sustainable. I don’t know what the future of dev work will look like or when it’ll balance out, but right now, these AI agents are effectively heavily subsidized by investors. At some point, they’ll need to either turn to the public (IPO) as a last resort, or actually begin to turn a profit. I think this happened with Microsoft’s Copilot. “Tokenpocalypse” was the term that got thrown around. They can’t undercharge for this stuff forever.

    Even if AI does end up being a significant part of work, actually knowing how to code will make you better at using it. Your skills aren’t useless. You’ll be better at noticing when the agents make shitty code or shitty decisions. If agentic development ends up being too costly for everyday use, you’ll still be able to assist with “manual” code writing.

    AI companies over hype their products and say they’re world shattering as a way of marketing. They say the idea of developers are over because they want people to invest and buy their product. Agentic coding has gotten pretty fucking impressive in the past few months, but something’s gonna break at some point. The bill always comes due.

    But yeah. Internship and networking. Learn AI, but don’t eschew traditional development practices entirely.





  • Extremely good insulation, possibly building things underground, and then air conditioning. You said people with health issues. If you need to make sure something is a a specific temperature because of health concerns, you need air conditioning to be certain. Really making sure you’ve got incredible insulation is really all you can do. Tall trees that block the sun around the building can help. Using blinds and curtains as well instead of letting the sun in.









  • I don’t know, the number of times I’ve needed to make two small changes in parallel is certainly non zero. The amount of times I’ve been mostly done with a feature and began a new one before a PR was totally merged is certainly non zero. Even then, some changes can make more sense if broken it into multiple commits (a moot point at most teams since squash and rebase seems to be the norm). You can keep a linear history and still have multiple commits in a branch, just commit (har har) to reading instead of merging.

    Regardless, doing commit fixups and rewords are not necessarily rare. These commands are still super useful. Bear in mind that just because something isn’t useful to your workflow, git is used by many different people with many different types of workflows.