• 0 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: January 31st, 2025

help-circle
  • As a senior developer, I use the new AIs. They’re absolutely amazing and a huge timesaver if you use them well. As with any powerful tool, it’s possible to over-use and under-use it, and not achieve those gains.

    However, I disagree with the comparison to knowing how hardware works. There’s a pretty big difference between these 2 things:

    Letting a company else design and maintain the hardware or a library and not understanding the internals yourself.

    Letting a someone/something design and implement a core part of your code that you are responsible for maintaining, and not understanding how it works yourself.

    I am not responsible for maintaining ReactJS or my Intel CPU. Not understanding it means there might be some performance lost.

    I am responsible for the product my company produces. All of our code needs to be understood in-house. You can outsource creation of it, or have an LLM do it, but the company needs to understand it internally.




  • Yes, you’re effectively renting a powerful computer.

    Previously, you could just use it without limits, and the math worked out for everyone. It’s something like 3-6 years of service to cover the cost of a decent-to-great computer.

    Now, if you’re a hardcore gamer and go over 100 hours a month, that value changes, and the break-even point is sooner. If you play for 40 hours a week, that time is effectively halved.

    At the current rates, it continues to seem like a really good value, so long as you aren’t bothered by the slight input lag or the video compression.

    But if more people use the service for more time, they’re going to have to charge more money. Either higher base rates, or lower limits. And it’s eventually going to show that it doesn’t really make sense for anyone except as a temporary measure, and then the service will disappear because it didn’t work well enough.







  • That sounds like pretty much exactly what we did at my last job, and it worked pretty well IMO. The individual commits in a PR didn’t ever matter. I don’t even think we used them for code review, except if it came up for review a second time after rework. In that case, we were able to just look at the new commit to see if the right changes were made.

    And we definitely avoided basing off each other’s branches. We had to do it a few times. The only times it went well was when the intent was to merge the child branch into the feature branch. If they were actually separate tickets (and the second relied on the first) it was generally chaotic. But sometimes, it was just necessary.


  • Having a dream isn’t wrong, but every business is difficult, and this one is already being run under by cheap Chinese prints.

    It’s still possible, but all the success I hear now is from people who have designed their own product and are fulfilling specific needs, like adapters for certain tools and such.

    Etsy also just banned 3d prints of other people’s design, so it’s even harder to make money with those now.

    You can still make money with your own designs on Etsy, and direct to people who need things, but now it’s as much about the design of the items as the printing of them.

    I suppose selling at a local market can still work, too, but it’s a huge time sink. (Like any other job, I guess.)