HN user
back at this
You’re conflating consciousness with intelligence. Consciousness is subjective experience
Indeed. Thinking is not the same as experiencing thinking.
there’s no way to know if any other people, much less machines, are conscious.
Or even ourselves :D
"Consciousness is just an illusion" "If so, who's experiencing the illusion?" "Yes"
Even those still halfway up said ladder: https://x.com/flowersslop/status/2058161240350794165?s=20
Aha, thanks!
a single Apple (Packard-Bell) ][+
I'm curious what were you referring to here. Did Packard Bell make Apple 2 clones? I didn't find anything in a quick search.
Please don’t post AI slop to HN. It’s against the guidelines.
Apart from the Transformer architecture that enabled the AI boom/singularity/civilization-reshaping-event/whatever-this-is? Not much, I guess...
I must have missed the 8GHz CPU era.
Right. It captures the destabilizing effect of stochastic terrorism, without the terroristic intent. It’s a neat phrase.
The earliest I've used was Protracker, which was the most popular tracker in the early heyday of the format (late 80s - early 90s), but the earlier Soundtracker was the OG "tracker", and probably used the same layout, but I'm not sure. https://www.exotica.org.uk/wiki/Soundtracker_History
But if FL Studio (formerly FruityLoops) and Renoise use the same layout, as others have said, then those are probably going to resonate with a wider modern audience :D Or maybe just call it "FL Studio / Renoise / tracker layout"?
I don't do computer keyboard note entry any more, but I still have the muscle memory for that 4-row layout from hours spent with it in the late 90s :D And I'd totally use it in your game. (My MIDI keyboards are kinda too far away from the mouse and monitor.)
This, but (or "and") use the 4-row layout that dozens of tracker programs used[0], to fit over 2 octaves on the computer keyboard.
On a US keyboard:
QWERTYUIOP[] is the white keys starting at middle C. (The row above is the black keys; the 2 key plays C#.)
ZXCVBNM,./ is the white keys starting an octave lower. (S plays a low C#.)
The two ranges overlap; e.g. Q and , both play C in the same octave.
Grew up composing music on a computer this way when my (musical) keyboard didn't have MIDI and I couldn't afford a better one :)
It’s a Zen proverb.
I broadly agree with the author’s point there, but disagree with the specific language he used. In my view, engineering includes those pesky non-technical considerations, like the business context and the human factors, which bring their own tradeoffs and priorities to the engineering decision-making.
That is, his “pure engineers” are not really doing engineering, at least under my understanding of the term, whereas (some of) the impure engineers actually are! :)
CDs never had any DRM
Oh, but they did, and quite infamously :D
https://en.wikipedia.org/wiki/Sony_BMG_copy_protection_rootk...
https://arstechnica.com/uncategorized/2005/11/5549-2/
https://www.networkworld.com/article/715376/network-security...
https://www.researchgate.net/publication/240779158_Lessons_f...
They’re going to get promoted anyway. The “senior” title will simply (continue to) lose meaning to inflation.
I love vintage computers, have a vintage computer collection, and have enjoyed visiting computer museums, but does this computer museum website really need to send me desktop notifications?
2024 lecture videos are on YouTube: https://youtube.com/playlist?list=PLoROMvodv4rN4wG6Nk6sNpTEb...
I believe it is aimed at investors.
I think it’s more likely aimed at the (internal) promotion committee.
And according to TFA, the AI slop results are also from Reddit!
Thread from 30 days ago (albeit without much discussion at the time) https://news.ycombinator.com/item?id=44294488
I assume it's Supreme Leader.
Another vote for the 68000 series :)
Thanks, I like your framing in terms of the impact on "trust".
Generating more complex solutions that are possibly not understood by the engineer submitting the changes.
I'd possibly remove "possibly" :-)
Feeling this too. And AI is making it "worse".
Reviewing human code and writing thoughtful, justified, constructive feedback to help the author grow is one thing - too much of this activity gets draining, for sure, but at least I get the satisfaction of teaching/mentoring through it.
Reviewing AI-generated code, though, I'm increasingly unsure there's any real point to writing constructive feedback, and I can feel I'll burn out if I keep pushing myself to do it. AI also allows less experienced engineers to churn out code faster, so I have more and more code to review.
But right now I'm still "responsible" for "code quality" and "mentoring", even if we are going to have to figure out what those things even mean when everyone is a 10x vibecoder...
Hoping the stock market calms down and I can just decide I'm done with my tech career if/when this change becomes too painful for dinosaurs like me :)
That’s fair, I didn’t think about climates actively hostile to “gentle” exercise :)
Sample of one, but I find gentle exercise in evening (like walking) isn't a problem. A moderate-to-intense run in the evening does affect my sleep, though.
The ST very subtly so, even :)
"ST" officially stands for "Sixteen/Thirty-two", referring to the Motorola 68000's 16-bit external bus and 32-bit internals.
Not quite RTX, but it almost happened, 25 years ago :P http://www.x86-secret.com/articles/divers/v5-6000/v56kgb-6.h...
The earlier machines had much higher quality capacitors that are mostly still OK afaik. Consensus (if I may be so bold as to try to represent it) in the Amiga community today is: definitely recap the later Amigas (A600, A1200, A4000, CD32) with their cheaper SMT caps that usually leak and slowly destroy the motherboard, but A1000* and A500 usually don’t need it.
*The caps on the motherboard, anyway. I am not sure about the durability of the internal PSUs. I haven’t bothered to replace anything in either of the A1000s I acquired recently.
That's true. It feels like every other ladder-climbing wannabe out there is also trying to attract powerful people's attention on Twitter et al these days, so I imagine it's much harder to stand out than it was for a kid in the 1970s. But you're not wrong.
As a reviewer... it really, really depends on how trivial or gnarly the PR is.
If it's a simple change that is obviously correct, I'll try to unblock the author ASAP - often within minutes, even if it interrupts my flow.
If it's a giant PR with lots of risky changes in vital code, an awkward-to-unreadable diff, and/or maddeningly questionable design/coding decisions that require me to think a lot and compose some nuanced, reasoned comments to steer you in a better direction, then, well, you might find yourself nagging me for a review 2 days later. (And I'll probably ask you to split up PRs like this in future, e.g. to separate major refactoring from any logic changes.)