1,281 karma · joined March 19, 2013
Happy to chat. Ping me on marty [at] orbitalhq dot com
[0]: https://gist.github.com/martypitt/0d50c350aa7f0fc73354754343...
BUT (and it's a big but), it adds a second axis of subjectvity. Already, I'm out there talking about a thing which I think is "interesting" and "worthy" subject matter of other peoples time. Now, I'm adding "and is delivered in an entertaining way".
For me - that's humour - both in the delivery, and in the slides I show. But - like anything - it doesn't always land.
And, when it doesn't -- it's a very very long awkward talk. I've been on speaking circuts where a conference goes to multiple cities (same country), and the talk went down very well in one city, and bombed in another. Things like timing matter (after lunch sucks).
Also, The author lists the requirements as "inform, educate and entertain" -- and I'd add -- "in that order". I've cut things from my talk because they were funny (IMO), but ultimately didn't support the content of the talk enough. After all -- This is a tech talk, not a standup routine.
All three are very hard to do well -- but I do agree with the author in that's it's the speakers job to do all three.
Just FYI - There's a pretty popular (in finance circles) JVM library called Chronicle[0], which also deals with high throughput event queues etc.
- Shorter support windows, with longer support available for purchase (VMWare actually introduced this, but Broadcom can weaponize it)
- Then Enterprise Spring, which has additional features
- Then some other license shenaningans.
Hazelcast recently made the move where CVE security updates are only released into the OSS ecosystem quarterly - whereas the enterprise model gets them as soon as they're ready. In OSS, you have to rebuild and patch yourself.
That's a special kind of evil, which has Broadcom DNA all over it.
Sadly, it feels like an inevitability at this point.
Love it.
That'll truly give the efficiency that these employers crave - let's both speak once our AI counterparts have deemed we're a match.
Same concept, but the tldraw team delivered something with a bit more personality.
However, it boils down to "Don't advance technology, wait 'till we fix society", which is futile - regardless of whether it's right.
https://en.wikipedia.org/wiki/Chief_Mouser_to_the_Cabinet_Of...
Reminds me of a similar project years ago that was doing the same thing - they ultimately struggled with monetization and folded (I forget the name) -- however this one is MIT OSS, so I'm guessing that's not a key concern right now.
Note that your "Built with the Isoflow library" link at the bottom to isoflow 404's to https://github.com/isoflow/isoflow
Given these existence of these tools, which are fantastic, I'm often stunned at how sluggish, expensive and how lacklustre the UX is of the AWS monitoring stack.
Monitoring quickly became the most expensive, and most unpleasant part of our AWS experience.
How did you get VS Code embedded in your app? I'm aware of projects like Monaco, and that vscode.dev exists - so it's clearly possible - but I didn't realize it was something others could build upon?
Again, kudos!
JSON superset, optional quotes for keys, sensible string handling, comments, automatic env variable handling, variable references.
It's not perfect (all sufficiently powerful configuration language has quirks), but I love it.
Congrats to everyone.
People are scurrying to release MCP servers, and there's been a flurry of them put out - but it feels like we've skipped straight to the advanced tooling, on top of a stack that might not have found it's footing (yet).
I understand MCP, the problem it solves, and why it seems a good idea ... but outside of toy applications, are they proving to be useful?
> Claude Code keeps doing stuff. It keeps solving massive problems, one after another. I throw larger and larger things at it, and it is unfazed. Chomp. Chomp. Chomp.
Can you clarify the slack integration? I see you've mentioned it, but I'm unclear on the workflow.
A use-case I've thought about previously is support discussions we have on our slack channel, which indicate that we need to update our docs.
Is Promptless able to raise a PR with suggested updates on docs, based on question/answers in our support channels?
I'm curious how commodotized the underlying LLM's are for generating this type of code? (And thereby, how big the moat is for companies like vercel/bolt surrounding v0 et al).
What models are you using to power the code editor? Did it require much customization?
Is it likely that enterprises would be able to eventually bring their own LLM's, or does the training make that prohibitive?
I especially like that you're prepping them very clearly in advance, giving them every opportunity to succeed, and clearly setting a tone of collaboration.
In person design and coding challenges are a pressure cooker, and not real-world. However, giving people the choice, seems like a great way to achieve the balance.
Honestly, I'm really just commenting here so that this shows up in my history, so I can borrow heavily from this format next time I need to interview! :) Thanks again for sharing.