Posts • Korolev Blog

Posts

Know that you will save it in the repository Feb 18 '25
Try before you decide Feb 16 '25
Do not touch this code Feb 15 '25
Prevent the occurrence of errors Feb 01 '25
Install me Jan 23 '25
One binary file Jan 19 '25
Durability of temporary solutions Jan 14 '25
Use quantitative criteria Dec 28 '24
Satisfy your ambition through Open Source Dec 19 '24
Your clients mean something different than what they say Dec 17 '24
Do not be afraid to break something Dec 14 '24
Take responsibility for your build and its refactoring Dec 05 '24
The drama of hype technologies, customer needs, and pangs of conscience Dec 02 '24
Enterprise interview Dec 01 '24
Do not rely on miracles Nov 26 '24
Incredible, but testers are your friends Nov 25 '24
The golden rule of API design Nov 23 '24
You are negotiating Nov 22 '24
Program in pairs and get into the flow Nov 19 '24
Learn foreign languages Nov 02 '24
How to use the bug tracking system Oct 28 '24
Try not to alter the timetable Oct 28 '24
Tests are written for people Oct 24 '24
Professional programmer Oct 23 '24
Convenience is not an attribute of quality Oct 17 '24
One line of working code costs 500 lines of specifications Oct 17 '24
Carefully choose your tools Oct 10 '24
Comment only on what the code not say Oct 02 '24
Message passing improves the scalability of parallel systems Sep 22 '24
Relational Database Management Systems Sep 19 '24
Architectural compromises Sep 16 '24
Simplicity is achieved through reduction Sep 13 '24
Programming paradigms Sep 07 '24
Interfaces Sep 06 '24
Improve the code by removing it Aug 22 '24
Communication is the king, clarity and leadership are its loyal servants Aug 08 '24
Read the code Aug 08 '24
Know how to use command line utilities Jul 21 '24
To do something hastily and run away is a crime Jul 20 '24
Write code as if you will be maintaining it for the rest of your life Jul 19 '24
Before starting the refactoring Jul 14 '24
The importance of code formatting Jul 09 '24
Write code wisely Jul 09 '24
Before blaming others, check your own code Jul 08 '24
The assembly must be clean Jul 01 '24
Code is design Jun 29 '24
Continuous learning Jun 28 '24
Hard work does not justify itself Jun 26 '24
The myth of the guru Jun 26 '24
First say yes Jun 22 '24
Time changes everything Jun 22 '24
Thinking about performance is never too early Jun 03 '24
Warning - Common code ownership May 30 '24
Creating architecture as the art of balance May 29 '24
Apply the principles of functional programming May 22 '24
Only the code will tell the truth May 20 '24
You need to take care of the code May 14 '24
Give developers their own space May 08 '24
Writing code in the spirit of Ubuntu for the friends May 06 '24
Keep everything in version control May 05 '24
When programmers and testers collaborate May 04 '24
Perspective as seen from 300 meters Apr 20 '24
Code review Apr 19 '24
Beauty is the result of simplicity Apr 18 '24
Two mistakes can cancel each other out, making them difficult to correct Apr 18 '24
Automate your code formatting standard Apr 13 '24
Stand up! Apr 05 '24
Do not repeat your code Apr 02 '24
The true meaning of the clients requirements Mar 19 '24
Know your IDE Mar 13 '24
Commentary on comments Mar 12 '24
The performance of an application is determined by its architecture Mar 07 '24
A verbose journal will deprive you of sleep Mar 05 '24