If you have a personal website: how did it change your life?

Instead, it could be better to use:

• community pattern: everyone else is doing it. Everyone sees it they know exactly how and why it is there.
• readability pattern: created for the sake of making more readable code. The only true goal is writing code that anyone can reason quickly about.
• performance pattern: squeeze the code for maximum performance, and it can degrade readability.
• guardrail pattern: it exists to avoid known foot guns such as magic number

Often people see "best practices" as community, readability, or guardrail patterns. It is also time as professional that we use a richer vocabulary.

This article set the priority on humans, which is also a point of the agile manifesto

Programming by voice instead of keyboard

About the complexity of the PRs. The less complex the better.
There are analogy to O(1), o(n), O(n×m) and O(n!)

It’s a reminder that reliability, consistency, and user satisfaction can coexist in the realm of software development.

Maintaining, improving code, fixing bugs and delivering minor features. Small step by small steps.

1. Automating stuff gives you superhero strengths
2. Coding is fun (and we can forget the rest)
3. Sharing is fun too
4. Elegant, creative solutions
5. Talk to a machine
6. Standing on the shoulders of giants

The difference between professional and hobby is accountability. In professional programming, you're expected to get the job done.

If a skill becomes obsolete, it's not a skill.

Professional programmers have to balance constraints: deadlines, budgets, and code quality for example.

At the end one of the most important fact is communication.

The dedication, the urgency to reach your aims must come from within you.

About job announces

Build minimal BitTorrent, HTTP server, grep, Redis, Docker, Git, SQLite (and more will be added). The guides are not exclusive to rust, and they support manu languages instead.

One nice thing about being employed is when you wake up, you know what you're going to do. You're going to work. The choice has been made.

The author shares ways he tries to stay motivated:

1. Work on things that you find engaging
2. Building routines into the day: Coffee and a walk with my partner, gym for an hour, journal and write, work block 1 (3 hours), lunch and chill, work block 2 (3 hours).

Do I manage to keep to this structure every day? No. But I try and mostly succeed. It's a framework. Sometimes I'm just not feeling it and allow myself a day off to read or play PlayStation. Without forcing myself to grind I never get too ground down.

3. I'm intentional with my down-time

To preserve my focus I don't engage with any of these platforms until the end of the work day.

4. I hang out with people in my field
5. I write about it

Basic advices, so nothing new at the end.

1. Use programming standards
2. Use programming design principles
3. Use patterns
4. Use proper names
5. Use tests
6. Manage time, as time estimation often fails. Double or triple the estimated time
7. Use appropriate speed

DORA and SPACE give some pointers, and we offer two more:

• Producing at least one customer-facing thing per team, per week.
• Delivering business impact committed to by the team.