Presumption of innocence -> every person is considered innocent until proven guilty.
⬇️
Presumption of bug-free -> every issue is considered innocent until proven with minimal reproduction.
👌

It can be useful someday

Two lessons from algorithms:

1. Debugging complex code is hard, first simplify, then debug.
2. Single source of truth is good

Second, algorithms teach about properties and invariants.
Third, algorithms occasionally are useful at the job!
Fourth, connecting to the previous ones, the ideas really do form interconnected web which, on a deep level, underpins a whole lot of stuff.

Here again a list of algorithms.

When looking for a job, it can be tricky to know what to ask for in terms of salary, especially for underrepresented minorities, who are routinely under leveled and underpaid. So I thought it would be useful to share my salary history since becoming a software engineer, in hopes that it will help someone at some point.

The author of https://carol.gg/salary/ shares their salary too

When you develop a major new feature, product, anything, one of the defining characteristics is that you don't know what you're building. The only way you know what you're building is if you've built it before.

This leads to a problem: If you don't know what you're building, how do you know where the rough edges are? How do you know what the design demands, and what technical decisions to make?

Another personal website <3

I'm a front-end developer, designer, accessibility specialist, educator, and CSS artist. I write, speak, and collect ethical design resources. I work freelance, and you can hire me.

The blog: https://fossheim.io/writing/

A frontend developer and accessibility auditor (and other things). The website design is close to the WCAG documents appearance :D

The blog: https://www.matuzo.at/blog/

A list of projects of Lee Martin:

His dev blog is on Medium: https://leemartin.dev/?gi=e5f0945e85bd

The personal website of cassie :)

My blog is where I think out loud. Expect mainly front-end development, with a sprinkling of self care and mental health.

A personal website that has themes depending of the day: "live", "cycle", "sunrise", "Day", "Sunset", "Night" and "Light".

I'm a web developer based in Edinburgh, Scotland, and use the pronouns he/him. I love front-end development—particularly CSS, HTML, and web performance.

The blog: https://alistairshepherd.uk/writing/

A design egineer with a focus on accessibility.

The blog: https://www.ellyloel.com/blog/

She make a difference between blog post (longer content) and digital garden for thoughts.

Programming with HTML, CSS and JS :)

The website has a neon title with pixellised icons and multiple themes are available for the website.

The blog: https://localghost.dev/blog

Writing recently about Hotwire, SPA, and Dev stuff

because it does not fit long-term.

I was lucky to learn this lesson very early in my career: there is no silver bullet, any single tool, no matter how good it is, must be evaluated from the engineering point of view of pros and cons. Everything has a cost, and implies compromises. It's a matter of ROI. Which is hard to evaluate without experience.

JS technologies are reinventing the wheel and breaks compatibility often. More examples are provided.

So it is coming back to reason:

• YAGNI is popular again
• Vue, HTMX and unpoly, alpine.js or just vanilla are getting traction.
• There is talk of coming back to using Postgres for most things.

You do need the cloud, containers, nosql, go, rust and js build systems. Modern software requirements, customers’ expectations and incredible new features are not to be ignored.
Just not for everything.