Posts • Korolev Blog

Posts

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