The ClojureScript (CLJS) story has been moving so quickly for a few years now that occasionally it’s worth putting together a quick post on how to get started with a productive dev environment as simply as possible.
Here’s my version for late 2018 (November).
tl;dr the best way to get rolling is now
First you need a new and up-to-date Clojure.
$ brew install clojure
brew upgrade clojure if you already have a 1.9+ version and want to get the latest)
Static site generators are the best way to produce a simple, secure, super fast website.
But the generators themselves aren’t all that simple, and it can be tedious to choose one of the many, learn it, and get started.
Here’s a quick way to roll your own with nothing but the basic skills you might have learned as a webmaster in 1999.
You want to
You’ve read the lean startup books, you’ve listened to the podcasts, and you want to validate your startup idea with real customers as fast as possible.
One classic technique is to put up a landing page with a payment button on it, and prove whether you can convince real customers to pay you money before you have a full product.
The only problem is, you don’t want to spend the time and effort — or hire a developer — to build a secure back end server application to help you take payments (which is what you have to do to…
Atlassian JIRA is the market leading issue-tracking and agile project management tool, and is in heavy use at companies around the globe.
For CTX, my team search app I wanted to build a slick integration to JIRA to help my customers to search their JIRA issues alongside their Slack messages, Trello cards, files, GitHub issues and emails.
Don’t waste time picking tools to run your startup, just get these.
When you’re starting a startup or project, it’s easy to fall into the trap of taking ages over unimportant details, while putting off the really important, but awkward, things — like talking to customers.
One of these traps is choosing just the right set of tools to manage the project.
(This post is about non-technical tools — but tech founders often do exactly the same thing when identifying the “stack” to use too. Some day I’ll write a post about that.)
When starting CTX, I made a conscious…
I mean this isn the best possible way, but developers are like children (for the avoidance of doubt, so are testers, UXers, ops folk and Scrum masters)
What do I mean by that?
Well, I have a 5 year old daughter who’s in her first year at school.
Each term we get a mini report card from the school that tells us about her progress. Because she’s so little, she doesn’t have exams yet (thankfully), so it’s not a list of grades — instead it’s a few short paragraphs of observations from her teacher.
These observations tend to focus on…
It’s also not “analyst”, or “sysadmin” or “tester”.
Your job is definitely not “manager”.
In a modern software team, your job is to help your team ship working software so your employer (customer) gets more value.
The skills you use to help your team do that might be mostly development, or mostly devops technologies, or mostly people management, or you might be a great organiser and facilitator so you often wear the “scrum master” hat. That’s cool.
But your responsibility is to judge which of your skills you should be applying for your team at any given time.