If you need 70 hours to do what others are doing in 40-50 hours, you need to git good.
If you feel your employees should work 70 hours to produce meaningful impact as a team (maybe because your team is lagging behind competition), you might have failed as a founder and built a weak team. You need to git good.
Change my mind.
When build time takes more than 2+ hour to build, you didn't do git (ops) good.
When your dont have testcases in your SDLC and production fails, you didn't do git good.
When you send a PR with a large number of file changes, you didn't do git good.
Software engineering is full of such meaningless pain and misery. Time to revolt.
Recently the CHRO of my company called me into a discussion on improving WORK LIFE BALANCE. Wow. I just cannot understand. Look at this.
I'm surprised to see on the comment section that people actually support this load of crap.
To any newbies or freshers entering tech this year, don't follow this advice. These CEOs exploit your time to gain revenue and when the time is...
Let me explain, managers or senior folks who reply/slack/email or do any form of communication outside working hours and especially over weekends… I hate it. If u do it without the counter party explicitly expressing such urgency then yo...
Haan toh bhai tu mat kar They reply at a time that works for them- you set the right expectations for yourself. Unk...
He's a founder and possibly gets salary and stock dividends in millions of dollars every month. He can most certainly...
