1,589 karma · joined December 12, 2011
I now work as a "consulting CTO" (see drtomallen.com/consulting) meaning I'll do anything from writing code, defining your architecture, hiring your team, through to persuading your board to raise investment for a new product line.
Cubescape (http://www.cubescape.com.au) is my side business delivering automated Escape Rooms. We've been running for over ten years now. I was the CTO and most of the time the only software developer. We own and operate The Curium Experience, which is rapidly gaining a reputation as Australia's best escape room. We won the only TERPECA top-room award in the southern hemisphere in 2024.
Best contact is email: tom@jugglethis.net
A little example from my life is forgetting to secure the buckle of my motorcycle helmet. Once I've done everything else and gotten my gloves on, it's a pain to take them off again to buckle it up if I forget, and a few times I just shrugged it off and rode anyway.
Then an instructor suggested he always follows exactly the same procedure each time, to the point that he always even puts the same glove on first. It made me wonder if I should do that, and in thinking it through I realised if I changed my order to always buckle up before putting my glasses back on, I'd never forget. There's no way I'd ride off without the glasses (because I can't see without them!), so if that step can only come _after_ buckling up, then there's now no way I'd ever not buckle it up either.
The fact that I can _read this very article_ is why I can trivially afford a $5 coffee. Maybe if we focussed on education instead of $5 coffees, we could get to the point where we could justifiably ignore the coffees.
Cooltrax builds IoT hardware and software to monitor temperatures, control fridges, and track refrigerated goods as they move across the country.
We need senior engineers to help us uplift our legacy systems while developing a new IoT pipeline from scratch. We have happy paying customers, a strong growth story, and interesting software problems to solve. We’ll give you the autonomy to choose the right solutions, the flexibility to work in the way that suits you, and the support to handle everything a rapid-paced start-up environment can throw at you. We have some specific openings for an IoT Architect and DevOps Lead, but are also always looking for generalist software engineers who want to work in the IoT field. We're predominantly a Javascript shop with a tech stack comprising Node/React/Couch/Redis/Kubernetes/etc.
More about the roles: https://www.cooltrax.com/wp-content/uploads/2019/02/Software...
Cooltrax builds IoT hardware and software to monitor temperatures, control fridges, and track trailers as they transport goods across the country. That might sound simple, but Australians alone buy $120bn of groceries each year and our services provide an increasingly critical piece of the supply chain infrastructure that makes this possible. We operate in Australia and the United States and have a small engineering team with their home base in Melbourne.
We run a global real-time temperature monitoring system covering some of the largest supply chain partners in the world, where you will face daily challenges and demanding timelines that will be your problems to solve. But we’ll give you the autonomy to choose the right solutions, the flexibility to work in the way that suits you (working from home or abroad is possible, some of the time), and the support to handle everything a rapid-paced start-up environment can throw at you. Most of our front-end and back-end software is in JavaScript (or increasingly TypeScript), we’re moving from an Ember.js application to React, our firmware is in C/C++, and our infrastructure is defined in code and orchestrated with Kubernetes. Other technology keywords we use include: MySQL, CouchDB, GraphQL, Redis, node.js, Azure, git, and Jira.
For a more thorough position description, or just to have a chat about the sorts of projects we have here, please contact me at: tom.allen@cooltrax.com. I'm the Engineering Manager here and I'm passionate about building a workplace culture that supports high performance engineering. We have our fair share of problems and legacy software to deal with, but there's abundant opportunity for interesting greenfields work too, with a board ready and willing to invest in new areas of the business.
I think that's the nail in the coffin for me; the screens are just too damn big.
Even though that doesn't financially penalise me, it still feels a bit mean. From the company's point of view though, I'm sure they'd view it as far more mean if the government suddenly told them they're obliged to pay everyone more.
The second point is a given in the more socialised parts of Europe, and is a core tenet of most support programs for the involuntarily unemployed elsewhere.
Which is to say; I don't get your point. Sounds like everywhere but the US could do this right now.
"System and method for extracting value from a portfolio of assets" - a.k.a. The process of being a patent troll is patented.
As the software guy, I also found I spent much of the rest of the week subconsciously thinking through issues and solutions anyway, so by the time I did get that six or so hours to code I was pretty damn productive.
https://scripting.wordpress.com/2006/12/20/scripting-news-fo...
Specifically, I do this in Melbourne, Australia where it's free and legal to park a motorcycle on the pavement (aka sidewalk). A 2012 study found that we make up almost exactly 1% of all commuters: http://atrf.info/papers/2013/2013_rose_delbosc.pdf
Is that acceptable, or does it feel like blackmail?
(FWIW I'm discussing this with a lot of other gamedevs too, but since you brought it up I figure you might have a "different community" opinion worth my knowing!)
For the operators I know, most focus on 2) and 4). Most believe the puzzles are the core hook and must be well designed. Then they believe the puzzles have to fit the room theme. If a story can be squeezed in too, then they try, but it's rarely the driver. And gimmicks and wow factor aren't usually high on the list, but some operators (arguably us) do find these make customers want to play when they hear about them, so they're certainly not ignored.
The groups in A are all friendly and collegiate. The groups in B are less so. We see group A continuing happily, but not really growing or turning significant profits - one of my friends in this group described it as "I bought myself a fun job".
We've seen a fair few groups in B fold. As the article suggests, you can't start with a mere $7000 now - customer expectations are higher, and there are enough review sites (e.g. TripAdvisor) that anyone with a low quality game will be called out pretty quickly.
Groups in C (include Nate Martin from the article) all seem to be doing well, but it's a hard slog to get sufficiently well known to become a primary supplier to others. My company is kind of in C, but we partnered early with a key chain in our geography and there's both good and bad to that choice. Not personally operating our rooms certainly has some drawbacks, but being able to build multiple copies of a room simultaneously has enormous cost savings too.
We try to do things like detect partial solutions that might indicate the players are close to a full solution, because the worst thing is to bypass a puzzle when the players are actively engaged with it and having fun. On the other hand, if we know there's more interesting gameplay to come, and the players are spending ages on a particular puzzle, we want them to progress. This is the part where some enthusiasts disagree with our approach - some of them would rather fail than be pushed through. Fortunately, the bulk of our players would rather be given increasingly easy hints until they "solve" things themselves.
ER enthusiasts typically seem to prefer losing to having a puzzle spoiled by a clue, and as a result, often hate our rooms. First timers, who make up >99.5% of our customers, absolutely love it. It's a weird position to not focus on repeat business, but in such a supply-limited market there doesn't seem to be any shortage of new customers. It's also a pleasant market to operate in because virtually all the other operators are our friends - everyone refers customers to other venues because they can't replay your rooms anyway. There's hardly any of the cut-throat business practices you might see in other fields.
AMA if you're interested!
The first was my Ph.D. writing path planning algorithms for autonomous vehicles. We drove robots autonomously across an entire farm. We ran trials combining data from ground and aerial vehicles in real-time. I flew in a helicopter telling the pilot where to go based on instructions from a GUI I wrote that was receiving data from the ground vehicle running my path planning code, sending its data back up to me via a datagram I specified and a threading and networking library I designed. It was a great team of people, and the core group of five of us is still in touch and sporadically working together a decade later.
The second was the early years of my company, Cubescape, which makes Escape Rooms that run without a human game-master. I spent my thirtieth birthday crouched in a pile of dust debugging why a DMX controlled light wasn't properly flashing out a morse-code sequence, and why one particular Raspberry Pi would reboot after our strobe light kicked in. (Nope, not current draw - turns out if you hit the right chip with the right frequency of light, the photoelectric effect can cause a voltage drop. We covered it up with duct tape...) These days I've mostly automated myself out of a job so even though it's my baby, it's still less fulfilling than those early periods.
Everything else I've ever done in (work) life has been less fulfilling than these journeys, and it's really only through a recent period of deep introspection that I've managed to connect the dots and nail down those three key requirements. I'm now looking for what might be next, and using those as a filter on the opportunities - if you think your company fits, please reach out!
That's pretty impressive!