The single most important "side-effect" of solving linear equation systems: the LU decomposition.

Why? Because in practice, it is the engine behind inverting matrices and computing their determinants.

Here is how it works.

Burnout sneaks up when:

• You skip meals to code
• Social life is on autopilot
• Work spills into personal time

The fix?

• Commit to one health habit
• Treat relationships like deadlines
• Take breaks before you feel tired

Start small—big changes follow.

Most software engineers let their employer define their career—big mistake.

Here’s what happens when you build a personal brand:

• Recruiters come to you.
• Side projects become income.
• You gain freedom and influence.

Take control.
Build your brand.

Picture this: you’re asked to update a decade-old codebase, and every change feels like defusing a bomb.

One wrong move, and everything breaks.

Frustrating, right?

That’s the cost of poor maintainability—a problem you can avoid by mastering a few simple principles.

The most underrated way to contribute is by being a great listener.

This is how you should listen in meetings:

• Pay attention—don’t multitask.
• Summarize key points to ensure alignment.
• Encourage quieter teammates to share their thoughts.

My wish for you:

• The mind of an entrepreneur.
• The body of an athlete.
• The soul of an artist.

That’s it.

You don’t feel satisfied at the end of the workday.

I get it. Back in 2022, I was no different. I was working at my third job as a software engineer, juggling meetings, fixing bugs, writing documentation, and reviewing code like a productivity machine.

But something didn’t sit right.

I spent 2 years working completely remote jobs.

Here are the 3 mistakes I made distilled into 3 posts (so that you can avoid them):

Just had a one-word retrospective meeting with my team.

This was our sprint in 5 words:

- IKEA
- Positive
- Multitasking
- Interruptions
- Disconnected

More on this coming soon…

You don’t feel satisfied at the end of the workday.

I get it. Back in 2022, I was no different. I was working at my third job as a software engineer, juggling meetings, fixing bugs, writing documentation, and reviewing code like a productivity machine.

But something didn’t sit right.

My Favorite Software Development Framework:

1. Generate an idea.
2. Create an MVP.
3. Publish it.
4. Market it.
5. Collect feedback.
6. Modify based on feedback.
7. Repeat from step 3.

Works every time.

You are not focusing on what matters.

Being productive is not about working more.

Instead, focus on working better.

Spread the word.

Journaling is no mumbo jumbo.

Software engineers should do it too.

I've done it for the past 10 months and I think more clearly now.

If you don't know where to start, here's how you can get started:

You are not focusing on what matters.

Being productive is not about working more.

Instead, focus on working better.

Spread the word.

🧠 A new edition of Algorithmically Speaking is out!

🤯 It's time to see how boards and graphs are related.

📭 Subscribe if you don't want to miss any of the weekly posts.

Being able to read an adjacency matrix can give you insightful information about the graph.

For example, inspecting the following matrix, we can realize that:

🔸 Node number 1 has the most outgoing edges, while
🔸 Node number 5 has the least (actually it doesn’t have any)

Hello Bluesky! I'm new here, so I thought about introducing myself:

I'm Alberto, a Computer Scientist living in Sweden. Currently working as a software developer in Volvo Cars, and teaching about algorithms, data structures and Computer Science here 👇