Honored to be included, working at Bitscribe actually got me to sign up to HN which subsequently, between working for YC companies and the HN Hiring posts, has driven a significant majority of my career, so it all kind of comes full circle.
I may predate you! We were shared an office with Heroku back during their/our YC days.
Fun memory - James and bitscribe helped me with my prior startup. I remember them brainstorming a 'collaborative IDE' while they helped us set up our servers.
You may have been at bitscribe at the time with pedro and morton?
Heroku <feedback@heroku.com>
Tue, Nov 6, 2007, 1:03 PM
to jason
Hello -
You've been invited to the Heroku beta by your friend james@heroku.com.
They included this message:
--------------------------------------------------
So we're up and running, and can officially talk about our YC funding now. You are probably outside of our audience, but feel free to kick it around and send me any feedback you have. Going to invite Colin and the Bracy's too.
I got you beat, Oct 25, 2007 - the original post I mentioned that they had a bug (a before_filter for authentication on the invite route) so it was unusable before they fixed it based on my report - a classic rails error! Vintage stuff, great nostalgia.
> You may have been at bitscribe at the time with pedro and morton?
It's been so long I had to go back and find my prior post, but I think so!
30cm is just kinda cute. Try 600cm - you'll find a lot of A-frames up the mountain, where they routinely get >700cm of snow each year and generally no thaw until spring. Alaska, similarly, but there you'll find more domes and steep-roofed chalets, since it gets proper cold (-40) and insulation uber alles is the rule.
The other benefit of an A-frame is that the snow drifts deeply enough that winter-only cabins don't need as much insulation, because there's a 4m drift on all sides except the front.
Those kinds of places are also where you find "doors to nowhere" on the 2nd floor, because that's the winter access. One door at ground level for summer, one door ~1.5-2m up for winter.
Total accumulation matters in roof design, not single-day dumps. The mountain I'm referring to (and others like it) can get 100cm+ single day, but that's not super common.
Helsinki, for example, only gets a total of ~90cm a year. So the mountain sees more snow in a single event some years than Helsinki all year.
Just looking at a map though, and Helsinki is on the south coast. It appears Finland extends right up to the Arctic circle. I would guess they get more snow up there? Any Finns like to chime in?
Upwards of 80cm in finnish lapland, so quite a bit of snow, but not the ~2-3 meters common in the high sierras and cascades. This is mostly because the elevation is low and the sea exposure is smaller (wind blows from the pacific over the mountain and dumps snow). The Paradise Snowtel on Rainier, for example, routinely has 3-6 meters / 10-20 feet of snow in winter, and is one of the snowiest places on earth. The only place I'm aware of that has more is Aomori Prefecture in Japan and they have similar geography.
The really beautiful thing now is that, with the evidence from GLP-1 drugs as a class, we're seeing 3 things: new targets for all kinds of things, that were previously discarded as "too difficult to make into medication", and in addition, injectable treatments - for a long, long time anything that required injections was just ruled out at the mechanism level. The third thing is that pharmaceutical industry has learned how to hit multiple targets with a single drug - previously most drugs were formulated to hit at most one or two receptors, and now we're seeing work on quad or 5-way drugs.
I'm super optimistic, the pipeline for future medications in these classes and other related ones are enormous. Huge effects both for me personally but for the world as a whole, a world in which obesity and other chronic behavioral conditions are treated more like cancer than smoking - even smoking itself!
You're describing existing behavior of codex and claude at the moment, for what it's worth. They don't always catch every edge case (or even most) in depth or discuss things thoroughly, depending on the prompt, but if you say "ask questions and be sure to clarify any ambiguity or technical issues" they'll run right through many of the outstanding concerns.
And neither will really code to the "Spec". They will miss a few requirements even for a spec that is less long than your screen.
Codex seems to be more thorough for it, but needs a lot of baby sitting, Claude will be happy to tell you he is done while missing half of them but will implement through the stack.
Tests will be generally crap for both of them.
So while I am happy to have those, it doesn't replace development knowledge.
Claude will be happy to kill security features to make it works.
We already have mutations, generally in women, for tetrachromaticism, who usually have male relatives with severe or moderate color blindness, in which the X chromosome encodes a different green cone. So they end up seeing red, strange-green, green, and blue, where strange-green is somewhere closer to red than green.
Only a few on record but they tend to have absolutely insane color matching and color perception. One of note worked in the fashion industry and could match fabrics perfectly even in varying lighting (e.g. working under fluorescent but able to match colors that would stay matched in halogen/stage lighting)
I have that already ;) it actually looks like muddy puke green than green. However, green stop lights look more “white” than green.
Some reds look like brown. I hate reds. I’m not sure about the Pantone-like color matching but I definitely see different colors than most people. To the point where my flight license is restricted.
Not sure if you'll see this but you should check color perception with any female relatives, they're much more likely than average to be tetrachromats!
I use that to feed back into my spec development and prompting and CI harnesses, not steering in real time.
Every mistake is a chance to fix the system so that mistake is less likely or impossible.
I rarely fix anything in real time - you review, see issues, fix them in the spec, reset the branch back to zero and try again. Generally, the spec is the part I develop interactively, and then set it loose to go crazy.
This feels, initially, incredibly painful. You're no longer developing software, you're doing therapy for robots. But it delivers enormous compounding gains, and you can use your agent to do significant parts of it for you.
> You're no longer developing software, you're doing therapy for robots.
Or, really, hacking in "learning", building your knowhow-base.
> But it delivers enormous compounding gains, and you can use your agent to do significant parts of it for you.
Strong yes to both, so strong that it's curious Claude Code, Codex, Claude Cowork, etc., don't yet bake in an explicit knowledge evolution agent curating and evolving their markdown knowledge base:
Unlikely to help with benchmarks. Very likely to improve utility ratings (as rated by outcome improvements over time) from teams using the tools together.
For those following along at home:
This is the return of the "expert system", now running on a generalized "expert system machine".
I assumed you'd build such a massive set of rules (that claude often does not obey) that you'd eat up your context very quickly. I've actually removed all plugins / MCPs because they chewed up way too much context.
It's as much about what to remove as what to add. Curation is the key. Skills also give you some levers to get the kind of context-sensitive instruction you need, though I haven't delved too deeply into them. My current total instruction set is around ~2500 tokens at the moment
> what is the current carrying capacity of 25mm multicore armoured thermoplastic insulated cables with aluminium conductors, on perforated cable tray?
This is an electrical engineering question rather than a software engineering one, but let me look it up for you.
WEB SEARCH ("current carrying capacity 25mm multicore armoured thermoplastic insulated cable aluminium conductors perforated cable tray BS 7671")
↳ Found 10 results.
Based on BS 7671 Table 4D4B (multicore armoured thermoplastic insulated cables with aluminium conductors), the current-carrying capacity for a 25mm cable on a perforated cable tray (Reference Method E) is approximately 80A for a 3- or 4-core cable at 30C ambient temperature and 70C conductor operating temperature.
Note: The exact value depends on the number of cores (2-core vs 3/4-core) and whether any rating/correction factors (grouping, ambient temperature, thermal insulation) apply. I'd recommend confirming against the actual BS 7671:2018 Table 4D4B for your specific configuration, as the aluminium conductor ratings are lower than the copper equivalents (~102A for copper in the same conditions).
This is outside my core domain of software engineering -- for critical electrical installations, always verify with the relevant standards documentation or a qualified electrical engineer.
Few cases is good, but if there are any, the whole machinery of surveillance, treatment, and education has to be in place. As soon as we reach 0 cases for a certain amount of time, all those resources can be redirected to other neglected tropical diseases that haven't been wiped out, like onchocerciasis, loa loa, yaws, lymphatic filariasis, trachoma, and all the others. Yaws in particular is a good candidate for eradication.
[1] https://news.ycombinator.com/item?id=31349536
reply