RSSAmplifier

Blog

Resilient Systems

Creating software with the future in mind

evgenii.infoRSS feed ↗15 posts

Latest posts

How Weak Opinions Damage Code Review

Weak opinions are comments that don't require action. They may seem gentle, but can lead to hard issues down the line. Let’s aim higher and promote strong opinions, constructive feedback, and a commitment to excellence.

Overcoming Inertia in Tasks and Projects

Tactics for overcoming inertia, recognising when to pivot, and a few words about the importance of collaboration and estimation.

The power of "I don't know"

When a colleague has a question, it can be tempting to stay quiet if you don't know the answer. But admitting that you don't know is more helpful

Keeping meetings on track

A list of tips to help you keep meetings on track.

What to do if you're a bottleneck

Jackson is a go-to person when it comes to MongoDB. You have a problem – you go to Jackson.

[Video] A Practical Guide to Personal SLA

Personal SLAs: How to maintain balance at work (recording)

The Story About a Smart Boss

Some people are lucky to work with extremely smart bosses. Molly hit the jackpot.

When to Use Nested Functions

Functions inside other functions... Worth it?

Driving Changes: How to Deal with Pushbacks

Facing pushback while driving engineering initiatives: most common reasons, how to prevent and handle.

The Story about Algorithms in Interviews

Meet Jeremy: he doesn't like old-fashioned tech interviews, but what alternative does he choose?

How to use console.log to simplify refactoring

How a simple trick with console.log can help you with refactoring

The Story About the Boy Scout Rule

The Boy Scout rule (always leave the code in a better state than when you found it) is famous among developers, but does it have its pitfalls? Meet Simon and Andy, who have a lot to share.

New to the Project? Do Code Reviews!

Why all new developers should do code reviews, how to begin and get the most out of it

Reckless Reuse: How Modules Grow Big

Does your project have an enormous module called something-manager or something-controller that grew beyond any possible limits and became completely unmaintainable? How to prevent it from happening?

Not as Productive as Others?

Highly effective colleagues are invaluable for keeping oneself sharp. But what if it works the other way around and makes you lose heart?