You dont get 7% of a company, you get 7% of outstanding sharez. So its shares held * stock price. Usually there are less stocks issued at the initial stages with more coming in later as more investors are added. I dont think YC maintains 7% across all their investments.
From my own observations with OpenAI's bots, it seems like there's nuanced levels.
"Don't do that" is one level. It's weak, but it is directive. It often gets ignored.
"DON'T DO THAT" is another. It may have stronger impact, but it's not much better -- the enhanced capitalization probably tokenizes about the same as the previous mixed-case command, and seems to get about the same result. It can feel good to HAMMER THAT OUT when frustrated, but the caps don't really seem to add much value even though our intent may for it to be interpreted as very deliberate shouting.
"Don't do that, fuckface" is another. The addition of an emphatic and profane quip of an insult seems to generally improve compliance, and produce less occurrence of the undesired behavior. No extra caps required.
Distribution is king. Kudos to Ramp for that. My weird thesis is that for whatever reason Ruby on Rails shops just seem to survive more. I wonder if someone did a stack specific survival rate analysis.
Thats because getting promoted requires thought leadership and fulfilling AI mandates. Hence the tweet from this PE at Google, another from one at Microsoft wanting to rewrite the entire c++ base to Rust, few other projects also from MS all about getting the right Markdown files etc etc
It works for me but I do it incrementally. I use codex. I ignore the hypesters because I was around the last time self driving cars were just few quarters away.
What I do is - I write a skeleton. Then I write a test suite (nothing fancy just 1 or sanity tests). I'll usually start with some logic that I want to implement and break it down into XYZ steps. Now one thing to note here - TDD is very useful. If it makes your head hurt it means the requirements arent very clear. Otherwise its relatively easy to write test cases. Second thing, if your code isnt testable in parts, it probably needs some abstraction and refactoring. I typically test at the level of abstraction boundaries. eg if something needs to write to database i'll write a data layer abstraction (standard stuff) and test that layer by whatever means are appropriate. Once the spec reaches a level where its a matter of typing, I'll add annotations in the code and add todos for codex. Then I instruct it with some context, by this time its much easier to write the context since TdD clears out the brain fog. And I tell it to finish the todos and only the todos. My most used prompt is "DONT CHANGE ANYTHING APART FROM THE FUNCTIONS MARKED AS TODO." I also have an AGENTS.md file listing any common library patterns to follow. And if the code isnt correct, I'll ask codex to redo until it gets to a shape I understand. Most of the time it gets things the 2nd time around, aka iteration is easier than ground 0. Usually it takes me a day to finish a part or atleast I plan it that way. For me, codex does save me a whole bunch of time but only because of the upfront investment.
You personally should just ignore the YouTubers most of them are morons. If you'd like to checkout AI coding flows, checkout the ones from the masters like Antirez, Mitchell H. Thats a better way of learning the right tricks.
If theres ever launch an enterprise version, I'll push for this product to be adopted across the company. And what a phenomenal name. Also a huge fan of k9s myself.
I'm not sure what an enterprise version would look like. I don't have any plans to ever charge for the app, so it'll never be "enterprise" in that regard.
I also like k9s! That team created a really great product for people who want to TUI.
Thanks for the compliment on the name. It's been literally the most polarizing thing about the app. More people comment on the name than on anything to do with how the app actually works, lol. I don't know whether that's a good thing or a bad thing. Probably both. :)
reply