skysight-inc/HackerNews huggingface dataset:
>Blogs aren't "realtime", so they don't solve any problems that people went to social media for.

Curious, what is your basis for this assertion that "realtime" is the primary reason for social media? I think "realtime" has created this incessant need to watch and feed the machine. That has been an interesting diversion for a while, but I can't see it as healthy long term, IMO. I, and many others I know, check up on friends once or twice a day and then got on with our actual lives. With a less frenetic and more sane model of interaction, "realtime" is way down the list of important attributes.
"How quickly you are to agree or disagree" has been my interpretation of the big five definition.

You have to average it over self-assessments and also the assessment of all your friends, family, and coworkers.
One-on-ones are the reason for that. Two people mean both are actively involved. Either listening to someone speak to them directly, or talking to someone directly.

> Teams that work together on the same project should regularly get together in a synchronous conversation.

This doesn't prevent that. It seems that it only prevents you from automating the decision on when to do that. If you need to synchronize, you can. However, if you don't, there is no need to hold a meeting. But people tend to make meetings opt-out rather than opt-in. This seems to enforce an opt-in approach first.
So here's my question about static-site generators, such as the one that the linked site recommends.

They seem fine for lengthy prose. You probably aren't going to write that many long-form blogs anyway — in the vicinity of several hundreds, maybe. After many years. So that's fine.

But what I've discovered about my writing habits is that I mostly tend to write short notes, about the size of a Hacker News comment. And those can easily number in thousands after several years of writing.

So how well is a static site generator suited for this? Do I want to build thousands of pages every time I start the site locally? I probably don't. But I can't find a reasonable static-site generator that will only build the requested pages locally, and build everything when deployed.

It's probably also silly to pre-generate a static html page for every such short posted note.

What's the most appropriate solution for such a writing pattern? Bite the bullet and set up a Wordpress or a Mastodon instance? That's a bit depressing.
We have organizations like Consumer Reports here too in the US, they also make a large amount of money, but that doesn't mean that most people make their purchasing decisions from such organizations. I guarantee if you did some sort of study, most would say they made a primary purchasing decision via advertising.
I spent a while looking at this trying to figure out why 14 degrees would be a problem before I realized it was Celsius rather than Freedomheit.
You are absolutely correct. It turns out "copy initialization is the formal term used. It's kind of stupid IMHO, since it may not be initialization by copying or using a copy of anything, but:

https://en.cppreference.com/w/cpp/language/copy_initializati...

So I half-take-back my comment.
I swear that's what it was called when I was first introduced to it a decade ago. When I first saw one of the posts focused on it on here I didn't initially recognize it as referring to the same thing.
No. I worked there, and saw the services available to developers. There's a dizzying array, and many of those services are quite excellent. However, they're deeply intertwined with each other and often quite idiosyncratic. That's going to be a hard sell in a market where people are already used to the Amazon or Google or Microsoft versions.

There's a lot of automation, but it's mostly for the team running the service itself. If you're a user of a service, you're likely to be quite reliant on knowing a member of that team to get new allocations or resolve problems. This is fine for developers within a single org, but building out the self-service and multitenancy necessary to make it palatable to outside users would be a major undertaking even if all the oxygen weren't being sucked out of the rest of the company by metaverse stuff.

Lastly, that capacity is already being actively used and they're barely keeping up with building out enough new capacity. Where are the resources going to come from to support outside users?

It just doesn't make sense for them to try, technically or logistically or culturally. The last thing they need is more distractions.
The lack of type checking and general runtime failures made the transition particularly difficult if you didn't have a bazillion unit tests covering all your large codebases.

I was lucky it didn't affect me much, but I could sympathize if somebody had hundreds of thousands of lines of python2 legacy code that needs to be migrated..
Stating a blog is easy. Posting regularly is fucking hard.
Already technical work arounds:

tooth hearing aid : https://newatlas.com/hearing-aid-tooth/14042/

contact version of google glasses : https://massivesci.com/notes/smart-contact-lens-google-glass...

https://newatlas.com/wearables/team-hart-vibrating-sleeve-la...
Sorry, I've meant the US' interchange rate, not EU's. There are no flat rates (or sometimes it's a floor - you'll be charged a flat $XX even if you processed <XXX transactions (or even not have a transaction) weekly).
You can come to USA. Utah and california had great starts to their ski season. One of the best, infact.
HTTP/3 prioritization demystified
Mistakes were made. They obtained it from someone who had no right to give it to them in my opinion, although of course rights are a tricky subject and many believe “might makes right”

Eventually going up the chain brings us to the government, which again, had no right to give that land away when it belongs to the people. Whether they did it because of corruption or ineptitude is irrelevant.
I thought the challenge was for one that does it well? :D
Blogger doesn't get much attention and I'm somewhat surprised Google hasn't killed it. (Maybe enough people run Adsense to make it worthwhile.) But it's perfectly adequate for a basic blog and, if you do get a traffic spike, it handles it without breaking a sweat.
May I ask why they are not even in the same data center?
Meetings are how humans share state. Most people’s writing skills are not up to replacing the back and forth synchronization that happens in meetings. And big meetings have value in avoiding games of management telephone.

Canceling all recurring meetings may work for awhile, but I imagine it won’t be long before there’s a permanent action item for every meeting to schedule the next one. And it also won’t be long before senior management is made exempt.
IRC + email + VCS system works fine for FLOSS projects.

tmux can also be used for screen sharing, if anyone needs support or wants to pair on something.

One nice thing about using this comms stack is it doesn't exclude people who are on slow internet connections. Video/audio is grossly inefficient for transfer of some bytes of raw information versus text.
Sure. But this is a pointless thing to complain about.

OP could have given a long, complex nuanced statement to appease pedants like "Due to climate change making warm weather and lack of snow in January far more likely than in the past, there was in fact warm weather and lack of snow during my planned trip, so I had to cancel my plans. The odds of this happening without decades of carbon emissions from fossil fuels would have been very unlikely".

Or, you can skip all that excessive cruft which is understood by almost everyone as being implicit and just say due to climate change.
Teams work in cycles. This would mean, for example, that a monthly/quarterly retro with the whole team is now not allowed. That's bad.
>A full half of the voting base, or more, fervently vote against their own best interest.

You really shouldn't assume you know more about half a voter base's own interest than they themselves do, regardless of their "side" in an election. People are driven by different things and put different weights on said things than you do.

The only thing this kind of thinking does is infantilize adults at best and demonize them at worst, which is pretty silly when you're talking about half the voting population.
Yes. In Brazil, a single judge can issue an order that makes your website inaccessible to anyone within the country, plus cancel all your social media presence at once. All that in a matter of hours.
I think you are just helping make his point.
I'm not so sure. The whole point of an exercise like this is to demonstrate power, or to acquire resources. Neither tactical nor strategic nuclear weapons would help with those objectives. Ukraine's army isn't isolated to a single spot — tactical nukes wouldn't even be as effective as WW2-era area bombing, and a whole lot more expensive. Strategic weapons would deny resource acquisition to RU. The use of nuclear weapons (of either kind) against civilian centers would be problematic, I think? The US "got away" with its use of nuclear weapons (first use; the US was the only major player left; etc.)
Friend of mine got told by doctors as a young girl to "toughen up" and "not make such a fuss about food." Turned out she had Celiac disease.
rich just fly to wherever there is snow.
Might have to have a read of that - reportedly my grandfather worked on antifreeze solutions at the NPL in London during WWII. Be interesting to see if any of his work is referenced.
>"Well, the person in control doesn't see it that way"

Said person is definitely lunatic but I bet none of us have any real clue on what he sees and why.
For an org capable of adhering to standards. I've seen success in small teams. I've never seen it in a large org through, it's always a dumpster fire. Especially anything that grows really fast, culture is out the window to randomness, and it's a hodgepodge of understanding and methods that are all over the map.
Yeah. That is my goal as well. I struggled choosing between learning Rust, Zig, Ocaml or F# and landed at Nim

Given the compilation step to C allows nice FFI and using all kinds of compilers
Just learned about Usagi Electric from this post. Cool stuff. Also... there are plenty of loose threads on the intarwebs to pull on to learn more about this machine. The 70s was a great time for computing. We all know the stories about microprocessors being developed at Intel and TI (and Motorola and MOS.) The micro guys were building something as beefy as they could from the ground up. But this is the story of the mini guys trying to find a way to compete with IBM and DEC (and Harris and Prime and ...) and cutting costs down while maintaining the core of mini-ish functionality.

I love this stuff. Props to David for restoring this beast. Thx @xupybd for posting this here.
Terrible analogies are superior to great ones.

I can shout great analogies at my team all day long and they will just roll their eyes

But the moment I toss one out there that's terrible, they give me a dozen better ones back, and I win because I got them to swallow thing I was sugarcoating with analogy
I don't have strongly negative opinions about any math or CS books.
> I just had a shower thought the other day that with the growth of WASM, Apple could target the web as well

Lol you don't remember how Apple's been specifically trying to hold back web technologies to encourage native apps? Embracing WASM is completely against everything they've been doing for the last decade.
Quite so if you hold cows sacred or are otherwise opposed to using animal products - I’m neither it’s not that different to McDonald’s not disclosing that their french fries contained beef flavouring. I’m neither and it can sound trivial, but a lot of people are and really care about this kind of thing.
One thing I've noticed is that people are less prone to personal discussions over a conference call compared to in person meetings. We only rarely do in person meetings now because of how quickly we can get through a meeting. One thing that contributes to this is the fact that you are sitting at your computer with plenty of other things to work on other than the meeting. When you're sitting in a conference room, there's no work distractions so people find other things to talk about, whether it's what they did that weekend or other work discussions that are unrelated to the meeting. One other thing is that since a Teams meeting feels less "official", we can have multiple status meetings a week where it's not mandatory to call in for every one of them. Our in person status meetings were once a week and would go for at least two hours since it was easier to get people together for a long time once a week than a short time multiple times a week. A status meetings once a week was simply not enough because of how quickly things changed throughout the week so by Wednesday, the plans for the week could have changed or someone's progress may have been halted due to a problem. Very inefficient!
"If you are institutionally incapable of..."

This is the road to bullshit. Of course no manager or CEO will admit that their team/company is that. Admitting technical non-excellence is nearly impossible. Organisation inadequacy... impossible.

So the best course of action is to pretend your organisational methods are really just software architecture... and back to square one.
You can stop notifications in Slack now, and I don't know what the other engagement tactics are.
> If you're looking for a single "gotcha" quote you don't really find it because the document is a fortress of wordy CYA

I'm looking for any quotes. One thing that confuses the issue is that the gizmodo piece removed citations, which makes it look like this was all his original thoughts. Of course, one response to this is to then attack the cited pieces, but that's a different argument.

Anyways, I'm not here to pick up his banner and run with it. I believe that people did honestly interpret what he wrote as you have here. But I also believe that other people honestly interpreted it as not that.

Which, back to the topic of this thread, is a perfect example of the pitfalls of thinking in public. If people perceive you to be thinking the wrong things about topics that are very sensitive for them, they will react very strongly (understandably).

It's sort of like a variation on murphys law: anything you say publically that could possibly be interepreted negatively will be. And then it needs to be attacked because it might actually move the needle on some issue, whether or not the author intended it to.
>>a very long time we used email for most things

The only thing worse than email for communication is talking on the phone....

I would love to kill email completely
I wonder how much production during that time would move to places like China where the energy comes from coal to a much larger degree which is so much worse.
Lately I have really been wanting a super-simple electronic note-taker with voice recording and clock/timer function, and absolutely nothing else. Imagine a Blackberry/Palm PDA style device with a physical keyboard, and a minimal OS designed for note-taking, like what you see on Remarkable or Boox e-ink tablets.
Conways law:
Tech follows communication patterns (.i.e org setup)

hence, if you want a certain architecture, you likely need to execute a "reverse conway law" org first. To get the org into the target config, the software will follow.
People still use russian doll caching, but its a bit of a pain honestly due to having to make sure to call `touch` in all the appropriate places, which is surprisingly a lot of places. Its very easy to forget to do so and end up with stale caches.
Ghost.org seems to come closest to what you seek, and they include a very important feature, which is paid subscriptions for readers of your blog. People who are serious about blogging/web publishing will after some time need to charge for their content if that's their full time job. Wordpress makes this part very difficult for people who are not sys-admins.
My dad is a software engineer and has been my whole life. When I was a kid, he and my grandpa always surrounded me with computers. They got me my first computer (and Acer laptop that came stock with .5GB of ram - later upgraded to a whopping 1 full GB) and my dad installed Visual Studio on it.

I loved computers but really started writing code regularly when I was 13 and knew it was what I wanted to do. Once I got to college (for Computer Science), I realized how deep it went and I loved it all even more. Now I'm a software engineer and I regularly think about how lucky I am to work a job I love that pays well.
I'm just worried they never caught those clowns roaming the forest. Or the satan worshippers from the 80's. They're still out there!!

Or maybe they ran into each other and the problem is solved...
which would you rather have, thousands of people who maybe see your tweets, or a few people who actually engage with what you care about?

numbers vs community.
Nope. If a thread was getting long we would just schedule a meeting to make a decision.

I can’t remember ever seeing a thread of just 1 line back and forths (although I have seen this on slack). The 1 line emails I remember were usually from some higher up person who was signing off on some decision and that ended a thread usually.
Meanwhile, western US resorts are having their best November and December in over a decade. Alta has already received 300 inches this year!
It was called MARSNWE, if anyone is curious.

A source, ironically from Novell docs.

https://www.novell.com/documentation/suse91/suselinux-adming...

It only emulated Netware 2/3, not the later NDS versions.
Mail has always felt like garbage to me. Notes, I will have to give a try again. Though, really, the entire "office suites" that everyone makes always feels off to me. I will full cede that that is just preference.

Safari feels off, as well. But I'm pretty firmly in camp firefox.

When I think bundled apps, I think of their notepad equivalent. The finder. The calculator. And... that is about it. I remember trying to make a script once, and that script editor left me very very lost.
Thanks for the note!

I enjoy using slim in my views though prefer scss to sass. I think for many of those tools either misindentations raise an error (like failing a yaml schema validation) or result in incorrect but observable behavior (content isn’t in a div as expected).

It really comes down to how the tool is supposed to be used and how failures are handled.

In general I think that’s the difference between a good experience and a great one: when we can have beautiful failures that help us learn.
Not the worst thing in the world. I'm not saying it's necessarily better than a meeting, but at least you have a paper trail and automatic log of decisions made.

(A collaborative doc would probably be a better venue for that, of course.)
I'd recommend you have a read about the "Sunbeam Radiant Toaster" first released in 1948 [0]!

> When you stick a piece of bread into this toaster, it pushes down a series of cleverly designed levers that have just enough tension to lower and raise two slices all by themselves — and it’s got a mechanical thermostat inside that stops your bread toasting when it’s toasted and ready, NOT after some arbitrary amount of time.

[0]: https://www.theverge.com/22801890/sunbeam-radiant-control-to...
This is just another flavor of the Musk-esque belief that the ratio of delivered production code to man hours is too low. Engineers should be coding, not in meetings. This is a plausible thought for anyone with 1-2 years experience, and a frightening thought from anyone else

Yes there might be some fat to cut but this approach just sounds terrible

In reality projects will go in random unwanted directions, or TBs that used to be recurring will be manually created one at a time, and things will continue just like before this decision
> you need a proof of concept that centralizes various blogs into an updating feed of subscribed blogs.

its called rss
Massive fraud as well even from legit actors, stiizy for example is being sued for faking lab results

https://www.insurancejournal.com/news/west/2022/12/08/698377...

This brings questions up about contaminants for me

Raw garden too has been sued in a class action suit over terpenes misrep.

I agree be the wizard and make your own potions.
I think you may be wrong here. There is a consumerisation of the enterprise IT and Apple is happy to grab a big piece of that cake (and not unsuccessful) when it comes to push their devices into the business market. If they had no interest in dealing with businesses, they'd not invest in enabling companies to manage large fleets of Apple devices.

https://support.apple.com/guide/deployment/welcome/web
Presumably they can still schedule the synchronous conversations one at a time. They just can't set them to "recurring."

I have no idea how they make policies like these work with business partnerships though. I could live with a rule like this internally, but it's hard to get time on a client or partner's calendar and, when you do, recurring meetings let you reserve it.
I think this (and the overall discussion) cover it better than I ever could in a single post: https://news.ycombinator.com/item?id=30172268

However from a personal level the main two ones for me are the poor quality of its codebase and the lack of care or common sense around the official plugin repository, bordering on outright incompetence on their part for allowing unvetted and highly dangerous plugins to stay on the official repo.

Honestly as a developer for going on 20 years in a professional capacity I physically recoil at the absolute awfulnes of the codebase.
Ok. So that's just triggering auto-insertion of &mut *

It's completely optional fearure. You don't have to rely on it. Like auto-insertion of semicolons in JS maybe it's better if you don't. Although likelihood of this biting you is way lower than in case of relying on semicolons autoinsertion.
Under the same logic, would you call fetching static file "RPC call"? What about fetching a static file via FTP (per my other example) or Gopher -- is this RPC as well?

In general, do you think it is possible at all to have a request/response protocol which is _not_ RPC?
Banning recurring 3 person meetings initially sounded overly reactionary and reductive to me. It does sound like proliferation of meetings has become a growing problem and I wonder how much the video-off-zoom-attendance is a contributor.

The article implies that they previously had multiple 50+ person meetings per week(!!)
"Big meetings of more than 50 people will get shoehorned into a six-hour window on Thursdays, with a limit of one a week."

As someone who has never worked a company larger than ~300 people, can anyone enlighten me on what kind of meetings would have that many attendees, outside of say a quarterly all-hands?
Why do you believe there is more engagement in mastodon than in a platform designed to maximize engagement?
Huh? They can, and will, just add the things they want to the rest api of the microservice A and then call them from B. That doesn't change with microservices.

Look up a thing called "distributed monolith".
The most powerful people seem to do shady and aggressive things but always keep a professional and calm composure on the outside, no matter what. (Think of politicians who have remained in power for a long time)

As maybe an interesting business example, Elon has begun to shed the calm outward composure more and more over the last 5 years and has lost more wealth than anyone in history at the same time. Maybe that is coincidental but one wonders.
The change to the proposition above then must be that there are no vertically oriented transparent objects that are also solid in nature.