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