It really does feel like we (humanity) are on the precipice of something. We're smack in the middle of an era that entire books will be written about. I really don't like thinking about the decades to come and what kind of world our grandchildren will have.
Huh, this story sounds familiar. I read a HN comment the other day telling this same story. They didn't just turn a random HN comment into a news article, did they?
> Perhaps one reason is that OSS system programmers are washing their dirty linen in public; not a matter of "many eyes make bugs shallow", but that "any eyes make bad code embarassing".
I've committed sins in production code that I would never dream of doing in one of my published open source projects. The allure of " no one will ever see this" is pretty strong
Prague is fantastic if you can avoid the tourist crowds.
I lived there briefly with a Czech roommate who took me on tours through the "real" city. Also had a British friend there and we went through the usual tourist destinations now and then. The astronomical clock was neat, but the castle was so much more interesting and far less crowded than the old town.
Incidentally, I didn't drink before said roommate introduced me to Czech beer. What I wouldn't give for a nice frosty Kozel here in the states...
Man, I haven't thought of the word Kozel since I studied abroad in Prague 15 years ago. I must've drank two liters of Gambrinus and Kozel every day I was there.
The "dorms" for the School of Economics there were basically two large old apartment buildings 15 min out of the center by tram. One of them had its own bar inside. It was super small and dingy with a bartender who was this middle aged androgynous guy with pink hair. There weren't even tables, just assorted bean bag like seats you might find in a preteen's bedroom.
God that place was so much more me than Texas, and maybe the US, could ever be.
Not only is it delicious but it’s often 25% of the price or less than other European countries. I am not sure why beer is so cheap in Czech Republic specifically but every country that surrounds it is significantly more expensive
For quite a while before I built my homelab, my git server was a flash drive plugged into my OpenWRT router.
Honestly I still kind of prefer that to gitlab et al. It's nice to not have to leave my terminal to setup a new repo. It takes so much more effort to log into a website and dismiss a bunch of notifications before I can click even more buttons to create a new repo.
I like having all my repos accessible through the website, but I really just want to create new projects through ssh like a civilized person.
I doubt that wireless energy transmission at this scale and distance will ever be practical. It will probably never be economic compared to terrestrial panels and batteries.
If/when we build space elevators, then orbital solar might make sense to use the tether to transfer power. Even with the lower cost of putting mass in orbit, I don't think it'd be any cheaper than terrestrial solar.
Besides, by the time we figure put space elevators, we'll already have commercial fusion, right?
Well that's what the reactions are for, right? Because then we have this sort of division between acks (and other reactions really) vs "actual messages". Combine that with specific emojis in certain social/professional circles and you've got yourself an extra layer of nuance in an otherwise tricky-to-navigate space!
Well 'ack' is even shorter, and the common form of 'ACKNOWLEDGED' for such use. I've seen & used both ack & wilco in a technical/software chat context.
I use this, though I find that many folks, including many technical folks, interpret it as an exclamation of distaste (as in, "agh! ach! ack!"), so it may pay to be judicious.
Oh interesting, I have come across that, but only one person (both uses it like that and misinterpreted it when we worked with people that ack'd, which of course I saw coming & could explain since I was accustomed to his use) - didn't realise that was common too. (I would use agh/argh/ugh for that personally, depending on precise feeling(!))
Why do you need to respond at all? The phone tells you that the message has been delivered, and if you didn't ask a question or otherwise request a response why would there be any obligation to do so?
A delivery receipt, an automatic read receipt, and a human ack are quite distinct. The first means the device will offer it to a user who eventually looks. The second means the device expects that the user saw it. The third means the user definitely saw and understood it.
It's rarely obligatory (unless the sender literally requests an ack) but is more to offer a data point just in case it happens to be useful. In some cases it will definitely be useful, like to unblock something that can't proceed until the sender knows you've been briefed. For example, if I tell my kids they can stay out later than 10pm any night if I know about it, then even if they message me saying they'll be out late tonight, actually staying out late is blocked by my ack. Of course, this could just be turned into a yes/no question awaiting my answer, but that would be silly considering that I only say yes; they're not soliciting a decision from me, just acknowledgement.
> For example, if I tell my kids they can stay out later than 10pm any night if I know about it, then even if they message me saying they'll be out late tonight, actually staying out late is blocked by my ack.
Do you have an integration test for that in CI? That protocol sounds like the kind of thing which can break easily.
If I as a kid would hear that instruction "can stay out later than 10pm any night if parent knows about it" I would assume notification is necessary, but I would not return home early just because my parent did not ack it. And if my parents complained about that I would find them unreasonable.
Of course with your kids you might have been much more explicit about what you expect from them. Or who knows, maybe you are much more predictable in your response times than my parents were, so your kids might worry about you and call you if you don't respond anything.
I was just trying to come up with a scenario involving an obligatory ack (but not one in response to someone literally requesting a response every time), as a way of showing that while an ack is not typically obligatory, theoretically there could be a counter examples in the form of the ack-seeker twiddling their thumbs until ack, so to speak. I think you're right that these hypothetical kids would find it infuriating, and such protocol would work better if every ack-seeking message actually had a question ("11pm, ok?") making it explicit. It's just weird to pose a question if the answer is the same 100% of the time, and the only variable is timely receipt. How about this: "11pm, lmk" -- but the suffix is wasted keystrokes whatever it is.
Because the work is remarkably intricate. It requires you to get real close and personal with the work, usually with magnification. It requires complete and unimpeded dexterity of your fingers, so bulky gloves are absolutely not an option.
Depending on the work, it may also require frequent trips to the hearth for torch work. You really don't want to use an oxy/propane torch in a sealed glovebox.
In short, it's too much hassle and makes the work more difficult and much slower.
It really does feel like we (humanity) are on the precipice of something. We're smack in the middle of an era that entire books will be written about. I really don't like thinking about the decades to come and what kind of world our grandchildren will have.