> I’ve experienced that great feeling of “this is a great idea” coming out of nowhere while doing unrelated activities, and having to rush back at my desk to write it down and implement it. That was great - it was rewarding, it was really meaningful.
This is it for me. It’s a pretty incredible tool but it killed the vibe and challenge of building things.
Getting something 36 minutes after ordering it is a nice surprise and great customer experience. I’m usually happy with a day or two.
After spending close to 6 months and countless phone calls trying to get a refund processed the bad experience is outweighing the good for me.
The entire experience on the unhappy path is so obnoxiously dreadful i don’t purchase anything on Amazon over an amount I’d be fine just losing. Even though 99% of my orders have been absolutely fine.
I wish there was a jobs board for companies that are somehow vetted for this type of engineering culture.
So many jobs are sold as “we’re pragmatist's” and when you show up there’s 5 devs, 50 repos and most of the work is discussing if x requirement should be a new micro service. The product is usually an web app with 10 entities and and an API.
There is, it's java/ruby shops. No one wants to use that stuff in current year, so if they're using it anyway, they're pretty likely to be boring tech users.
Yeah I don't see the big deal here. Some of the best software is made and maintained by a very small group of dedicated folks. It's a perfectly reasonable move to protect their time and project.
reply