A better expression of this idea is, "No zero days." Do something every day. Maybe it's getting up on time. Maybe it's exercise. Maybe it's a bug fix.
WTF, zero days are the best days.
Ship Something Every Day
101–110 of 134 posts
Re: Ship Something Every Day
#102Spell it with me team B U R N O U T
Totally. Some of us can't afford to stop working for a year or two or however long it takes to properly deal with burnout, so we need metods like this to keep our families from going hungry.
Re: Ship Something Every Day
#103Earlier quoted context omitted.
Do I care? No Does my manager? No, but what if they leave and I have a new manager right before performance reviews? I’d hope they don’t care about it, but I assume they’ll see it. May as well make it look nice. Does the random recruiter looking at your resume care? At some point in your career you might be able to afford to not care about this. Most people don’t have that luxury.
If people invested as much time improving their abilities as they did gaming the system, they might find the problem solves itself.
Right - you fail at leetcode interviews despite your high abilities, and leave programming behind in anger to become a gardener.
Re: Ship Something Every Day
#104Alternative title: Train Yourself To Only Work On Low Hanging Fruits
Re: Ship Something Every Day
#105Or don't. The older I get, the more I find the obsession with work and hyper productivity to be pointless. This might be good advice for young people starting their careers, but even then I would advise prioritizing real life goals over work. Don't buy into the entrepreneur ideals you see on social media. People can be successful without working all day, everyday. Take rests, prioritize your health, and enjoy life fi…
This reflects my own changes. Me at 25 and me at 35 are completely different when it comes to code. I'd rather finish early, spend time with family, and come back tomorrow with a better solution than keep on hammering away on an overnighter to try and hit some arbitrary metric.
Re: Ship Something Every Day
#106Our customers want release notes and time to test features so we have a monthly cadence.
Re: Ship Something Every Day
#107Earlier quoted context omitted.
> This has nothing to do with streaks or dopamine rushes or pleasing managers. This is about getting stuff done. To me, a developer who can't figure out ways to be productive by contributing tiny commits spread over time is a developer who is wasting space in a team. This totally discounts any work that does not result in commits, such as requirements analysis, legacy code analysis, or code that results in insights b…
> This totally discounts any work that does not result in commits, such as requirements analysis, legacy code analysis, or code that results in insights but won't be merged. I don't think it does. My point was not "do this OR that". My point is that posting a commit a day is a goal that's easily achieved if you do professional work. The work it takes you to fix a typo or add a commit is not something you need to plan…
What's the point of having such a goal? Seems like additional overhead if you need to remember and go out of your way to do such a trivial commit.
Re: Ship Something Every Day
#108Our team is slowing down instead. The quality of the code has become so poor, full of bugs and what not, that we have decided to slow down and instead invest in quality. We currently spend so much time fixing bugs and refactoring spaghetti code to shoehorn the next shiny new feature, that the amount of actually useful features we deliver has decreased. Half-assed features which work on paper but totally unusable for users because we're still at MVP where nothing really works but the PM is happy because he can report to CEO we shipped another cool feature. It's actually quite demotivating to learn that no user actually uses the feature you developed because it's total crap. Yes, we shipped often, but we shipped crap.
Now we focus on writing more tests and doing more design reviews.
Re: Ship Something Every Day
#109IMHO "every day" is far too frequent, and this ADHD-ish attitude is one of the reasons why the quality of average software has gone down the drain. Developers need to step back, think more deeply, and not worry about being pressured into "shipping code" that barely works. The dopamine rush of your code being shipped This frequent overstimulation leads to less ability for long-term attention. When I taught programming…
> Optimising for metrics never works for those who can see through the illusion, and that's an increasing number of people over time.
Adorable.
Re: Ship Something Every Day
#110|> Your team (and manager) sees you're working That's one of the greatest corporate flaws and my biggest personal failure that I fail, and refuse, to adapt to. When I work in a team I often try to empower lacking teammates by taking a challanging task, do most of the hard work, and give it to somebody else to finish up the easy part and ship the solution. While working on it they have to understand how the solution a…
this comment resonates with me. I think it’s a common mistake for a lot of folks to forget that programming is a creative task, and creative tasks rarely fit into metrics effectively. I have a bad habit at my place of work for not ticketing things out correctly and pushing larger than average commits.
At one point I just realized that the work in BigCo has very little to do with actual value, and much more politics and PR.
In my last workplace we had two teams working on almost identical applications - large, multistage web forms for insurance. At that time it was a common practice at the office to estimate in units of time. One team was constantly commiting sprints to 300 units and delivering 200, and the other was commiting to 100 and delivering 150. First was quickly disbanded and fired, and the latter was praised for performing beyond expecations.