---
title: "Ben Buchanan (200ok) (@200ok) | Hashnode"
description: "I make some bits of the web. Read the latest articles by Ben Buchanan (200ok) on Hashnode."
url: "https://hashnode.com/@200ok"
---

@200ok

# Ben Buchanan (200ok)

@200ok · Australia · Joined April 2016

I make some bits of the web.

[Website](http://weblog.200ok.com.au/)

## Comments

[Do you write documentations? Yes, a lot. I do a lot of work on UI libraries and other things with APIs. For projects like that, anything you don't document may as well not exist at all. For other projects, I'm regularly documenting onboarding/setup guides so people (or just me in a year) can easily learn how to get the project up and running. What role do you think documentations play in writing good code/software? They reduce risk, increase developer engagement... basically good docs make for a happy team. What are the best practices you've seen/heard/used in writing documentations? Be concise - write just enough Write without assumptions - write a document that someone could follow without needing help If you do make assumptions, declare what they are (eg. I often state prerequisites for installation guides) Treat docs like code - DRY and YAGNI both apply surprisingly well. Docs can be modular! Think about the maintainability of your docs - don't set yourself up for an impossible task What are you trying to avoid in documentation? (bad practices? common mis-conceptions?) Unmaintained or innacurate docs are harmful Unmaintained or innacurate docs are REALLY harmful No one tool is the best for all documentation - eg. I use a mix of wiki (Confluence), markdown files in repos (readmes) and purpose-built documentation websites. I don't use much auto-generated documentation as I find it tends to be less useful. In the end though, the tool your team will happily use and maintain is the right tool.](https://hashnode.com/forums/thread/how-do-you-write-documentations-what-practices-do-you-follow/comment/5ece7bb3957247ce0a4ec63a)

Comment · Thread · May 27, 2020 · [How do you write documentations? What practices do you follow?](https://hashnode.com/forums/thread/how-do-you-write-documentations-what-practices-do-you-follow)

[Native technology tends to outlast any given proprietary technology. So I would say if it really was a black and white question, go with the web. It constantly evolves and you'll never have time to get bored ;) But the real question is whether you like working on apps in a specific ecosystem, or if you like building for a more general case. If you like one in particular, do it!](https://hashnode.com/forums/thread/what-will-be-better-to-become/comment/5ece76b0123fdcb70b93182b)

Comment · Thread · May 27, 2020 · [What will be better to become?](https://hashnode.com/forums/thread/what-will-be-better-to-become)

[You can learn anything given enough time. The main thing is not to try to learn everything at once - focus one or just a couple of things at a time; learn them well; use them regularly so you retain the information. Build up your personal library of notes and code samples so you can pick things up again later. Also be clear on the difference between concepts, methodologies and languages; so you can work out how you learn them most effectively. In terms of "mastering" multiple stacks - the wider you spread your attention, the less you can deep dive into any specific thing. Earlier in your career it's normal to learn a wide range of things, over time you'll find the things you really enjoy and naturally want to dive in deep and truly master. Or maybe you'll become a really well-rounded generalist. There is no "right" way, do what you enjoy; keeping an eye on what will keep you gainfully employed ;)](https://hashnode.com/forums/thread/is-it-possible-to-master-in-many-stacks/comment/5ece7645957247ce0a4ec616)

Comment · Thread · May 27, 2020 · [Is it possible to master in many stacks?](https://hashnode.com/forums/thread/is-it-possible-to-master-in-many-stacks)

[All the above, really. Plus time to focus long enough to get in the zone and get stuff done. Sometimes music is swapped for quiet.](https://hashnode.com/forums/thread/what-makes-you-productive-as-a-developer/comment/5ece7307123fdcb70b931759)

Comment · Thread · May 27, 2020 · [What makes you productive as a developer](https://hashnode.com/forums/thread/what-makes-you-productive-as-a-developer)

[I appreciate it's not the question you're asking, but... my immediate thought was that unless the company is planning to sell the LMS itself (as opposed to selling the learning being done on top of it), you should probably review existing options. There are a lot of them out there and unless you have really unusual requirements you may find it better to customise something off the shelf, rather than build from scratch. Worst case, it will give you lots of ideas to consider in your own build :) To address your question more directly: if this job is being handed to you directly with no additional staff coming, go with whatever you personally know really well and can comfortably build and support. The only caveat is you should sanity check your choice in terms of whether you will be able to hire people when the company does grow. React and AWS are certainly solid choices... I have no idea how many people in your market know Laravel though.](https://hashnode.com/forums/thread/best-tech-stack-to-develop-an-e-learning-platform/comment/5e907e3044e36e1a7630bbc6)

Comment · Thread · Apr 10, 2020 · [Best tech-stack to develop an e-learning platform?](https://hashnode.com/forums/thread/best-tech-stack-to-develop-an-e-learning-platform)

[I find it useful to name them separately just to make it clear which files have JSX and which do not. Some code tools benefit from the explicit file extension; and you might have different linting settings, associate them with different test types and so on. Basically it's just a bit more accurate. We also name ts/tsx separately from js/jsx for much the same reason.](https://hashnode.com/forums/thread/what-are-the-significant-differences-between-naming-a-javascript-file-with-js-or-jsx/comment/5e186a64b523bae931586fc1)

Comment · Thread · Jan 10, 2020 · [What are the significant differences between naming a JavaScript file with .js or .jsx](https://hashnode.com/forums/thread/what-are-the-significant-differences-between-naming-a-javascript-file-with-js-or-jsx)

[While not quite what you asked I think my experience with junior devs is more illuminating than my personal experience learning React... The most common issues I've observed amongst juniors is trying to learn everything at once. eg. React+ES6+Typescript+Redux (and probably HTML and CSS as well; and probably webpack; and Jest or some other tests... oh and the build just failed so go and debug that...). There is just too much going on and they don't yet know which bit is which. They have to hunt through all the docs for every question they have, until they slowly piece it back together the hard way. Think of this way: if you didn't know any of these things separately, how would you know that an enum used by a JSX prop is typescript? Juniors have a better time when they slow down just enough to learn ES6, then Typescript, then pure React (I recommend starting with React Armory for this), then add on state management. This doesn't have to be a long and arduous training regime, it's just a matter of layering things on so they know where things "come from" so to speak. The order can be mixed around a bit as well, the key thing is to learn the bits separate before putting them together. As a sidenote to this - we provide our juniors with a specific list of key things to learn for each technology. eg. we don't say "go learn... hand-wave you know, ES6"... we say learn these specific features of ES6. Because if you don't know arrow functions you really aren't getting far! Stuff like that.](https://hashnode.com/forums/thread/what-is-the-biggest-problem-you-have-in-learning-react/comment/5e147c871a3128c630de9083)

Comment · Thread · Jan 7, 2020 · [What is the biggest problem you have in learning React?](https://hashnode.com/forums/thread/what-is-the-biggest-problem-you-have-in-learning-react)

[https://learn.shayhowe.com/ https://marksheet.io/](https://hashnode.com/forums/thread/what-are-the-best-resources-to-learn-css-and-design/comment/5e01ca2f63a8929272c3450e)

Comment · Thread · Dec 24, 2019 · [What are the best resources to learn CSS and Design?](https://hashnode.com/forums/thread/what-are-the-best-resources-to-learn-css-and-design)

[If I'm understanding your question you have this going on: /\* your code \*/ a {} /\* their code \*/ a {} Generally you shouldn't do detailed styling directly on element tags as they as such weak selectors. You're essentially hoping your style will load last, which you can't really guarantee. You need to put your CSS into a namespace or follow a CSS architecture. A really simple namespace approach: /\* your code \*/ .your-app-namespace a {} /\* their code \*/ a {} Ensure your application's outermost element has class="your-app-namespace" and your styles should apply: <a href="https://example.com/">Their link style</a> <div class="your-app-namespace"> <a href="https://example.com/">Your link style</a> </div> If the other styles have stronger selectors you will have to increase your selector weight until it works. How you do that depends on the selector weight of the competing CSS. Web components, css-in-js etc will also work but to be honest you should probably try a simpler approach first as it may be all you need (much less code).](https://hashnode.com/forums/thread/css-overwriting-problem-micro-service-development/comment/5df223c7066598ab27528d0c)

Comment · Thread · Dec 12, 2019 · [CSS overwriting problem (Micro-service-development)](https://hashnode.com/forums/thread/css-overwriting-problem-micro-service-development)

[For what it's worth, I would reframe your thinking - if you know JavaScript, you know a bunch of programming concepts in JavaScript syntax. If you want to enter a different field that focuses on a different language, you will be able to learn that language. While JS is a quirky beast, so is every other language. You will have learned a conceptual foundation that will give you a head start learning the next language. It did not teach you everything, but it did teach you a lot of transferable concepts. So if you want to work in a different field, don't wait for it to embrace JS. Learn the language that field uses and go for it.](https://hashnode.com/forums/thread/which-other-fields-except-web-can-we-work-in-with-javascript/comment/5df22164066598ab27528d05)

Comment · Thread · Dec 12, 2019 · [Which other fields, except web, can we work in with javascript ?](https://hashnode.com/forums/thread/which-other-fields-except-web-can-we-work-in-with-javascript)
