HN user
I think it is great that people point out LLM generated articles here on HN. Sadly, it feels like I am slowly loosing my skill to identify LLM speak. Maybe I am getting worn out of all LLM content... So, please, list the indicators and telltale signs from the specific article or blog post (like others have done here already). At least I would appreciate it a lot.
I guess this just shows how divided the world is right now (in a lot of ways), but for me this sounds like one of the creepier episodes of Black Mirror or Twilight Zone.
Was this a joke? I must know!
It is still used for operations procedures in, at least, European space industry. E.g., in mission control systems from Terma (CCS5 and TSC).
I am pretty sure there are people here qualified enough to edit that Wikipedia page in a proper way.
An "explorative" hex editor where you can do "fuzzy" searches, e.g., searching for a header with specific values for certain fields. (I thought ImHex should be able to do this (and still think it might), but haven't really figured out a good work flow...)
Then you are part of truly strange circles, among people who don’t understand human behavior.
Even though I do find your indifference refreshing I must say: it does matter for quite a few people.
Almost 16000 lines in a single source code file. I find this both admirable and unsettling.
Need to check it out. I guess you mean these:
- C++ Exceptions Reduce Firmware Code Size, ACCU [1]
- C++ Exceptions for Smaller Firmware, CppCon [2]
Modern autogenerated C code from Simulink is rather effective. It is neither garbage nor spaghetti, it is just... peculiar.
Not my experience. I work with a -fno-exceptions codebase. Still quite a lot of std left. (Exceptions come with a surprisingly hefty binary size cost.)
Do you have some concrete or specific examples of intentional compensation or purposeful scaffolding in mind (outside the topic of the article)?
Yes. The LEON series of microprocessors is quite common in space industry. It is based on SPARC v8 and SPARC is big-endian. And also, yes, SPARC v8 is a 33 years old 32-bit architecture, in space we tend to stick to the trailing edge of technology.
Also remember: Even though many of these articles/books/papers/etc. are good, even great, some of them are starting to get a bit old. When reading them, check what modern commentators are saying about them.
E.g.: What every programmer should know about memory (18 years old) [1]
How much of ‘What Every Programmer Should Know About Memory’ is still valid? (13 years old) [2]
[1] https://lwn.net/Articles/250967/
[2] https://stackoverflow.com/questions/8126311/how-much-of-what...
Not just students TBH...
But even in LEO, there must be quite a few SEUs and resets?
I've always wondered how well these RPi based cubesats really work in space. Really hard to find out. Also, people (naturally) aren't always eager to talk about failed projects. Maybe some people here on HN have experiences to share?
Great project! Been using it for years together with VTS [1] to visualize real-time and propagated satellite positions and attitudes, and also star tracker and payload "beams".
Swish is great, but it is sensitive infrastructure. It has already been down multiple times due to DDoS attacks (together with BankId). Don't let Swish completely replace a stash of cash at home.
The same can be said about prints.
Yeah, look at that! Fourteenth edition. Then it stayed in print for more than 30 years. I guess earlier editions are even more expensive.
A bit strange though. So many editions should mean there are quite a few in circulation and that they aren't that rare, or pricey.
It is becoming increasingly difficult to sell, or even give away, books. In Stockholm, Sweden, where I am most familiar with the situation, most charity second-hand stores no longer accept hardcover books at all. The monetary value of most second-hand books is so low that many end up being thrown away instead of recirculated.
Of course, there are rare antiquarian books that always find a buyer, but they are quite few. And perhaps nobody will mourn the vast number of cheap crime novels thrown away every day, but there is so much more: good, beautiful, high-quality books that happen to be out of fashion for the moment. These, too, are being thrown away.
It was a long time since public libraries aimed to maintain a somewhat curated (or complete-ish) collection. Nowadays it is all about statistics. If books are not borrowed often enough, they are removed from the shelves and disappear.
Perhaps I am overly pessimistic, but I fear that many, many books will, for all intents and purposes, be lost. There are so many books that aren't scanned/digitized.
Most books are, sadly, quite worthless nowadays (monetary value). But the Tove Jansson illustrated, swedish edition of Bilbo is still a sought-after book that usually goes for hundreds of dollars.
Here is an ongoing auction on Tradera (the swedish ebay), currently at SEK 3050 (~$320):
https://www.tradera.com/item/341571/686383148/j-r-r-tolkien-...
She wrote a "treatise" on electronic music called An Individual Note of Music, Sound and Electronics. From the back cover:
"[...] a fascinating glimpse into the creative mind behind the Oramics machine. In this engaging account of the possibilities of electronic sound, Oram touches on acoustics, mathematics, cybernetics and esoteric thought, but always returns to the human, urging us to 'see whether we can break open watertight compartments and glance anew' at the world around us."
http://www.anomie-publishing.com/coming-soon-daphne-oram-an-...
Sure. But if you don't have reliability at the network layer you don't have any chance to have a reliable transport layer.
After years of maintaining and using an application suite that relies on multicast for internal communication, I would hesitate to use "reliable" and "multicast" in the same sentence. Multicast is great in theory, but comes with so many pitfalls and grievances in practice. Mostly due to unreliable handling of switches, routers, network adapters and TCP/IP stacks in operating systems.
Just to mention a few headaches I've been dealing with over the years: multicast sockets that joins the wrong network adapter interface (due to adapter priorities), losing multicast membership after resume from sleep/hibernate, switches/routers just dropping multicast membership after a while (especially when running in VMs and "enterprise" systems like SUSE Linux and Windows Server, all kinds of socket reuse problems, etc.
I don't even dare to think about how many hours I have wasted on issues listed above. I would never rely on multicast again when developing a new system.
But that said, the application suite, a mission control system for satellites, works great most of the time (typically on small, controlled subnets, using physical installations instead of VMs) and has served us well.
Some thoughts regarding this:
1. It is partly because the typical metrics used for software development in big corporations (e.g., test coverage, cyclomatic complexity, etc) are such a snake oil. They are constantly misused and/or misinterpreted by management and because of that cause developers a lot of frustration.
2. Some developers see their craft as a form of art, or at least an activity for "expressing themselves" in an almost literary way. You can laugh at this, but I think it is a very humane way of thinking. We want to feel a deeper meaning and purpose in what we do. Antirez of redis fame have expressed something like this. [0]
3. Many of these programmers are working with games and graphics and they have a very distinct metric: FPS.
Whatever the reasons are, decent countries should not fall for the temptation to launch embarrassing campaigns to rise the fertility rate. That is what totalitarian countries do. And all these campaigns seem to fail anyway. Sure, low fertility rates (if they prevails) will cause disturbances on society, but then societies must adapt.
I remember this blog! It was posting diary entries 70 years after they were written. This was a good time in the history of Internet and the diary/blog ended at the dawn of the golden era of the "blogosphere".
George/Eric paid a lot of attention to how many eggs his hens laid. It almost became somewhat of a joke in the comments. But good content!
https://orwelldiaries.wordpress.com/2008/12/01/11238/
Lots of great quotes (quite a few hen related):
This morning a disaster. One hen dead, another evidently dying.
I am pretty sure he wrote more about hens and other birds than the ongoing world war.