These choices are trade-offs. If you want to write a quiet song, it won't be loud. If you are writing a software tool and you want to prioritize speed over simplicity, then it won't be as simple as if you'd prioritized simplicity over speed.

There are two main signs that you've succeeded at your goals. The first, and more pleasant, is that you get compliments about how your thing is like you wanted it to be. "I love that song, it's so quiet!" "Your tool is so fast!" Why thank you, that's exactly what I was going for.

The second sign, though, is that you will get complaints. Specifically, people will complain that your thing does not achieve the things you didn't set out to achieve. "I wish this song was louder", "this tool is so hard to use". That you are receiving complaints at all means that people are aware of your creation; that they are complaining about what you specifically set out to make a non-goal is a side-effect of the fact that you made that trade-off.

A story of a Julius who lacks knowledge but has good charisma. There's a lot to learn from such Julii.

Когда я работал в Совкомбанке, пришлось чуток поработать с аналитиком Э. Он мне сразу не понравился. Потом он ушёл, раньше меня. Статья помогла понять, что с ним было не так. Наверное он был таким Юлием.

Но очень может быть, что я неправ, и у меня просто не было возможности увидеть хард скиллы этого аналитика. В конце концов, мы пересеклись только на одном низкоприоритетном проекте.

“The longest-running vaporware story in the history of the computer industry”

Герой истории стал выращивать чеснок. По числам очень сомнительно, но читать интересно.

A year ago, Marginalia Search's developer received a grant, so he walked out of the office and never came back, and he still has more money funded. I don't think I would want to work like that forever, but working on my own projects like that for some months — sounds like a dream.

It is very important to conduct regular code reviews within every software team, but it is not so easy to do them right; here are a few typical pitfalls.

OLLOS is an experiment that organizes everything in my personal computing environment on one unified timeline.

Instead of asking over and over again if she is working tomorrow. I just consult her very organised calendar — and when she wants to check if I'm free she looks at my very empty calendar.

Personal goals are generally expected to happen later.
The reason it’s hard to get going on personal goals is that you’re already using all of your time. No matter who you are, you’re already using all 24 hours, every day, for something. Because this will always be true, goals that happen at all must happen now, while you still don’t yet have time.
Basically, you learn to work in small, uniform parcels of time. They’re short, timer-bound, and unwaveringly focused on a particular outcome. Most importantly, they can fit into real life, as it already is.

“JUST” It's one of the worst four-letter words I know.

Автора бесит слово «просто». Меня тоже! Я вот стараюсь его искоренить из себя. Непросто это всё!!

A specific someone in disguise says that accepting help to your software projects often leads to destruction.

You need a good team to go forward.

Get the right people or you'll just waste your time, energy and health!

Poka Yoke - яп. «избегать ошибок». Не искать виноватых в ошибках, но совершенствовать процесс.

10 things to do to improve your team and make yourself replaceable. The author claims that being replaceable makes it easier for you to grow professionally.