Senior Software Engineering
[Keep] a very tight leash on this new over-eager junior intern savant with encyclopedic knowledge of software, but who also bullshits you all the time, has an over-abundance of courage and shows little to no taste for good code.
... and who charges you per line of code it writes
👏2
❤3🔥1😁1
Just learned that Mint has no apparent way to install fonts. You just gotta know how
I guess I just hate computers now
🤝1
"It's actually GNU/ECMAscript"
😁2
Cryptocurrency is so stable and viable
https://decrypt.co/344463/printing-money-paxos-mints-burns-300-trillion-paypal-stablecoins
https://decrypt.co/344463/printing-money-paxos-mints-burns-300-trillion-paypal-stablecoins
Decrypt
Printing Money: Paxos Mints, Then Burns $300 Trillion in PayPal Stablecoins - Decrypt
A fat-finger mistake, or a hack? Crypto traders are confounded after $300 trillion worth of PayPal's PYUSD was minted and then burned.
🤣1
Forwarded from AI Quesadilla (The Northstar✨ System 칠성들 AKA Ky)
AI is so smart y'all, just fire your software engineers and use LLMs instead
🤪6
Checkers.java
64.6 KB
Check this shit out. Northstar code circa 2010 (when Ky was 19)!
Especially look at the Computer Player code We wrote, starting at line 1000.
Definitely nothing like anything We would write these days, absolutely beginner shit… which is what makes it so interesting to look back on!
Especially look at the Computer Player code We wrote, starting at line 1000.
Definitely nothing like anything We would write these days, absolutely beginner shit… which is what makes it so interesting to look back on!
❤2
Here's a great free idea for how to use LLMs in your user-facing software:
Whenever you catch an error that you didn’t expect, and which isn’t localized:
Instead of telling the user “something went wrong“ with no other information…
Have a tiny local LLM evaluate that error against your source code,
try to figure out where the user input led to that error,
figure out whether or not the user can resolve that error,
and then give the user a nice full-text localized explanation of what happened and what they can do
Whenever you catch an error that you didn’t expect, and which isn’t localized:
Instead of telling the user “something went wrong“ with no other information…
Have a tiny local LLM evaluate that error against your source code,
try to figure out where the user input led to that error,
figure out whether or not the user can resolve that error,
and then give the user a nice full-text localized explanation of what happened and what they can do
❤2✍1👏1🤔1
people dreading Windows 11:
people dreading macOS 26:
You will lose your privacy, features will be forced upon you that you don’t want, it doesn’t run all your programs that Windows 10 ran, it’s extremely buggy and crashy, and deletes all your data
people dreading macOS 26:
It looks a little bit more glassy
💯1
The OWASP Top 10:2025 is out! New risks this year
https://owasp.org/Top10/2025/0x00_2025-Introduction/
https://owasp.org/Top10/2025/0x00_2025-Introduction/
🔥1