761–770 of 1001 posts
This month I'm recovering from major surgery. I'm okay, it's something I've been waiting to get done for a very long time. I'm just bored in recovery and running out of my science YouTube backlog.
Mission: get startups access to senior & principal big-tech engineers at a 90% discount and without hemorrhaging equity.
The hack is that I'm tapping into a hidden supply of people hiding in plain sight: top engineers that are already full-time employed in big-tech with benefits who enjoy helping smaller startups, and, recently retired people who want something to do.
The name I'm using is Low Touch Advisor because we are selling what I call "low touch" help in the form of async Slack based guidance. By having access to senior people perfectly matched to your team's needs, you can use your actual engineers to do the hands on and majorly reduce the likelihood that a major rewrite is needed after 6 months of effort on new projects.
Basic model: - Our customer (an early stage company) pays $1,500 / month with no long term commitments to get async Slack help from a vetted senior/principal engineer perfectly matched to their needs - Of that, we ACH $1k / month to the engineer who provided the Slack-based help
Within the first 3 months of operating, I have $27k of monthly revenue booked in my sales pipeline.
So far I've done everything by hand but once I'm a bit further ahead, I'm going to look to begin automating this.
If you want to connect: https://www.linkedin.com/in/jonathanblockengineer/
Most of the work as of today is in a branch, can see the language spec at https://github.com/cretz/duralade/blob/initial-runtime/docs/..., and some samples at https://github.com/cretz/duralade/tree/initial-runtime/sampl....
May not amount to anything, but the ideas/concepts of this durable language are quite nice.
Bringing back the hobbyist self-made PCB workflow since it can be a headache to get designs back from PCBWay / JLC between customers, tariffs, shipping..get more quick to close the prototyping loop.
Here's a YouTube playlist of how to make PCBs at home for anyone who wants a deep dive. https://www.youtube.com/watch?v=Hm_JrACrmVs&list=PLWDQgxl-jH...
Basically an API wrapping a cyclic graph where rules govern the state transitions / graph traversal (i.e. rules around handing off work between agents and the associated review, rollback and human intervention escalation logic).
It's mostly just to teach myself about multiagent patterns and what blend of "agentic autonomy" and deterministic / human governance gets the best results with the current set of (Anthropic) tools available.
I don't really know what I'm doing w.r.t AI, but having 15 years of industry SWE experience (high-availability distributed systems and full-stack web dev) on top of a fairly-solid CS education I feel like I know what the results of a working system should be and I'm learning a lot about the AI pieces as I go through trial and error.
Generally it feels like there are lots of ways the next generation of AI-assisted coding workflows could work best (beyond just "AI helps write code", I mean) and the results will be as much about the tooling built around the AI bits as it will be the improvements in models / AI bits themselves (barring a theoretical breakthrough in the space).
Trying to figure out what my personal dev workflow will look like in the middle of this evolving landscape is what led to this project, very much a scratch my own itch thing.
I'm building a lightweight screen recorder for macOS. It supports lots of features you'd expect from a professional screen recorder such as ProRes 422/4444, HEVC/H.265, and H.264, capturing alpha channels and supports HDR. Frame rates from 24 to 120fps. Can capture system audio and mic simultaneously. You can also exclude specific things from recordings, like the menu bar, dock, or wallpaper.
No tracking, no analytics, no cloud uploads, no account. MIT licensed. Everything stays on your Mac. Still early, but happy to hear feedback!