Old Fucking Punk @lwriemen@librem.one

Oh goody! My favorite job, replacing a garage door spring. [sic] #fml

I was a little disappointed in the chapter on technical work in Sarah Jaffe's book, Work Won't Love You Back, because it focused too tightly on Silicon Valley and game development. The things she described aren't wholly unique to the game industry, but it kind of sounded that way. She did a good study on how the software industry abuses youthful enthusiasm, and her treatment of burnout, ego, and mistaking software dev for art was spot on.

Don't let the right-wing fucknuts take Viking history or Norse gods away from you. They also don't own the "Don't tread on me" flag. We know they're bullies that run in the face of stuff opposition, so stand up and show them how small of a minority they are! #NaziPunksFuckOff

@vandys @fribbledom Sounds like a culture of fear. Everyone should be engaged in delivering quality code. The only reason to avoid good reviewers/testers (those who find issues) is when people get penalized for schedule slippage

@TheConstructor @fribbledom if you're reviewing after tests have been written, you're reducing your productivity based on most of the peer review research I've read. If you're doing test first, then the tests should be reviewed before the code is written. The up front test writing takes the place of requirements analysis, so the tests might contain many wrong assumptions that could lead to a bad design.

@fribbledom Once the requirement analysis review and solution design review is done, the implementation review is just a matter of review the application of implementation language against the solution design. If both reviewer and coder are at the same fluency level with respect to the implementation language, then the code review will be roughly the same time as implementation. (typing vs reading speed.) A discrepancy in knowledge/assumptions at any stage skews things.

@kyle You made it a lot further than I did.

Forget 5 an Hour — the Minimum Wage Should Be 4 https://theintercept.com/2021/03/05/minimum-wage-raise-15/

No, Dr Seuss and Mr Potato Head haven't been 'cancelled'. Here's the difference https://www.theguardian.com/commentisfree/2021/mar/06/dr-seuss-mr-potato-head-cancel-culture

However, you can't prove or disprove a hypothesis with no metrics, so anecdote becomes the metric; this causes people to complain about "big design up front" and "abstraction", both of which are productivity and quality enhancers when done right, but popular hypothesis of how to do both have led to an aversion of both.

The software world needs to start maturing before we have a real software crisis. #immatureSoftware

This has resulted in a reduction in reliability, because software isn't a mature field. While an EE level of CAD (automation) exists, it is little used. While metrics exist, they are little used. Repeatability is not considered a desirable trait. Untrained practitioners learn by development of small systems, and best practices in such development do not lead to best practices in the development of large systems. Some of this is the fault of bad hypothesis treated as theory. 2/n