Crev is a scalable, social, distributed Code Review and recommendation system that we desperately need for establishing trust in Open Source code.

Getting started: https://web.crev.dev/rust-reviews/your_personal_reviews/

The project is not maintained anymore though.

The Open Source ideology is misused by companies: its ideology concerns production (similarly to FLOSS). You contribute to the software back.

Copyleft can force an absolute minimal “contribution” back to your project, but it can’t force a good-faith one. This makes it an inadequate tool towards building something with the kinds of values that many developers care about.

But I do think I’ve properly identified the problem: many developers conceive of software freedom as something larger than purely a license that kinds in on redistribution. This is the new frontier for those who are thinking about furthering the goals of the free software and open source movements. Our old tools are inadequate, and I’m not sure that the needed replacements work, or even exist.

The downside of AI for programming:

• Erosion of Core Programming Skills
• Over-Reliance on Auto-Generated Code
• Lack of Ownership and Responsibility
• Reduced Learning Opportunities
• Narrowed Creative Thinking
• Dependency on Proprietary Tools
• false sense of expertise

For simple sites, keep things manual.

Automate when it hurts to do it manually.

The comparison are pertinent. It compares the following topics:

• Gender
• Creativity
• Sustainability
• Trends

Good code is code that’s fast to work with.

• text editor
• 2D game
• compiler - tiny Basic
• Mini Operating system
• Spreadsheet
• Video game console emulator

Insight 1: trust
Insight 2: loneliness
Insight 3: finances with big peaks and a couple of month of a lull

Developers are not happy with their job.

Programming is not the problem though (64% does it afterwork).

Moreover coding is a sedentary job, and a sedentary lifestyle is extremely harmful to physical health.

So we have the three pain points of the software developer job.

The user expérience should be what matters the most.

Les salaires de développeurs ne semblent pas avoir augmentés plus que cela. Ils ont cependant suivi l'inflation.

protip: when referring to your favourite programming language’s features, call them spells instead to sound more mysterious and cool.

👎 “memory safety feature”

👍‍ “memory safety spell”

One of the most prolific contributor on the Astro documentation 👍
They insights are awesome for all devs.

In the presence of uncertainty, acquiring information is often the best way to generate value. — Dan Milstein

1 hour of planning can save you 1000 hours of coding. 1 hour of coding can save your 1000 hours of planning. There is no science to figuring out which case you’re in. Only art. — Robert Roskam

OK a queue of tasks: tasks build a feature. In a sprint, the story points (and velocity) are replaced with tasks (or task rate).

Reacting to fast feedback is literally the point. you update the tasks with the new information. Your team can mob around the new information and add new tasks and remove tasks that no longer apply.

You get more accurate projections and estimates because you stopped estimating.

There is one way to control the flow rate from the support queue: quality control and rapid response to support issues. Higher quality control is designed to reduce the output of issues which could potentially trigger support requests. Rapid response allows you to immediately deal with any issues that quality control didn't catch but your customers did.