I left. The people were decent and the product fine, but my personal interest in the company went from "eh, sounds kind of interesting" to "why am I here...?" very quickly, and every day felt like an uphill battle to not rub my disinterest off on my coworkers. Looking for inspiration is a mind trap that is best avoided. Inspiration comes when you are silent and you listen to yourself (and those around you). Keep an o…
> I left. You know, this is one thing I need to learn: when to bail out on a situation that's beyond repair. I have a bit of a mental block about quitting without anything lined up, and job searching is just annoying enough for me to not want to do it without the incentive of needing to replace a paycheck. But, there are definitely a couple times in my career that I should have left long before I did, and I believe t…
Ask HN: What did you do to improve your company?
171–174 of 174 posts
Re: Ask HN: What did you do to improve your company?
#172Earlier quoted context omitted.
And I think getting to the end of the book, and seeing Pirsig descend into a pretty dark place in understanding quality being undefinable in any actionable way, I guess sometimes it's easier to just let go, and not understand something. A lot of times, understanding just makes us more miserable. Fantastic book, read it as a teenager and it deeply affected me.
A gross paraphrase I got was "I cant define quality, but I know it when I see it".
Re: Ask HN: What did you do to improve your company?
#173At one of my jobs, the very first thing I did when I arrived was redo the code deployment system to get the deploys from 30 minutes to 30 seconds. Cutting deployment time makes a huge impact because it makes everything go faster. You can iterate faster, which means getting bugs fixed faster, getting data to product managers faster, etc. It also has an effect on reliability. The faster you can make changes, the faster…
We have the exact same issue in my company. Could you explain how you managed this?
Re: Ask HN: What did you do to improve your company?
#174At one of my jobs, the very first thing I did when I arrived was redo the code deployment system to get the deploys from 30 minutes to 30 seconds. Cutting deployment time makes a huge impact because it makes everything go faster. You can iterate faster, which means getting bugs fixed faster, getting data to product managers faster, etc. It also has an effect on reliability. The faster you can make changes, the faster…
> At one of my jobs, the very first thing I did when I arrived was redo the code deployment system to get the deploys from 30 minutes to 30 seconds. We have the exact same issue in my company. Could you explain how you managed this?
If I had to do it today, I'd be looking at GitHub actions or some other similar CI/CD tool. If you're already using those, then I'd ask what is the slowest part of the process, and how can we speed it up?
To answer that question you obviously first need telemetry and monitoring to track each step of deployment. That telemetry will be useful in not only finding slow spots but tracking your improvement, which will help you both in operating as well as justifying your work to others.