> Also, most of us are unlike the author, and 0.07s vs 0.38s startup time means no difference.
That's quite likely a workflow thing. If you are popping up new (transient) terminals frequently, then a ~400ms wait time for each adds up and makes the entire machine feel really slow. I'm willing to wait extra half a second for a new terminal -- once -- after I've changed my autocompletion configs (rebuild + rehash takes a while), but if I had to wait for that long every time I hit Win+enter and wait for the terminal to become active, I'd be irritated pretty damn quickly too.
You get conditioned to immediate responses pretty fast.
This has already been the case for political and/or social impact events for years in the UK's betting exchanges. The settlement rules for any potentially hairy real-world event have to be explicitly clear and account for all possible outcomes that might affect the resolution.
When there's money on the line, I have years of hard evidence that arm-chair lawyers (ie. betting exchange clients) will do absolutely anything to find potential loopholes in settlement rules and argue that their bets should have paid off.
That sounds like it would make one hell of a tech talk. I have a gut feeling many readers (especially lurkers) of this very thread would gladly watch the recording.
Common and/or various ways the two groups misunderstand each other, and how you help them to anchor to the underlying base concepts? Yes please. For example, we know that interest accrues over time, but we still use shorthand for the annual interest as a step function because it makes intuitively more sense.
While I agree, I think that's still incomplete. To me good comments have always been about "what is being done AND why".
Or to put it another way: to provide the necessary context for figuring out why a particular piece of code is written the way it's done. (Or what it's supposed to do.)
I'll drop in from the sidelines, with the massive track record of having written one (1) book.
The prestige probably isn't what you'd expect. Having an ISBN to one's name carries ~zero weight for the people that actually matter for your career (it may mildly impress some future coworkers in a decade's time, though). The real value of having written a book is that then you have written a book.
Having a publisher carries one extra benefit that was merely implied in the post: you get assigned a professional editor. If you're lucky (I was), the editor has a really good understanding of how to wield language and the lessons you get from the editing process are going to far outweigh any direct financial benefits. When I wrote mine, I had been doing freelance writing for a large IT magazine for nearly ten years - and as a direct result had been taught how to use written language as a weapon by a good number of old-guard journalists. The year I spent on the book project taught me a LOT more still, because I was assigned an editor who herself was studying (in a university) to become a language teacher.
The skills I picked up from that process are with me to this day, and ironically have been the single most valuable asset I have as an engineer and/or engineering leader. Being able to write well to a varying audience is a superpower. You also learn to appreciate professional authors, because what they do is decidedly not easy.
In the end my book sold well enough to earn out its advance, so I guess it was a non-failure for the publisher as well. I also picked up a lesson for all aspiring authors:
Writing a book is easy. You sit down by the keyboard, slit your wrists and pour it all out.
> Ultimately it was only used to install malware in the form of browser extensions, ...
Like any other MDM software.[0] Everyone who has been long enough in the infosec industry knows that MDM is fundamentally nothing more than a corporate-blessed malware and spyware package.
In the past 2-3 years the criminal gangs have realised that too. The modern form of socially engineered phishing quite often entices victims to install a legit MDM software package (eg. MS InTune) and hand over their device control for remote management. Why bother writing malware that has to fiddle with hooks to syscalls and screenshot capabilities when you have a vendor approved way of doing the same?
You've stumbled upon the same trade Matt Levine has been pointing out for a few months now.
If you're good at AI, you could get hired at a top-tier company for 1-2M annual comp, and expect to stay there for at most five (5) years. That's a maximum of 10M pre-tax, and you'd be still on the receiving end of employment gauntlet.
Alternatively you could spin up an AI startup, and get acquired for 75M+ in less than 2 years.
In less surprising news, Matt has pointed out a number of deals that look quite a bit like that throughout 2025.
Interesting. That sounds like the trade for a very credentialed AI person. For random hackers, it's a little different...
There's the job ($250K+ in a VHCOLA, and probably worthless stock options), or their own startup.
I'd distinguish the kitchen table bootstrap startup, from the courting funding and playing the VC game startup.
The bootstrapped startup lets you do whatever product or tech demo you can do, and only that, and then eventually you have to deal with M&A courtship.
The VC track startup, you have to focus on jumping through the hoops of all sorts modern VC investors throughout the process. And among their criteria will be things like what your socioeconomic class is, and which school did you go to, bro. But it's otherwise easy, because you just have to go through the motions and burn VC money and hit their milestones while the hype wave musical chairs music is playing, and worst case is that you're a serial entrepreneur.
Either kind of startup is valid, but bootstrapped could have you spending most of your time on actual AI product work, if you can scope it to be viable with your resources. But you have to work smart and energetically, and worst case is that you run out of personal and revenue money, and then have to do a bunch of job interviewing to beg for a job from the previous category of founder.
This reminds me of when YC seemed to be a response to the dotcom boom environment, a bit "by hackers, for hackers", to help hackers start Internet businesses. Rather than mostly only the non-hackers starting dotcoms (such as with affluent family angel investors and connections). Or rather than hackers having to spend their energy jumping through a lot of hoops, while dealing with disingenuous and exploitative finance bro types.
Humans are unavoidable optimists and (sadly) the only sustainable approach is to assume the worst of everyone.
Then when they eventually outdo even your worst expectations, you will be less disappointed by the gap between your original impression and the fresh dose of reality. I've adopted a motto that I could finally put words on about a decade ago. "You are not cynical enough."
Thats how Finland made it to one of the "happiest" countries. People just not expecting anything from anyone, so if by chance something is even slightly above the bare minimum, its been good.
Oddly enough I happen to be Finnish, and formed my view of the world during my first twenty'ish years in there. That view has served me well over the subsequent decades.
It's no surprise or secret that I have since left the country.
There is a surprising amount of important data in various Mongo instances around the world. Particularly within high finance, with multi-TB setups sprouting up here and there.
I suspect that this is in part due to historical inertia and exposure to SecDB designs.[0] Financial instruments can be hideously complex and they certainly are ever-evolving, so I can imagine a fixed schema for essentially constantly shifting time series universe would be challenging. When financial institutions began to adopt the SecDB model, MongoDB was available as a high-volume, "schemaless" KV store, with a reasonably good scaling story.
Combine that with the relatively incestuous nature of finance (they tend to poach and hire from within their own ranks), the average tenure of an engineer in one organisation being less than 4 years and you have an osmotic process of spreading "this at least works in this type of environment" knowledge. Add the naturally risk-averse nature of finance[ß] and you can see how one successful early adoption will quickly proliferate across the industry.
ß: For an industry that loves to take financial risks - with other people's money of course, they're not stupid - the players in high finance are remarkably risk-averse when it comes to technology choices. Experimentation with something new and unknown carries a potentially unbounded downside with limited, slowly emerging upside.
That's quite likely a workflow thing. If you are popping up new (transient) terminals frequently, then a ~400ms wait time for each adds up and makes the entire machine feel really slow. I'm willing to wait extra half a second for a new terminal -- once -- after I've changed my autocompletion configs (rebuild + rehash takes a while), but if I had to wait for that long every time I hit Win+enter and wait for the terminal to become active, I'd be irritated pretty damn quickly too.
You get conditioned to immediate responses pretty fast.
reply