2,615 karma · joined January 9, 2014
Stuff I’ve built/participated in:
https://www.narakeet.com, https://votito.com, https://bugmagnet.org
Previously worked on https://www.mindmup.com, https://claudiajs.com
My books: https://gojko.net/books/
eg. in australia, they launched the derided 'robo-debt' system that sent people notices about potential benefit fraud charges, and the harassment of people caused senate investigations in several states. turns out the new system is as correct/wrong as the manual process (20% error rate), but it's now able to process several order magnitude more cases, so effectively floods downstream workflows (claims, complaints, courts) that were not ready for such an increase in demand.
Monty Python's Flying Circus - 4 seasons
Peep Show - 9 seasons
Coupling - 4 seasons
That Mitchell and Webb Look - 4 seasons
Most developers today use automated builds, packaging, test runners, app genertors and so on.
Automation in software development is already there, it's been present from almost day 0, but it has so far been aimed at assisting humans, not completely replacing them.
this kind of linting can't spot broken document structure
in terms of 'make them untractive to do business with', since the company was restructured in this way we worked with some of the worlds largest investment banks, big telecoms companies, and a ton of other parties that require a lot of paperwork. nobody seemed to mind that we're structured this way or find us unattractive to work with.
This is missing the point (full disclosure: I know several people working at Crisp and co-organise workshops with them in Sweden).
I remember hearing Henrik Kniberg talk about this at Oredev a while ago, and we ended up restructuring our consultancy firm quite close to their model in 2013. The idea is that you don't work for the company, the company works for you. It's applicable to consultancies, where everyone effectively goes and earns money on their own, but some shared overhead (such as accountants, paperwork, getting master-services agreements with banks and insurance certificates so you can do business) can be effectively shared by everyone under the same umbrella.
our model is not a 10% haircut, but that all shared costs are divided according to the proportion of revenue quarterly. the company also doesn't have a boss or anyone in charge (legally, in the UK, we have designated partners who are allowed to sign documents, but everyone has that right, so everyone is a boss and nobody is the Boss).
Our company is also not allowed by the statute to have any assets or own any IP, that all belongs to individuals. This is to avoid any conflict of interest and people starting to 'work for the company' in the future.
This model obviously wouldn't apply to companies trying to accumulate wealth/IP/assets and looking to create an exit by selling the company. But it works amazingly well if you want a lifestyle consulting business where everyone does their stuff.
Edit: typos
I used to sell books on my own site as well until a few years back when EU created the stupid VAT on private electronic purchases that requires stores to adjust price according to the country of the buyer. I figured it's less hassle to just use leanpub for that.
Another book was on an emerging technique for collaborative analysis for software projects, that started becoming popular some time back in 2008-9 but was still not well understood.
Two more were on practical tips for how to work with user stories and how to come up with good testing ideas.
a slightly less dumb idea is to write a book. it's more upfront/unpaid work than when doing gigs, and more risk because it's up to you to create a good story, but significantly less risk than building a SaaS system. I've self-published five books so far, and books have three benefits over the gig economy idea:
1) you get to learn a ton of new stuff while researching for the book. writing a book is effectively forcing yourself to learn
2) even if books do moderately well, when you self-publish you retain most of the profit. my passive income from previously published books is roughly 3-4K USD per month now
3) books have an extra effect that they tend to bring name recognition and incoming work for consulting, and that can last a few years even if you don't plan to freelance and work as a consultant at the moment.
On a side note, the API was so broken, badly documented and useless that when we evaluated embedding an app into hangouts it just seemed as a half-arsed effort by Google to expose an API, and it was clear that they didn't really want people building apps inside hangouts. which is a shame, it seemed as a nice platform to extend with collab tools. I'm not at all surprised this got pulled.
I think this is perfectly normal and expected. When the platform is immature, small teams especially with opensource tools can move faster than the platform and plug holes in it, but then the platform can catch up and offer a systematic solution to a wider number of customers.
For us, Claudia was a way to get our primary app running in Lambda faster and easier. If they replace our needs with a systematic tool, I can spend more time maintaining my primary product and not patching up the platform. Although it's fun to do opensource tools and get some community support and feedback, the money comes from other places.
For people building startups to patch up platforms, the situation is obviously completely different.
if you want api-level analytics stuff and dashboards, have a look at amazon mobile analytics. it's an interesting alternative to google analytics that lets you control the session key (so it's easy to correlate events from front-end and back-end), and the event data is also yours (so it can easily be exported).
People wanted to implement new things, support new databases, I felt overprotective of the design, but didn't have enough time to bring new contributors onboard. So I just kind of gave up, and that allowed me to think about it from a completely different perspective. If I just deleted it, then I wouldn't care too much about it any more. Giving away the keys was kind of the same, but without preventing others from contributing. And it worked out great.
And sure, I can self-host something and it's going to be cheaper if you just measure the cost of hardware. but count in the cost of humans maintaining that, patching the OS, dealing with security, working the network etc. You might be particularly good at that (and if you're running all your stuff you probably are), but I'm not. And I don't want to be. I want to focus on building stuff that I care about. So paying a bit more for server hosting works out a lot cheaper than managing all that myself, as I can focus on other things.
On the whole serverless thing - yes, it's a buzzword, but people tend to look at it from a technical perspective which is all wrong. the financial side is what matters. the tech isn't really that exciting there -- sure, there's a lot of new tech like containers, but the major change is that I'm only paying for stuff when it does something useful, instead of paying for servers to sit idle. But that's a topic for a completely different discussion. I published some of my thoughts on it here: https://gojko.net/2016/08/27/serverless.html