- Quoted phrase in the opening sentence
- Opening quote: “no longer supported”
- Quoted phrase in the opening sentence
- Opening quote: “Tiny”
Used phones are good for tinkering, especially for "display with sensors and battery attached" usecases, but there are still plenty of downsides. And unfortunately Linux on phones is just not ready for primetime, last I checked.
I can relate to that. But as I’ve aged I’ve appreciated just how much was done with less back. I mean that literally: we couldn’t afford a computer so my dad would haul home his work computer each weekend. We’d call BBS’ on it, print stuff. Play shareware games. It pissed my mom off because it took up half the dinner table. But my brother learned to code this way too.
So later on when my friends got EGA and VGA, CGA meant “poor.”
Fast forward many years and I have kids and were in better financial circumstances than my dad and mom back then. My kids have MacBooks. One of their friends was over one night and was visibly embarrassed that all she had was the school assigned Chromebook. She and my daughter were doing homework and her friend said that she wished her family could afford better laptops.
I didn’t want to embarrass her but then next morning after I made pancakes and I was sitting at the table I was like hey let’s take a look at these Chromebooks (we had an old one sitting around) and the three of us sat there and in about an hour and a half they’d put together a very simple farm game in the spirit of Stardew Valley on PICO-8.
Point being, we live in a world where especially with AI, it’s easy to think we can do everything. And it can feel like that, which means that when you can’t, you feel worse that you can’t because it would appear everyone else is doing amazing things with no limits.
But maybe we need more limits on things. Maybe that 4 color palette forced devs and artists to be creative back then in ways that make things better for everyone.
- Quoted phrase in the opening sentence
- Opening quote: “cold”
Respect for the graphics artists in general for that time to be able to make something out of almost nothing, four colors or less and/or black and white low resolution.
- Be able to analyze a situation into processes and discrete steps
- Be able to describe the actual (!) problem you want to be solved
- Be able to describe how to verify that the problem is actually solved
- Be able to ask the right questions regarding HOW the problem has been solved in order to gain understanding and to identify the next steps and improvements
- Be able to identify when the AI gets stuck or down a rabbit hole and to guide it out of there.
- Understand what LLMs are good at and what they are not good at. And there are tons of things they are not good at.
Disclaimer: This is absoluty not based on any scientific study or so :-) Just my personal experience! Feel free to disagree.
But my experience comes directly from my work: I have a lot of customers on my platform that are not engineers, but make use of AI to solve business problems through automations. Nearly everytime when they are stuck (or burning through a sh*tload of tokens in no time), it is because one of those skills aren't present. So I try to teach them more and more how to "think like an engineer". And often when it lands, they become much better at using AI in a very short time. The best learners are often those that already had some kind of engineering background.
Now granted, the frontier models can help themselves pretty well and often can produce amazing results with very bad input. But they are also expensive. If you work with less-than-frontier, those skill requirements become very salient again. And thats what we do. We mostly work with models like Deepseek flash or GLM Flash or even local ones like Qwen3.7 .
Most people, even technical people, can't imagine being 90 years old and being indistinguishable visually and in terms of mental capacity from a 20-year-old. They imagine decades of suffering with bone aches, diseases and dementia... even technical people who should know better that when you optimize a system that's full of technical debt, it's almost all upside.
I'll have plenty to do and plenty to think about when I'm 100 years old, assuming I have a body and brain capable of it.
"Yes, but what about all the people you'll have lost by then?"
First of all, if I get to live a long and healthy life they probably do too.
Second of all, we adapt. It's not all sunshine and rainbows, but getting to live for as long as you want, as healthy as you want, is worth the grief.
I know you might respond "we know they have done iffy shit before, therefore worst interpretation is warranted here."
But, well, as I said - we can do that line of reasoning about anything, but our discussions kind of break down at that point - we're just throwing down impressions and "could be's".
- Quoted phrase in the opening sentence
- Opening quote: “weeks”
Don't over-index on this choice of words. LLMs can just as easily generate a diff that removes or refactors code, they don't have any intrinsic "preference" to always add more code, unless it's been trained into them.
A lot of the early training had concentrated on "wow factor" one-shot style demoable use cases, where the models indeed ended up with a tendency to assume they were in a "produce something new for me right now" situation and often or always started churning out additional code, even without all relevant information. As training regimes improve, and as customer demand evolves, this is changing, and the latest big models place a lot more emphasis on maintenance tasks - still not enough, but it's at least in the mix. As they mature, I'd expect the models' "instinct" to gradually align with what everyone's idea of a senior software engineer is, taking time to figure out if they can simplify and refactor rather than always adding more.
It's a new field, it will take time to get it right, but I don't doubt it will eventually be right.
> Because they are trained on mediocre code that is the vast majority of what's available on the internet
Again, this is outdated. It's true that the earliest training took this "spray and pray" approach, but data quality filtering is now a huge focus and the labs have made a lot of effort (and progress) in figuring out what good code is and getting the models to follow that. They've massively improved, in my experience, and it'll only get better. Again - give it time, this is new.
- Quoted phrase in the opening sentence
- Opening quote: “magic number”
For example, DJ Delorie's djgpp project, built in 1989, was how I got into "real" programming on MS DOS.
For industries that serve customer bases that are down-cycled on weekends, the dominant effect is "Deploy on Friday to minimize customer disruption chance."
For industries that operate with a 24/7 uptime expectation, the dominant effect is "do not deploy on Friday so you don't have to pay for your expensive software engineers pulling extra hours on a weekend. Much better to have disruption while the folks most qualified to fix it are in-house and alert."
- Ordinary term used more than once in the same comment
- “overload” appears 2 times
There's an unverified mention of a fiber cut, which might result in fewer circuits being available. That usually returns an "all circuits busy" signal.
None of the explanations will make sense until they stop coming from unqualified political appointees.
- Quoted phrase in the opening sentence
- Opening quote: “obsolete”
I think the problem with a lot of the push to "modernize" is we forget the legacy system has been real-world tested for 40 years now. It's the new stuff that needs to prove itself in terms of stability.
- Quoted phrase in the opening sentence
- Opening quote: “you have a second backup?”
I wouldn’t say anything but this is approximately the only time in my entire life this scene will be relevant.
- Ordinary term used more than once in the same comment
- “end of the week” appears 2 times
- “end of next week” appears 3 times
I worked for a person who had a fixation on "neat" deadines: the "first of the month", "the end of the week", "the start of the quarter", etc. It'd be one thing if the dates were tied to legal compliance (tax filings, etc), but that usually wasn't the case. They were chosen because they were "tidy".
I'd time meetings looking to maximize time for work. You try to meet late in the day Wednesday because an early Tuesday meeting might get an "end of the week" deadline. A late Wednesday meeting was more likely to garner a "end of next week" deadline. Meeting Thursday or Friday guaranteed an "end of next week" but you lost Thursday and Friday work time. Wednesday was a gamble, though, because it was still early enough to get you an "end of the week". Meeting after lunch helped with that.
You always had to be aware of the numeric calendar day, though. Gunning for an "end of next week" deadline when next Wednesday was the end of the month (or worse, end of the quarter) almost guaranteed you an earlier deadline than you wanted.
All of this deadline-setting happened with little regard for the amount of time work was going to take.
It was immensely fun, when setting a deadline in this person's absence, to get a group to agree on a mid-week deadline. You could see it make this person's skin crawl hearing that the work would be done on Tuesday or a Thursday.
(They also own a small number of private VHF stations for relaying company messages to air carrier operations domestically, but these aren't used for ATC purposes.)
Otherwise, the VHF radio links are operated directly by FAA TechOps.
L3Harris owns the telecommunications backhaul between facilities.
You'd say "Valid from the thirteenth at two zero five three zulu" over radio.
Looking at LAX departures, it looks like nothing has departed since about 10:30 AM PST, and everything later is showing Delayed or Cancelled. There are times after Delayed, but it's not clear those times mean anything. Some are now in the past.
"flysfo.com" is too overloaded to display departures. Stuck at "loading...".
JFK departure status shows almost solid "Delayed".
No good explanations anywhere.
- Quoted phrase in the opening sentence
- Opening quote: “centers”
https://www.nbcdfw.com/news/tech/a-calamity-disrupting-hundr...
Update: Starship launched on schedule.
edit: https://www.fly.faa.gov/ois/oisedit/adv_oisedit_dis?number=1...
> "We see individual elephants leaving and possibly dying at accelerating rates, but new individuals are not coming into the population,” said Madsen. “With fewer individuals in the population, those who are left will naturally have fewer relationships. However, the remaining elephants are also changing their relationships with each other."
In my opinion "dying at accelerating rates" is the/a key takeaway. Notably climate change doesn't seem to be explicitly mentioned and hate to see poaching be a direct cause:
> Many elephant populations are already impacted through deaths resulting from poaching and conflicts with humans. Other contributing factors may be disruptions in habitat connectivity and less food available...
Other comments mention other intelligent and social species and this reminds me of Puget Sound Southern resident killer whales [0] and their decrease in food availability and offspring viability.
[0]: https://www.nature.org/en-us/about-us/where-we-work/united-s...
- Quoted phrase in the opening sentence
- Opening quote: “Monomaniacal perfectionism.”
One day, Ron (a hardware engineer from Xerox) gave a talk about the theoretical performance of an Ethernet file transfer. He calculated the end-to-end latency and data-rate including disk latency, network latency, the number of clock cycles necessary to send and receive the data, etc.
He had (overhead projector) slides that showed all his assumptions and calculations. Finally he displayed a slide with a graph showing this theoretical maximum, the actual performance of the 3Com network stack, and (IIRC) the Novell stack. As I recall, actual performance was about an order-of-magnitude lower than the theoretical max.
His point wasn't that our software division should be able to achieve the theoretical max. It was that if we (for example) got halfway there, we would know that Novell would never ship software that was twice as fast as ours.
He was very nice and scholarly about it and did not mean offense. I and many others weren't offended. But a surprising number of people were.
I'm sorry to hear that he passed.
I was on the Macintosh network os client team. For whatever reason (maybe he was annoyed that Apple copied so much from Xerox) Metcalfe didn't like Macs. In this era Macs used Apple's proprietary AppleTalk/LocalTalk network. We did a demo for 3Com execs using a large external monitor connected via a single black coax cable that looked just like thin-ethernet. He got excited for a moment and came right over to look at the Mac and was very disappointed to see the cable attached to a display! (3Com was working on Ethernet cards for Mac at the time but they weren't ready at the time of this demo.)
For those too young to remember: there was an SF Bay Area baseball park known as Candlestick Park that was briefly branded "3Com Park" -- to the great annoyance of SF Giants fans. During one interview he as asked if in the early days of 3Com he would have done anything differently. He said, "I would have named the company 'Candlestick'!"
- Quoted phrase in the opening sentence
- Opening quote: “special military operation”
contrary to popular belief, DNS doesn't actually need 24 hours (or whatever) to "propagate". It only needs enough time for caches to expire, if they exist. For non-existent domains this shouldn't be an issue.
Quite a bit was changed between "illumos bhyve" and FreeBSD upstream. We in illumos decided to take a slightly different approach in how we approached the machinery for saving/restoring the state of devices emulated in-kernel, which is a necessary part of doing such a live migration. FreeBSD was first to add that functionality, but we (I) felt it exposed too much in the way of implementation details from that device emulation, rather than a more abstract model of the emulated hardware. It was at that point that illumos "soft-forked" the kernel VMM component so we could take a different approach. While the two kernel VMM components are very similar, and much of the bhyve userspace emulation (a counterpart to propolis) will run on either OS, there are some key differences around instruction emulation and those kernel-emulated devices which prevent them from being drop-in replacements for each other.
All that said, I'm happy to see FreeBSD making progress on this front. They've been a friendly peer in this space, and both projects benefit from efforts in this area.
I can only speak for myself but I use the CLI and TUIs specifically because of the limitations those modalities impose on software that uses them as the primary method for interfacing with the end user. If you want a full featured UI and all that comes with it why not just use QT or GTK or modern HTML or etc?
I think the only "improvements" I'd like to see are thing such as metadata regarding what the different streams are for, an official way to communicate using structured data as opposed to raw bytes, that sort of thing. Spiritually in the same ballpark as the difference between HTML before and after CSS.
1. Log in to OKTA and choose my specific account (we have 2 accounts for some reason, and only one of them is used for development) 2. Log into AWS with that account 3. Select another sub-account in AWS 4. Navigate to my developer EC2 5. Start the instance 6. In VS Code, open a terminal and log in with “aws login —profile myName” 7. Wait for redirect to AWS in the browser window 8. Click ok and close the tab 9. Back in VS Code, open remote explorer and click on a preset that does an ssh tunnel to my workspace on the EC2 10. Wait for VS Code to spawn a new window 11. Now I can go through all of my other development setup tasks (another 6-10 steps depending on what I need to do)
Every day. And our instances force auto-shutdown at 9pm, so if you need to work late, better save your work, log off preemptively, and go through the same process.
- Quoted phrase in the opening sentence
- Opening quote: “data surveillance”
- Ordinary term used more than once in the same comment
- “login” appears 2 times
- “Confirm” appears 2 times
1. Tap "login", taking me to the login page.
2. Tap the "login" button on that page.
3. Sign in using 2FA. (A few more taps, but I'm not counting that against the portal).
4. Tap "Redeem Parking Permit"
5. Tap "Redeem use of Permit Pack"
6. Tap the car that I used that day (which is always the same car)
7. Tap "Confirm"
8. Tap the calendar icon to open the date chooser.
9. Tap on today's date (why isn't this the default?!)
10. Tap "Confirm"
11. Tap "Complete"
After a month or so at being annoyed by all of this unnecessary friction, I had Claude write an iOS app that keeps me logged into the parking portal. Now paying for parking requires just a single tap in my custom app. It also shows me a widget, telling me whether I have already paid or not.
I've built a lot with Claude this year, but that simple tool might be the one that brings me the most happiness.
- Quoted phrase in the opening sentence
- Opening quote: “Clever”
A spokeswoman for the National Weather Service said a screenshot circulating online that claimed its weather radar was down was “outdated.”
The Weather Service “has not experienced a disruption to its radar systems today,” said Kim Doster, the spokeswoman.
- Quoted phrase in the opening sentence
- Opening quote: “pixel-art-styled?”
- Quoted phrase in the opening sentence
- Opening quote: “the global North”
If people's MS subscription revenue were funneled into on-site devs and devops for open source solutions, we'd all live in a better world. Sure, the money wouldn't be funneled to a single ledger in Redmond, but the overall productivity would be higher and there'd be greater GDP growth in other areas.
I've heard of so many small companies with a slightly technical bent replacing their SalesForce with better CRMs that make everyone happier, thanks to AI. MS is next.
Let's make sure that dollars get funneled away from economic rent and into more productive efforts. Schumpeterian rents might exist for a bit, but they should never exist long. Microsoft's rents have lasted for too long to be economically optimal.
While probably harder to find a no-questions asked buyer, the price premium on GPUs is a lot higher than some consoles.
If it is true that eventually a general approach that scales with compute/data will supersede a bespoke expert solution, it is not necessarily true that today's expert solution should be thrown away at the first sign of a data-driven model.
It says nothing about what you should use today to build things, it says everything about how you should do research that lasts.
If you're building for billions of users in 10 years, sure go with whatever you think is the bitterest.
But if you're building for right now, you probably mashup whatever works best. That might still be a PID loop, EKF, and Homographies sometimes. But when you hit the frontier of what "works", then you have to reach for new things anyway.
Chesterton's baby/bathwater
WRT humanoids - I am making no statements.
- Quoted phrase in the opening sentence
- Opening quote: “official”
Blender is a little different because every 3D modeling program is odd in its own way, and the new UI was close enough that it was easy to learn after the transition (I do still use the legacy keybinds though).
But Blender is very niche hobby software. To "succeed" (if we define success as capturing a significant user share from closed source spyware), Libre and GIMP need to offer workflows that are close to what the average non-coder technical person expects. Maybe that isn't valued by the teams, or maybe they don't have enough resources to make it happen, but the end result is a reputation of jank.
I dislike vibe coded clones because of concerns about the engineering quality. But the reason they're making waves when traditional FOSS hasn't is that the UX is leagues ahead.
1 20" box fan.
4 20" mirv 13 filters (cheapest is likely costco or lowes or home depot - buy in a 4 pack to save money).
This is still expensive but the amount of air processing per hour is incredible.More info Search "Corsi-Rosenthal Box" or click https://filterbuy.com/resources/air-filter-basics/how-to-bui...
Don't go hepa because it slows down the filtering too much. I use this technique in my house and it cuts down on pollen, smoke and mold. You'll feel a lot better than a tiny expensive hepa that has proprietary filters.
- Quoted phrase in the opening sentence
- Opening quote: “cutting off Search from AI-free schools”
can someone smarter than me explain in simpler words, how is that literally not the same thing?
Everyone complained there should be a way to disable AI, and that it should be on by default. For some reason (curiosity still makes sense here), Google did some 'malicious compliance' and added the AI switch-off without making a new version of search, and disabled AI by default.
My personal theory is some sort of moral liability thing, where they're hoping you blame your school district and tell them to switch platforms, so that if/when they don't, it's "their fault", not Google's.
I think that is an unfair characterization of the video and the intent of Haskell's co-creator, based on the rest of your comment. Simon Peyton Jones makes a graph with two dimensions, useful/useless and safe/unsafe. The question he gets at is: how can one distinguish between effectful and effect-free computations in a programming language? He proceeds to characterize most useful languages as unsafe, and Haskell as useless but safe. He then spends the majority of the video talking about how useful languages are becoming safer, and at the same time how Haskell must become useful.
> we are going to build the best onboarding experience in the programming language ecosystem
> This can only be done if we commit to unix principles > write programs that do one thing and do it well
Rust is so approachable because Cargo does not subscribe to "do one thing". In fact Cargo does a bunch of things. Which is very convenient for newcomers, because they only need to learn one thing instead of a bunch (and how they interact).
The same holds for a GUI like a file explorer with buttons and interactions like drag / drop or marquee select, which is a bunch simpler than chaining 3 programs together to delete 30 old files and move some folder into a subdirectory.
It also explains why the most successful tools within the land of Unix philosophy are stuff like AWK, which really don't just do one thing. Or why PowerShell is less usable than GNU. Or why Emacs is an 'operating system'.
It's also a reason why the installation experience for Haskell is so bad: there are a bunch of programs and users don't know where to start and what they need.
> Cabal and Stack: which one should I install? > We recommend installing both.
One thing and one thing well.
Atleast it seems they've added a combined installer for these tools since the last time I've checked.
I was much more interested once I saw the actual website.
Long story short, it's basically a fret at the bridge end of the guitar, so using it will bring the 'root' note of the bass strings up a semitone or few.
I can see this being pretty useful for drones when fingerpicking. Though combining this with normal frets on the top string will necessarily be inaccurate because it shortens the string length, so the normal frets will be slightly misplaced.
- Quoted phrase in the opening sentence
- Opening quote: “but it’s always a game of catch-up.”
Do they really? They take a cut; they have incentives to let people get scammed.
EVs were the future then and especially now. German car manufactures placed poor bets.
People and the law keeps treating this as "just a sales pitch", but it's really theft in disguise and should come with evidence on an S1 filing.
Honestly, the way he lists them and even pauses before vaguely saying "mental illness" gives a strong impression that he's choosing whatever illnesses he can think of as he goes.
The actual quote from the actual article: “ Then he went on to describe the situation the company was in. Major cloud providers were running away from Nvidia, making plans to use alternative chips and lessen their reliance on the firm. Even worse, Huang said, the vast supply of chip wafers and memory Nvidia had committed to buying were coming at him like an "avalanche."”
Well said, thank you.
It saddens me that people can't understand this. Already there is the fallacy of "I can make apps with AI, therefore no one needs to code anymore," as if all coding was was making apps. But even the apps that people think are passable feel so fake, clunky and sludgy.