blank

@robynngarfield "i kNoW ThInGs aRe mOrE ExPeNsIvE NoW, bUt tHeY'Re nOt tHaT MuCh mOrE ExPeNsIvE." Ok Boomer.

When my husband and I were first married we were dirt poor. For date night we used to go to Costco and split those old wonderful chicken Caesar salads that were $4. I know things are more expensive now, but they're not that much more expensive. People just feel entitled to spend crazy amounts of money on unnecessary stuff.

@dreamsofcode_io My guess is it's going to be something like going to the gym. When (mostly) everyone was doing manual labor, no one needed to 'work out' in their free time. If AI is doing all the coding, you'll need to do deliberate exercise to prevent mental atrophy.

I’ve been getting back into coding by hand, specifically challenging myself to doing low level Rust, whilst streaming on Twitch. Skill atrophy is absolutely a thing. Kinda embarrassing how difficult the first day was. Second day was a lot better, but it honestly scares me about setting myself up for a future dependency by outsourcing these skills to coding agents. Maybe it won’t matter, but something inside me screams danger about the idea of paying a subscription fee just to be able to write code.

@coldopn @kilocode Great job on the stream today! Looking forward to the next one.

I'm going to build an entire e-commerce business on stream using @kilocode, 1 hour at a time, and the first session is tonight at 7pm EST I'll be building the storefront from scratch, designing the merch live, wiring up integrations with Shopify, and using KiloClaw to automate the boring ops stuff so I can keep building. From there, I'll scale it like a real business. If you've ever wanted to see a solo e-comm build go from zero to launched, this is that! luma.com/1ajrfm2u

@KingBootoshi This was almost word for word what I landed on building out my workflow. Only missing step is the /post-mortem to distill learnings and refine the setup for the next round. Just have to figure out how to sell myself so I can get one of those shiny new harness engineer roles lol

when I set up an orchestration flow using Claude Code to execute a very direct PRD with Codex agents, my runs take 3-4 hours to fully complete so I often have this running overnight because I've automated my entire prompt workflow I usually do first off you have to understand that creating and using agents are a form of alchemy. one wrong word/prompt/step and your output went from a God tier one shot to being absolute dog shit anyways my workflow i have agents do is research, scoping out the codebase, doing the actual implementation, then review. research/scoping code prevents hallucinations and induce a genuine understanding of the design and patterns set review agents will flag things that the PRD requested which got missed, or flawed bugs then the {manager agent} will handle spawning in these specialized sub agents per task. the main context window as a result of using subagents remain small, which lets it do a lot of managing to keep the entire workflow focused i'll often have a couple of these workflows running at the same time, because they LITERALLY take hours. so I just relax after setting off an army as a result, workflows like this mean I have one agent handling up to 16+ subagents throughout the whole sub process i also combine this with hard guards to enforce good design like eslint & custom rules, strict design patterns and a lot of foundational templates i've built for myself the last year a lot of what i do end up becoming skills so i'll literally /skill combo my way through a prompt to chain up a series of very detailed actions at the end of the full process, THEN i review the full PR and it's really easy for me to skim through the code this is absolutely not vibe coding, and instead taking engineering workflows i've fundamentally learned and automating the process with detailed agents there are levels to this shit. the smallest discovery could 2x the quality of your workflow. sometimes 10x, even more. you need to be open and keep exploring!

My typical day working in the new Codex Superapp

@thdxr I got into QAE / SDET work primarily to do this.

are there people out there who just want to refactor every day? just wake up and find the worst code and just chip away at it and clean it up wake up the next day do it again, infinitely improving things with zero external impact?

@roikfbuwgc254 Can confirm, I have never heard of these before reading this post.

マジかよ

@ai_saboru_tech Currently Shimarin

海外ニキに質問🙋 日本で好きなキャラクターは？ わからない人は、挨拶して！

@memeticsisyphus I had *one* math teacher give a passable answer for why they wanted me to show my work. "If you get it wrong, I can see what step you missed and help you fix it". I made the effort for them. Still had tons of bad teachers, but they made me appreciate the good ones.

Practicing pronunciation of a target language is important. Once your mouth has "learned" the correct patterns, these sorts of irregularities become natural. ひき is a good Japanese example, and "a" vs "an" in English is another. With enough practice, saying it "wrong" will feel wrong

小動物の数え方 1匹（1ぴき） 2匹（2ひき） 3匹（3びき） 4匹（4ひき） 5匹（5ひき） 6匹（6ぴき） 匹だけでも数によって発音が変わるの罠だと思う。

@tanuzou1027 Anime has a range of stories, characters, and perspectives that makes domestic media seem bland and monotone by comparison. Older generations just see cartoons and assumed "it's for kids", not knowing that things like Grave of the Fireflies or Ghost in the Shell exist.

前にロシア人が「日本のアニメはどれだけの人を救っているのか、日本人は知らない」ってポストをしていて、その中でロシア人やアメリカ人、他の国々の人もその意見を「その通りだ」って肯定していたんだけど… そんなに救いになるものなの？確かに日本のアニメは面白いものが多いけど、そんなにたくさんの人の心を救うものだったとは考えたことも無かった。

@Maguro_Maznaga Good answer, good answer!

タイタンフォール

@hoshizorarock After this arrest, how do you intend to prosecute once I've eaten all the evidence?

これはハンバーガーですがXで言語の壁がなくなった今はハンバーガーから世界中の人間と友達になれるツールになりました。 ですが私はチーズ警察なのでこれを食べる人は逮捕しなくてはなりません。

@TheBlademaker Chef's knife. I'd use it daily and need something better than my current Cangshan.

We’ll already have to give 2 away. Reply Bowie if you want the Bowie. Reply Chefs knife if you want the chefs knife. Will pick the winners as soon as I finish the blades. Will post progress.

@ankkala "just write the code" only works when the project is small enough to fit in your head. Treating it as an absolute would be like saying that no library needs the Dewey decimal system when you've never worked in a library with more than 1000 books.

this tweet is written in a funny way but is literally true and good programming advice instead of constructing a rube goldberg style system of objects, just write the code that solves the actual problem that you have

@jammaru_lab I've heard from colleagues that they've talked to new graduates that don't know git/VC. It's like going to school to be a chef and never learning to grocery shop, it's wild.

I feel the same way. Recently, with AI, it’s possible to build things end-to-end even while skipping over the fundamentals, for better or worse, so I think more students in Japan are starting to overlook those basics. I also believe that having a lifelong learning mindset is especially important for engineers.

27卒メガベンチャーエンジニア就活の技術面接を振り返って、一番焦ったのは非機能要件まわりの質問だった。 ・N+1問題を説明して、どう解消するか ・DBのインデックスをどのカラムに貼るか。その判断理由とトレードオフ ・ページが遅いと言われたとき、バックエンド側でどう切り分けるか ・GraphQLはRESTと比べて何が良くて、逆にどこが辛いか こういう質問って、正直かなり難しい。機能面は極論、仕様に書かれたロジックをつないでいけば形にはなる。でも非機能要件はそうはいかない。パフォーマンス、スケーラビリティ、セキュリティみたいな領域はケースバイケースで、表面的な知識だけでは答えきれなくて、実体験や深い理解がないと自分の言葉で話せない。 実際、自分もその場でうまく言語化できなかった質問がかなりあった。 学生でここまで考えるのは正直かなり難しいと思う。でもだからこそ、この領域までちゃんと考えている人は少ないし、実際に経験している人も多くない。毎回聞かれるわけではないけど、たまにこういう質問が来たときに、理解や思考の深さがかなり出る分野なんだろうなと思った。

@y_omori @jammaru_lab In my experience, private software isn't inherently any better than OSS. "Security by obscurity" is a comforting story ameteurs tell themselves to feel better. Getting feedback from strangers can be stressful, but you have to bear with it to be a successful professional.

@jammaru_lab @graffhyrum 「OSSはセキュリティに不安がある」という20世紀みたいな言説を現代に見る、これも「基礎軽視」でしょうか

@rhobotmeat @Rianstone Who is John Galt?

@Rianstone I am so fucking pissed that Ayn Rand was just straight up right about everything and Atlas Shrugged is only a slightly more cartoonish version of what is actually happening.

It's perfect game theory. "Either stop ruining my chances at prosperity or no one gets to have prosperity." It's a male emotion (anger) on the macro. This is probably why so many people are against it. And frankly, it works really well, and only stops working if people (read: women) don't think it's credible. Whether they don't find it credible because they have more force on their side, or have been safe for too long to accurately assess risk doesn't matter. It's most likely that people don't recognize the risk because things have been so good (for them) for so long. But yeah, where some see cascading failure, I see a warning shot. So if the people in charge are smart (they aren't) they'll recognize this for what it is. The Sea People are coming.