Do not over-Design. While a design is imperative, how much of it is needed is completely up to you.
Software Development, Finance and AI20 Tammi 2021

Do not over-Design. While a design is imperative, how much of it is needed is completely up to you.

It’s sometimes compelling to try and get every question answered before you start working on coding a feature (regardless of which part of the stack it belongs to). But it may or may not be a good idea. Find the right balance. Here’s how we do it.

Jaksot(410)

Aspect Programming (or even other flavors of it) come in real handy to solve certain types of problems

Aspect Programming (or even other flavors of it) come in real handy to solve certain types of problems

If you want to add or improve your logging or caching layers, you definitely want to consider doing them using Aspect Programming. Those are some common examples but there are numerous scenarios where touching your "core" coding layers (or, tiers or services) is not a good idea. Aspects come in quite handy on those occasions.

11 Heinä 20204min

Come up with a design (in mind) before you get to your computer

Come up with a design (in mind) before you get to your computer

To make the best use of your time at work, and/or when you are in front of a machine, it is a good idea to come up with a design (no matter how high level) in mind. This way, you can hit the ground running when you get to your machine. I've seen time and again that this approach works for me.

11 Heinä 20201min