Olaitan Adebayo.

Questioning what is assumed before building on it.

Most bad websites and most bad products share one cause: they were built on an assumption nobody checked. Who the visitor is, what they came for, what they already believe about the business, what they will do next. The assumption felt obvious, so it was never written down, so it was never tested, so the whole thing was built on it.

The habit here is simple and slightly uncomfortable: before building anything, find the sentence everyone is treating as true and ask how we know. It is cheaper to test a sentence than to rebuild a system. Sometimes a five-minute conversation with three real customers changes the plan entirely.

Critical thinking is not being negative. It is refusing to spend a month of work on something that could have been checked in an afternoon.

Systems, cause and effect, and why things work.

A website is a system. So is a business, a habit, a team, a city's traffic. Systems have inputs, rules and outputs, and when you understand one well enough you can predict what a change will do before you make it. That is the difference between fixing a problem and moving it somewhere you cannot see.

In practice this means drawing the thing before building it: where does a visitor come from, what happens when they click, where does the enquiry go, who reads it, what happens if nobody does. Most failures are found on the drawing, where they cost nothing.

Logic does not replace judgement. It gives judgement something solid to stand on.

Where the ideas come from.

Ideas do not arrive by waiting. They come from reading widely and noticing what annoys people, from connecting two unrelated things, from asking what a website would be if it were a room instead of a page. The 3D studio at olexweb.com/studio is the answer to that last question.

The other half of creativity is protection: giving an idea enough quiet to grow before judging it. Most ideas die in the first ten seconds, killed by the voice that says it has been done or it will not work. Write it down first. Judge it next week.

The Lab, further down this page, is where most of that noticing ends up, and where a few of the notes become products.

Extensive reading and learning, every day.

The person doing the building is the most important part of the build. Every skill compounds: the tenth site is built with everything learnt on the first nine, and the hundredth book changes how the next one is read. So learning is not a hobby that happens after work here. It is the work that makes the work possible.

The routine is unglamorous: read every day, write down what was learnt, try one new thing in every project, and revisit the notes. The results show up slowly and then all at once.

The books on the shelf are the visible part of that habit.

The shelf, and why these are on it.

Clean Code, because the difference between code that works today and code that still works in two years is care, and care can be learnt. Atomic Habits, because the studio runs on habits more than on inspiration. The Psychology of Money, because every business decision is a money decision wearing a disguise. The Lean Startup, because the fastest way to find out if an idea is good is to build the smallest version of it and put it in front of someone.

The rest of the shelf changes. Technology, business, human behaviour, how people think and decide. Reading widely is how the ideas in the Lab get their raw material.

If one book had to be recommended to someone building their first product, it would be The Lean Startup, read twice.