This chapter covers lessons learnt in code or architecture. It is most useful for the CTO.
The principle of polite software is a great cheatsheet while improving your product design skills.
You're likely not innovating on tech but rather on the underlying process. So you should hire for people familiar with your niche and tools.
Using a static analysis tool that scans for vulnerabilities is a great help for this.
It's much easier to build it in step with the platform rather than having to backfill later.
Premature optimization might be the root of all evil, but performance often means just not being lazy.
A central place where you can trace errors, track their progress and easily identify regressions becomes valuable very early on.
It's a pre-requisite in some cases, a nice to have in others, but it also gives you better bang for your buck when it comes to hosting.
Docs are useful but will quickly take a back seat. Using tools that generate as much documentation as possible automatically are essential.
These are some common attributes that we've found to be useful to include in many models.
It is important for UX but also removes the need to think about them during implementation.
Build in tracking for things in advance even if you think you won't use them because data is the first step towards developing something new.
Store and sync derived columns that are frequently accessed or that you need a historical record of.
Often the ideal structure involves three levels: system, group, and individual. The setting should be picked up in reverse order.
Don't only avoid magic numbers but avoid constants entirely.
It's just needs setting up once and is useful for a few different things.
That way you will be able to track incoming and outgoing from the start, immediately be able to reconcile, give finance a proper insight and make due diligence easier down the line.
Make a robust import feature that can be used for different entries.
Use a library for exporting your index views to XLS or CSV.
It will be very helpful as a central store of operational knowledge that survives team changes.
This ranges from being able to edit individual order values to being able to perform tasks on users' behalf.
Their features are nearly identical, they all have advantages and disadvantages. Pick the one most of your people are familiar with.
Features that are used frequently, impact sales or are complex should be rolled out in phases rather than to everyone at once.
One part should be the migration while the other implements the functionality. They should be deployable independently.
So you won't needlessly invalidate large parts of your cache
Make sure that duplicate actions aren't destructive or that they cannot be done in the first place.
Instead of querying the stats first, join it with the rows that you have to have.
You can track stats independently and not have to keep adding columns to the main operation models.
Implement a re-usable structure that can be used for different models.