Jezen Thomas

My blog sometimes appears on this website and generates some interesting discussion. I most recently wrote about making database tables smaller, and I plan to write more posts exploring what “make it smaller” means to me. It’s usually about the size of the problem space, and the economics of expediency. https://jezenthomas.com/ I plan to make the business calmer by further establishing a culture of conscientious writing among my colleagues. I’m a big fan of 37 Signals and I often (but not always) follow their lead in business. I have been pushing (and leading by example) for written pitches paired with fat marker sketches for proposed feature development. Previously we have plugged insufficient specification and iteration directly into high-fidelity UI design, leaving developers to infer product behaviour from graphics they see in Figma. I think this hasn’t worked. I also plan to continue aggressively cutting features. I would rather sell half a product than a half-assed product, and I think the benefits of paring a product down to the good bits has a positive compounding effect on both the user experience, the developer experience, the sales pitch, etc.

Remembering best practices for BASH might be hard. I recommend using http://www.shellcheck.net/. I use with vim and syntastic. This article talks more about it: http://jezenthomas.com/shell-script-static-analysis-in-vim/

Link seems to be dead. 404. Oddly, it works without the final '/'. http://jezenthomas.com/deploying-a-haskell-web-service-with-nix