Rid (@codesmear) header
Rid (@codesmear) profile picture

Tinkering 🛠️ with Elixir | Erlang | Ruby | Zig. Human figuring stuff out.

London, England
Joined June 2012
Photo by Rid (@codesmear)Photo by Rid (@codesmear)Photo by Rid (@codesmear)Photo by Rid (@codesmear)Photo by Rid (@codesmear)Photo by Rid (@codesmear)Photo by Rid (@codesmear)Photo by Rid (@codesmear)Photo by Rid (@codesmear)Photo by Rid (@codesmear)
Are there Elixir-lang developers in Nigeria at all? cc: @olucurious @StudioTobs @__arinze @Oukwuani @IyanuAdelekan @unicodeveloper
6
3
11
It’s refreshing to have access to, and be able to work with, a team of incredibly passionate and skilled (not to mention human) engineers, who want to break the code, and find bugs as much as you do. To be clear, machines (like the VOPR and LLMs) are great at exhaustively enumerating bugs, but these things are defense-in-depth: The principle is that you should always be adding layers, but never replace one layer with another. For example, don’t replace human review with LLM review, but rather add another layer as defense-in-depth. (The LLM should only be a canary, if it finds anything, you know your other layers failed, and you fix them and invest in them). At the end of the day, the most valuable software in the world is not valuable because of the “time” it took you to create, but because of the “quality” and value you added.
Apparently you're not allowed to do Deterministic Simulation Testing with GPT 6 Astra
9
10
1
119
4,201
Replying to @Cristiano
Congratulations on an illustrious international career. Legend ⚽️
1
11
Rid retweeted
Relive the nostalgia of playing the popular 90s bike-racing game where you can kick people and stuff roadrash.pages.dev/
1
19
3
19
972
3 months to lock in. Let’s see what I can conjure if I refrain from using this app for that period. Tchuss ✌🏾
1
1
65
Rid retweeted
Unfortunately, software engineering is dying. Lets check what is happening on many "developers" or "engineers": - no architectural design or analysis - no technical curiosity or understanding - no respect to the quality And the standard bar has been lowered from "excellent design, good and coherent implementation, comprehensive tests" into "I don't know shit about the design, I don't give a fuck about the codes, I don't care about tests, and Codex is taking care of all". That means the definitive degradation of quality, and predictable decreasing of user experience. When we don't care about the users, essentially, we are killing our industry. This is the red alert, and this matters to us as software developers, critically.
39
50
5
561
27,397
Excessive flattery often preludes treachery.
1
39
Replying to @haiseyah
I bought an mp3 player some months ago just to listen to radio shows 😅. I’ve been enjoying it.
13
Seest thou a man diligent in his business? he shall stand before kings; he shall not stand before obscure men.
1
44
You’re paying to solve the same problem twice. Something goes wrong in an AI workflow. Someone fixes it. Then a similar issue comes up later, & the team has to figure it out all over again. We’ve been thinking about why that happens & what to do about it.
1
4
1
5
74,032
He's back @JulianAssange
2,568
14,165
1,318
94,716
20,614,292
The usage of AI for writing documents, especially product specs without an explicit declaration is slowly becoming a pet peeve of mine. There’s something about it that irks me.
3
1
3
363
Replying to @ms_pelz
😂😂
11
Qinwen Zheng, what a game
78
Replying to @ms_pelz
I read it every November 😅
1
17
It's always Arsenal are beatable until it's time to beat us
94
2,826
45
17,152
160,967
“You wonder if you’ll ever find your dreams?”
50
Beware people obsessed with outcomes instead of building outcome machines. Its worse than ever with AI, but these people existed before. Short term results above all else, etc. Don't fall into the trap. Invest in building strong fundamentals, invisible supports, and outcomes flow like water. An outcome machine.
113
550
83
6,327
274,939