BlackSudo (@blacksud0) header
BlackSudo (@blacksud0) profile picture

Building @firewireio

Khartoum, Sudan
Joined August 2021
Photo by BlackSudo (@blacksud0)Photo by BlackSudo (@blacksud0)Photo by BlackSudo (@blacksud0)Photo by BlackSudo (@blacksud0)Photo by BlackSudo (@blacksud0)Photo by BlackSudo (@blacksud0)Photo by BlackSudo (@blacksud0)Photo by BlackSudo (@blacksud0)Photo by BlackSudo (@blacksud0)Photo by BlackSudo (@blacksud0)
stop 👏 storing
stop 👏 storing 👏 IDs
26
who even uses OpenAI models for coding?this is insanity 😂
36
lmao 😂
Real men manage their own memory
40
Damn! 😂
if this PHP vulnerability allows remote code execution, doesn't that mean we can use the vulnerability to auto-patch all vulnerable servers?
75
Holy moly, why use an agent to review PRs on github? just have your agents review everything locally and fix the findings before creating the PR, github PR reviews are for humans and CI is there to verify everything works
My take on agentic reviews. If you want best balance between cost and quality, don’t use the SaaS codex/claude reviewers. Instead… 1. create your own an agent, triggered by GitHub webhooks on PR raised or updated events 2. Give it company and architecture context. Any key insights that the SaaS reviewers would never have. 3. Give it risk guidelines and tell it to separate out nit picking things from those that should block PRs from merging. (Agent approves or request changes on GitHub PRs based on risk. This has the benefit that request changes on github block and coding agents have to address the risks before the PR gets through) 5. Probably goes without saying but the codex/claude agent still does the review just not via the SaaS service . As it stands today, you’ll get better results this way. Might even be cheaper but definitely will be better use of resources. A nit picking agentic code review can be worse than not having one at all . If you just want something off the shelf that ticks a box ignore the above and just use the SaaS reviewer as they aren’t inherently bad, just not great, yet!
39
AI isn’t optional anymore 🤝
🗞️ if your team is too busy doing their 'normal job' to experiment with AI, you're preparing them to be replaced ghuntley.com/replaced/ In this post, I guess this's the last time I'll say it. AI use is no longer optional if you wish to be employed. What follows is advice for current employees and hiring managers on how to hire in 2026 to source AI-first candidates.
48
The final boss of skill issues
Replying to @crertel
I didn't do anything. I asked two frontier agents to make the most of Elixir and this is what they came up with. Please do send a PR to speed things up! But also realize that it's not exactly extra points for Elixir if frontier agents can't find the magic "go fast" switches.
104
BlackSudo retweeted
TanStack Charts 1.0 is here 🎉 Small bundles, fast updates, and charts you don’t have to outgrow. Start with a line and see where it takes you, or just simply tell your agent to "use Tanstack Charts"! tanstack.com/charts
40
155
24
2,075
138,115
Grandpa with a skill issue
Sorry G, but calling Go “beautifully designed” is a immediate unfollow for me. We just have too different of perspectives on what that means. Math is beautiful. Go’s error handling is the least mathy thing ever in programming.
3
1
3
7,418
BlackSudo retweeted
Security will become a larger and larger function in software companies. Security is verification engineering (eg: “my code is probably memory-safe”), as well as capital allocation (“what surface should I throw most tokens at?”) For startups, it’s a challenge and opportunity. As the world’s paranoia grows given ever-more-sophisticated AI adversaries, how can you trust a 2-person-and-a-dog company? But conversely, given the dire state of global cybersecurity and increasing reliance on centralization, as always, there’re vast areas that small teams can now disrupt that I’m excited to invest in.
142
74
37
1,039
93,316
Kinda wild that this guy has never heard of go.dev 🤔
somebody should make a language that's good for systems programming, fast compile times, good concurrency, pretty simple mostly just gets out of your way, easy to distribute cross arch, very unfortunate that we all _MUST_ use rust all the time, maybe some day
233
True ✅
The current state of desktop operating systems.
59
Can confirm. It’s 100% a skill issue 😂
I've never had a case on any iPhone, I've never cracked a screen or broken the phone. People used to say "oh wait until you have kids." Well, I have a couple now, and one is 3. No problems, clearly a skill issue. No cases for me, using the device as it was intended by design.
2
342
BlackSudo retweeted
Hey ████, I think there is room for both. 1. Prototypes and other throw-away code can be treated as totally black box. If you’re going to throw it away anyway, and if the blast radius of it breaking is low, it doesn’t need to be perfect. 2. Production code written by Claude should have a higher bar than if it was written by a human. At Anthropic, we have many guardrails in place to make sure this is happening: lots of lint rules, lots of tests, Claude-driven end to end tests, Claude-powered fuzzers running daily, automated code reviews and security reviews, automated code refactoring, and so on. Without these, you can end up with a mess that is hard to maintain down the line. Luckily, the model makes it increasingly easy to do these well — run a few daily routines, use Claude Code Review, etc. Your job is to hold the bar on code quality. If Claude’s code doesn’t meet the bar, try: - Using the latest frontier model (Opus 5 or Fable 5.1) - Increase effort to high or xhigh - Invest in your CLAUDE.md and skills to succinctly teach Claude how to work in your codebase If all else fails, steer Claude more when you work with it, or have Claude fix accumulated debt and rewrite your codebase to make it easier to work with. Or, wait for the next model. Best, Boris
146
124
58
2,488
394,948
I've been running `/claude-api prompt-audit` when upgrading projects to Fable 5.1 and it's helped so much It goes through your setup (CLAUDE.md, skills, etc.), flags instructions the new model doesn't need anymore and proposes a diff. Also works if you don't use the API!
141
82
11
1,793
139,387
Hey @mattpocockuk, AI slop was already solved by codegen. Type-safe APIs, databases, and client SDKs — OpenAPI, Protobuf, sqlc, Ent, Prisma, Orval, etc. Let the model wire them together and focus on the actual app logic 👀
Starting to wonder if the smartest way to reduce slop is just to produce less code Force code review to continually reduce code while ALSO keeping cyclomatic complexity low Less code means less code to maintain, fewer bugs
2
5
15,015
Hey @theo, the T3-code repo is missing taskfile.dev
It's crazy how much the quality of PRs to T3 Code has improved after fine tuning the agentsmd/claudemd
2
735
BlackSudo retweeted
Congratulations to the champions of the @0xL4ugh CTF V5! 🏆🎉 🥇 𝟭𝘀𝘁 𝗣𝗹𝗮𝗰𝗲: P3AK 🥈 𝟮𝗻𝗱 𝗣𝗹𝗮𝗰𝗲: PwnSec CTF 🥉 𝟯𝗿𝗱 𝗣𝗹𝗮𝗰𝗲: 0xFun CTFtime Vote here: 👉 ctftime.org/event/3024/weigh… 💬 Connect on Discord: lnkd.in/dSWdjEWp Stay tuned for future events.
1
1
5
236
BlackSudo retweeted
We are excited to announce @0xL4ugh CTF 2025! Mark your calendars for December 19, 2025 ⏰ Join Now 🎉🏆 🔗 Sign up: ctf.0xl4ugh.com 💬 Connect on Discord: lnkd.in/dSWdjEWp 👥 Follow 0xL4ugh Team: lnkd.in/d-sGphZQ #CTF #cybersecurity #0xl4ughctf25 #ctfsd
3
1
213
BlackSudo retweeted
The ASU V11 CTF at Applied Science University was an incredible success! Swipe through to relive the best moments! 📷🔥 🔗 Scoreboard: asuctf.xyz 💬 Connect on Discord: lnkd.in/d3DMXv_m Stay tuned for future events. Happy hacking! ctf.sd
4
5
290