Old Fucking Punk @lwriemen@librem.one

@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

I saw electrical engineers get replaced by CAD and outsourcing. The outsourcing was mostly skilled labor, because EE is a mature field; it is easy to judge skill level in mature fields due to more repeatability and established metrics. The CAD replaced the problematic and tedious area of board layout and the tedious area of schematic drawing. It also helped verification.
Software, OTOH, is mostly just outsourcing without a reduction in tedium or increase in automated verification. 1/n

It might be true that, "anyone can learn to code", but saying, "anyone can become a software developer", is an entirely different proposition. It's about time for the software world to adopt an attitude that software development is a profession that requires people with actual formal training and that such people have the same worth as other highly skilled fields.

Is contributing to FOSS projects the unpaid internship of the software world? Does throwing a minimum wage on it make it feel more professional or more like flipping burgers?

US militia group draws members from military and police, website leak shows https://www.theguardian.com/us-news/2021/mar/03/us-militia-membership-military-police-american-patriot-three-percenter-website-leak

The climate crisis can't be solved by carbon accounting tricks https://www.theguardian.com/commentisfree/2021/mar/03/climate-crisis-carbon-accounting-tricks-big-finance