pd

3.5K posts

pd

pd

@pd96dev

Katılım Ekim 2010
4.8K Takip Edilen295 Takipçiler
pd retweetledi
sudox
sudox@kmcnam1·
sudox tweet media
ZXX
43
964
13.5K
349.5K
pd retweetledi
pd retweetledi
Тsфdiиg
Тsфdiиg@tsoding·
We are cooked
Тsфdiиg tweet media
English
23
134
2.7K
54.3K
pd retweetledi
Matt Pocock
Matt Pocock@mattpocockuk·
Skills should be: - Concise - Responsible for one thing, not multi-step - Composable - Progressively disclosed - Harness-agnostic What else? Or - what did I get wrong?
English
188
82
1.7K
126.3K
Thomas Klemenc
Thomas Klemenc@thomasklemenc·
Why does MarkText use a full GB of RAM to display an 875 KB file? And why does it take 5 seconds? In times of exploding RAM costs, I hope we start caring about efficient software again.
English
5
2
69
5.6K
pd retweetledi
David Fowler
David Fowler@davidfowl·
People that are building real things are all coming to this conclusion. You could argue that it’s because software engineers care about the code quality more than they should, but it’s really because if you don’t, you will get up with software that does not work well.
Lee Robinson@leerob

You might believe you should spend less time thinking about code because of AI. I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability. At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time. Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change. I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance. I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.

English
16
32
351
80.8K
pd
pd@pd96dev·
ZXX
0
0
0
19
pd retweetledi
Pirat_Nation 🔴
Pirat_Nation 🔴@Pirat_Nation·
Microsoft is reportedly reducing internal use of Anthropic’s Claude Code after its AI bills started exploding as employee usage rapidly increased. Some teams are now being pushed toward GitHub Copilot as the company tries to control AI costs. Uber reportedly faced a similar problem. Executives said the company had already burned through its entire yearly AI tooling budget by April because engineers were heavily using AI coding daily. AI coding tools are now being used for everything, and that level of usage creates massive compute and token costs when thousands of employees use these systems at the same time. Source: TomsHardware
Pirat_Nation 🔴 tweet mediaPirat_Nation 🔴 tweet media
English
181
322
3.9K
796.7K
pd retweetledi
pd retweetledi
Phil Eaton
Phil Eaton@eatonphil·
I wrote an article on epoll and io_uring basics through the lens of a simple HTTP file server written in C. Paywall has expired, give it a read!
Phil Eaton tweet media
English
8
82
822
37.6K
pd retweetledi
Lee Robinson
Lee Robinson@leerob·
You might believe you should spend less time thinking about code because of AI. I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability. At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time. Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change. I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance. I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.
English
259
524
4.1K
571.5K
pd retweetledi
Andreas Kling
Andreas Kling@awesomekling·
Working on replacing the crappy content blocker in @ladybirdbrowser with adblock-rust from @brave and the results are excellent! We'll ship with blocking off by default. You opt in and pick your own filter lists. We think that choice is yours, not ours :)
Andreas Kling tweet mediaAndreas Kling tweet media
English
19
16
528
23.7K
pd retweetledi
Gergely Orosz
Gergely Orosz@GergelyOrosz·
Meta laying off 10% of staff when revenue is at an all-time high, revenue growth is a beast (33% YoY!!), profits at an all-time high: just depressing These layoffs are not because Meta needs to lay off, but because Zuck wanted to lay off for whatever reason
English
232
294
4.8K
410.5K
pd
pd@pd96dev·
@JesseStojan I plan to buy it, is it worth it?
English
1
0
1
12
Jesse S
Jesse S@JesseStojan·
Alright, time to run some LLMs on this puppy! I do like the haptic feedback though, slaps different.
Jesse S tweet media
English
3
0
6
265
pd retweetledi
vx-underground
vx-underground@vxunderground·
Unfathomable banger
vx-underground tweet media
Français
45
798
15.9K
250.7K
pd retweetledi
Mitchell Hashimoto
Mitchell Hashimoto@mitchellh·
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.
English
291
778
8.9K
1.2M