
trying to remember what it was like to code before codex
someone
221 posts

@secretised
Building https://t.co/KZIZZqggGi

trying to remember what it was like to code before codex


If you know what this is, we're automatically friends

Codex anywhere and everywhere, all the time. Now your Mac doesn’t have to be unlocked for Codex to use your computer. From your phone, Codex can securely use apps on your Mac, even when the screen is off and locked. #locked-use" target="_blank" rel="nofollow noopener">developers.openai.com/codex/app/comp…




Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored). If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update! I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it. Feeling pretty swell about this mentality with all the supply chain attacks happening.

hand writing rust just to feel smth life is good again

This defeats the whole purpose of watching an unboxing video

@github holy shit, how did the attackers find a large enough uptime window to get in?