markdown guide
 

Do things right first, and by right I also mean only the things you need to do.

YAGNI.
DRY.

By cutting out what you don't really need the things that you do right will be faster.

 

So true. The first time I came across YAGNI, I wasn't convinced. The second time -- with more failures behind me -- the concept clicked. Then it changed my whole outlook on work.

 

I usually present information to management and product owners that "if we do X it will be fast but have Y thing happen later" and "if we do Z then that it won't happen BUT will take longer". There is a really nice freedom in being senior enough to advise but not to decide.

 

Seems a false dichotomy. If you don't do things the right way, you will inevitably have to go back and fix them. Which is another way of saying, "you'll have to do the work twice" ...which is generally slower than doing it once.

 

Saying its a false dichotomy is quite easy when there is no deadline. But its quite a different story when deadline hits hard.

So, handling this topic is the most hardest thing when you're in a leading role of a project. For me, it is more a prior subject to hold a deadline. You can always refactor code later on. But you can't refactor time. So when it comes to this point, my advice would be: hold the line, refactor later.
A customer is more impressed, when your team can do its job even if the pressure is hard. But no customer will value the code you or your team will deploy. As long as it works as intended.

 

I tend to make things right first so it's easier to make things faster afterwards. A good software foundation is a must for incremental development.

Classic DEV Post from Jan 30

Make art, not apps <3

You don't have to build an app. In fact, if you don't need to, then don't.

Rattanak Chea profile image
Full stack developer. Open to new opportunity.

dev.to now has dark mode.

Go to the "misc" section of your settings and select night theme ❤️