skysight-inc/HackerNews huggingface dataset:
I would think it's not the case for the majority of babies even. Some parents do keep the baby constantly at their side when sleeping and some are doing that weird co-sleeping thing with a raised cot right next to their own, but most parents (in modern societies where cots are used) seem to just do the usual: give the child their own place to sleep and let them develop a healthy sleeping habit right from the start.

We had our son in his own cot in his own room at night (within hearing range obviously) and in a wicker cradle during the day. We moved to an infant bed as he grew. He moved to a normal size bed a few months ago at 2½ (rather soon, but he's tall and outgrew the infant bed). He's a good sleeper.
Dune was fresh for its time because it introduced some ecological thinking into pop culture. Reading it in 2021, none of it is fresh anymore, so we're left with a generic SF story.
I've noticed quite big overlap between doom-preppers and cryptocurrencies true-believers. Even here in Sweden, the people I know who got very into crypto fall usually between: speculators trying to make a quick buck (coming from day-trading, etc.); doom-preppers that bought BTC, silver, gold, and other "stores of value" they believe will save them from a societal collapse; gullible people thinking that crypto is a safe way to make a lot of money quickly (so get-rich-quickly schemers).

I've met quite a lot of people invested in crypto around here (seems to be quite a big fad for a few years now) and only one had proper understanding of the technical aspects and believed in the technology itself to solve other problems that aren't just finance scams. One from a pool of 100+ people that I had conversations about crypto in the past 4 years.

Nowadays I simply avoid any chat around crypto in real-life, the signal-to-noise ratio is so damn low that it's impossible to have a good, intellectual conversation around it, it's a rotten subject.
Also BR:

- I'm shitting and walking ("estou cagando e andando");

- My as* doesn't even itch ("meu c* nem pinica").

- What about Kiko? ("e o Kiko?" -- trust me this one is hard to explain).

EDIT: formatting
It solves the double spending problem in a decentralised network. Whether that has an application is another question.
Or recently, the post-install page having a nagging animated button to please buy Mozilla VPN.
I'm in favor of this.
Why don’t you take your vacation?

It’s probably in your interest both financially and medically to do so, presumably?
A New Hypersonic Wind Tunnel Will Put China '20 to 30 Years Ahead' of the West
If you are satisfied with your pay, consider enjoying the time that has been freed up for you.
Not sure why you were downmodded, this would be a great idea.
Let's also not forget the value of having a person sitting there doing just the bare minimum needed to have some familiarity with where things are and what does what... so if something does blow up (and it will), (s)he can instantly step in and take emergency measures to restore service.

It's called 'reserve capacity', and some people think it is helpful
Ask, ask, ask. Yes, you can spend days or weeks poring over the code in various ways, but asking those who made it (ideally) or those who maintain it will give you the "why". Why was it done this way? What are the implicit assumptions and invariants? Why were seemingly obvious ideas not implemented? Or were they and found problematic? Document these findings for the next generation.

But as you do this, keep an eye out for assumptions that may have changed. A feature now obsolete requiring weird code. Out-of-date assumptions about the behaviour of computers or other systems. New language features that can simplify or improve code. Talk them over with the people who know the code, and maybe you'll be the one to delete that awful code everyone hated.

Also, take notes, not just about the code, but about its environment, release process, surrounding systems, use cases, and people. Knowing who to ask about a given issue is gold.

If there are post-mortems available, they can give a great insight into how the system works and fails. Design docs to a certain extent, too, but they can be misleading especially if they are not kept up to date.

Pair programming can be a very effective way of learning, too.
I built a foxhole radio some years ago. Fun project when you’re not locked up.

https://blog.jgc.org/2012/02/my-foxhole-radio.html
> Based on what OP has described, the company is likely doing a lot of work they shouldn't be doing and working on things in the wrong order.

How can OP, as an engineer, or anyone else, that just joined a much bigger organisation, have any clue that a company is doing work that they shouldn't be doing AND they are doing it in a wrong order?!
Still waiting for these guys to update their MacOS app, we use it in our company and it's so bad that our own team uses Slack.
> I have never seen anyone argue Mac OS was anything but beautiful but I guess there’s a first for everything.

Well, allow me to be number two, then. In my opinion, macOS is bland, unclear and the general UX is peculiar to say the least. I dislike the concept and the design of the system bar at the top and the blur effect they add to some UI elements (which Microsoft copied for their latest Metro design language) just looks excessive to me. The iPhone-i-fied controls that have been added to macOS are a step back, in my opinion, because now there's a giant system status popup that looks like you're supposed to touch it but Apple doesn't want to introduce touch screens to macOS.

The thing the macOS-ecosystem does well is integration, which is arguably much more important than just design. I rarely use any tool on Windows that follows Microsoft's guidelines, whatever those are this month, but on macOS the UI designers seem to be focused on integrating well with the looks of rest of the system. This has the unfortunate side effect of putting some of developers using the macOS design language on other platforms as well, fragmenting the system even further, but for macOS users this is a great benefit. Even an awfully ugly system (like the BeOS look which some people love, but also the Gnome 2 "3D" look) is still much more usable than most "modern" designs because you know what to expect from applications running on that system.

You can disagree with me, and that's alright. Any design is liked and disliked by different people. I personally enjoy the simplicity and elegance in designs like the SerenityOS UI, but I can definitely see why others hate it.

But, if you truly have never met heard anyone say that they didn't like macOS' design, then you're part of some very different social circles than I am.
I've had very good experience with Gl-iNet products. They have good hardware, very good openWRT support (the official firmware is based on openWRT) and are beefy enough to be used as home routers even if they are marketed as travel routers.
myself?
Not to mention it's an Intel only binary, what's the point of using these dreadful electron cross-platform apps if they can't even be built as universal binaries.
> We reported the issues to Microsoft in March 2021, who has only remediated one so far

I feel that I read something like this almost every single time Microsoft is mentioned in a vulnerability disclosure. What makes the company so bad at dealing with security reports? I don't expect it to be a lack of talents or resources, or is it?
I am a Mac user for 10 years and just can't fathom using anything else at this point so I might as well be called a "Mac fanboy". Yet, Monterey's (12.0) UI is a clear regression in comparison to Mojave (10.14). The utter lack of attention to the pixel grid, the unnecessary horizontal paddings where horizontal space is valuable like sidebars, these top bars that are way too huge and combine the title bar with the toolbar so neither fits comfortably, too much spacing between menu bar icons, the "control center" that's clearly made for touchscreens despite macOS devices having none, and this list goes on and on. This redesign was clearly done by someone who 1) prioritizes looks over function and 2) wants change for its own sake.

edit: you know you're making terribly misguided UI decisions when people build software to revert them: https://github.com/MacEnhance/MEMiniMe
There is nothing that prevents a digital machine from exposing such UX to the user.
Quite the contary; that's the only thing they can do by themselves.
>Remarkably, neutralization of Omicron was undetectable in most vaccinated individuals.

I'm not sure I understand, are they saying double vaccination had no noticeable effect on Omicron?
As a counterpoint, on first read I also thought it was ready to hatch now.
Somehow we still have medicine (they do a lot of testing before they release anything!) and doctors (they have insurance!).

It would increase the barrier to releasing software massively (possibly killing the startup scene altogether), but it doesn't mean software development would end.
You are right. But I do get outside for at least an hour a day to do sport, everyday. While I don't do calls or google around, I stop for taking photos with my phone. But you are right.
Steve Ballmer’s “Parting Gift” as Microsoft CEO: Trying to Name Cortana “Bingo”
Not at all unexpected...
Surely banks lose the same way tons of money for calling scams everywhere, it was good old phising scam + nft insanity greed.
Often the call scams at least where I live make old people to wire their money because they think they talk with a banking clerk. In this case young people thought they were talking with some sort of nft/crypto influencer I guess.
> Remarkably, neutralization of Omicron was undetectable in most vaccinated individuals.

Living in a country (Norway) where boosters are being slowly trickled out, this was disappointing to read.
They basically half the symmetric keyspace (but there could be better, more specialized quantum algorithms), and the next smallest keysize is usually 128 bit. So that's what most foreign encryption will use after this new law. A brute-force search of a 64 bit keyspace is no problem for a nation state like China.
Does the lower count imply lowered fertility? If so, there should be an affect on births. Is there data to indicate this (after two years of covid)?
> So you're telling me that if your customer wants the button in blue and you want it in yellow, you won't put it in blue?

If I don't feel like making the button blue, I won't. If they don't agree with my decision, they are free to take their business elsewhere.

> If someone else is giving you money, they are your boss.

It is true in some respect, but when you're employed, you only have a single or handful of bosses. When you run a business, you have tens, hundreds, or even thousands of customers. You can say NO to any one of them when the push comes to shove.
Personal advice: setup a workers coop with some people you trust you can work with. Equal pay for everyone, flexible schedule. And you get to choose who to work for as a client.

If you people have some crazy ideas worth researching, a coop is the perfect setup. You can find some contract to pay the bills then liberate time to work as a team on something free-software that actually matters to you.

You may even end up with leftover money to donate to other amazing projects you'd like to support.
Hi there. I don't do pair programming and I'm pretty wary of it, but I checked out the site and watched the video and I have a suggestion.

Suggestion: market this to remote teams regardless of whether they do "pair programming" per se!

In my last job we had our team spread out over continents and time zones and home-offices and office-offices: bandwidth for meetings was super unpredictable.

Thus anything with a live video component was hit-or-miss, and if you had something very technical to discuss, you often had to sync up to make sure everyone was reading the same page on Jira or whatever.

I realize your tool is probably only for 1:1 conferencing, but even then, I think it could be compelling to have really good screen sharing with some annotation and the resolution control. Even if (especially if) it's only going to be used by two people at a time.

(Maybe this needs a different kind of license though. If I have 10 people on a team and expect 5 of them will use it but I don't know in advance which 5 or when...)

Also I would absolutely want something like this in a startup, even for managers, just to be able to go over stuff like AWS consoles (shudder) together.

[edit: grammar]
One in this temperament: try accidently pasting a very large amount of data in the chatbox in Teams. Then spend the next 40 minutes re-starting Teams to try to remove the data from said box while your laptop tries to fly away and Teams keeps many processors and gigs of memory lit trying to parse your data.

Microsoft should (but won't) reconsider the idea that one chatbox to rule many underlying types of software is a good idea.
I know, those were two separate categories. Regarding the Wayfield project, citing them:

> It is very unlikely that distros will be ready to ship all the pieces we need in the next 12 months. So the "short term" goal may actually need to wait for somewhat longer than that.

https://wiki.openjdk.java.net/display/wakefield/Meeting+Note...
The English don’t notice their English accent.

England is a country of a new accent every 40 miles or so. We understand each other nonetheless; we’re habituated to it from birth. We rarely realise others don’t experience the same.
It can also download and execute arbitrary javascript from the web, outside of a normal browser sandbox, effectively turning every app into a potential vector for system takeover, because it is RCE by design.
I have a hard time understanding why MS is investing so much into VS Code yet so little progress is made on MS Teams (which in theory should be more important to them as it has broader usage?).
I think the first vulnerability could also lead to a DoS if they point the server to its own lookup route?

Also sad to see how Microsoft is treating security researchers, instead of thanking them with a small bug bounty. Especially for the one (or maybe two) DoS vulns
Great questions. You can read the original paper here: https://www.cell.com/iscience/fulltext/S2589-0042(21)01487-5

It’s fine to be skeptical and ask questions, but you’re asking a bunch of questions that palaeontologists have figured out years ago. I suggest you take some time to understand the details if you’re truly interested.

I suspect you may be coming from a place of mistrust in science? It’s not a good position to be in as you’re missing out on a lot of the world if you can’t enjoy this kind of thing.
Ants developed civilization. You don't need brains for that.
Parent suggested free software would be the exception to this rule. Personally, i don't understand why it's even legal to publish binary code without the corresponding source, but at least their point made sense: volunteer-run projects need to be exempted from such regulation, and there's exactly zero reason a volunteer-run project should not be free-software.
Boosters are gonna be the norm moving forward, I highly recommend people to check out TWIV (This Week In Virology) Podcast it has a lot of information based on real data and studies coming out.

Link - https://www.youtube.com/watch?v=VkhN4rC19RI
Look at crows, maybe.

https://www.thoughtco.com/crows-are-more-intelligent-than-yo...
Whoever wrote that sentence can’t write for shit. It’s the most important sentence in that whole document and they fucked it up.

You had one job.
Maybe people have a preference for software that conforms to a set of often well-thought-of platform UI standards and interoperates seamlessly with their other applications instead of Web applications that don't conform with the platform's standards. Part of what made the Mac and Windows attractive compared to MS-DOS is that the former had UI standards that made it easier for people to use new apps and to interoperate among apps, while in MS-DOS each application implemented its own UI and things like interoperability and accessibility were challenging. The Web is a throwback to MS-DOS-style development, where there are no standard UI guidelines. It's one thing to deal with this when using remotely-hosted Web applications, but it's another thing when an increasing number of desktop apps are essentially locally-hosted Web applications.

The Web is fundamentally a different platform from modern desktop environments; writing desktop applications as if they were Web applications running on beefy servers leads to bad user experiences, just like how Web applications that do not take into account network latency, security, and other aspects of the Web that don't normally apply in native desktop applications leads to bad user experiences.

I'm not saying that Electron is automatically bad. Cross-platform GUIs and other tools have existed for decades due to their labor-saving characteristics, and this is a recurring controversy (for example, Microsoft Word 6 for Macintosh was widely panned by Mac users due to its feeling like a simple port of Word for Windows instead of a tailor-made Mac application, and certain Java GUIs don't fit with the underlying platform's UI standards, though Java does support native UIs). However, I think it's a bad thing for software vendors and developers to take the attitude that users should be grateful for whatever they release, though I admit there is a thin line between expressing dissatisfaction and acting entitled.
TWiV 844: Paul Offit on children, Covid, and boosters
thanks for giving us a 600px image

here's the study source, with beautiful high res version of the pictures https://www.cell.com/iscience/fulltext/S2589-0042(21)01487-5
> 280 TWh and the associated emissions is not zero impact. [1]

[1] https://ccaf.io/cbeci/index
What kind of coinbase account verification do you have to do to convert $150M?
Great video, saw it yesterday, need to see the second one ASAP
Everything I've seen on optimizing Postgres on ZFS
In 2020 a rash of anti-zoom propaganda that I'm almost certain was driven by Microsoft led to a company-wide prohibition on using anything other than Teams "for security reasons" where i worked.

This was, I am almost certain, inspired by Microsoft corporate sales getting their hooks into management.

This was largely because of news stories like "end to end encryption doesnt really work as advertised" and "if you leave a room password unprotected bad people will enter". The level of press coverage was off the scale compared to what Teams got for far worse issues.

The vulnerabilities werent nothing but they werent even in the same ballpark as the MS teams vulnerabilities foisted on us for "security reasons" like this howler they tried to cover up https://www.techradar.com/news/microsoft-may-have-downplayed...
See also https://www.medrxiv.org/content/10.1101/2021.12.14.21267615v..., which suggests (Figure 1) that two doses of AstraZeneca does nothing to prevent symptomatic Omicron, but that an mRNA booster pulls effectiveness up to somewhere near 75%.
> are they saying double vaccination had no noticeable effect on Omicron?

Practically, yes. See Figure 2. Recent vax (< 3 mos.) and distant vax (6 to 12 mos.) neutralization is between the first two eighth ticks for omicron. (Distant vax + infection is a bit less effective than distant vax with the wild type variant, which should put to bed the nonsense around prior infection being equivalent to innoculation.)

We need an updated vaccine and/or to refresh the vaccination requirement to including boosters.
Great take, honestly. Web3 is essentially just a more convoluted way to federate based on a decentralized database. But in platform capitalism, there are zero incentives to federate. For instance, your gaming NFT will work with one publisher, likely only in one game (have an NFT for Generic Football Game 2021? It'll be useless in 2022, I promise). It will mostly be exploited for the promise of what it could be and not for practical reasons. Also because we already build decentralized federated systems without decentralized consensus. Like the Fediverse.

It's all smoke and mirrors.
Others have covered good, general rules of thumb, but I'll go into a few specifics for why I generally avoid microframeworks. I've spent quite a bit of time with Rails, and whenever I try a microframework I'm immediately aware of all that Rails does for me - for free! Here's a few things I had to set up:

1. Configuration: This is way more important than you'd think and very difficult to get right. Consider storing aws credentials etc - Rails has a great, in built pattern for storing and accessing them, and the initializers pattern allows you to load them without contaminating the rest of your codebase with it. Plus, environment specific configs - especially env specific db configs - are super tight to have for essentially free.

2. Logging: more of a pain to get right than you'd think! Rails gives you an easy way to log anywhere, environment specific logging rules, logging to file and console and other such nice to haves.

3. DB access: You don't have to think about setting up connection pools or an ORM - it's built in and pretty capable. With microframeworks you have to hand roll the entire db access layer.

4. The glue: this is the biggest thing. You'll know it when you're three weeks deep into building a "micro" service and you realise you've essentially made Rails in Sinatra, except worse because it's buggy and poorly documented.

I love toying around with microframeworks - it's the best way to learn what goes on behind the scenes of a complex framework like Rails - but unless you knoe exactly what you need and why the mciroframework is better you're probably better off with Rails.
I think this is because modern computers abstract as much of the underlying system away as they can. Smartphones are hiding the concept of the file system under a layer of custom selectors and UI controls to the point of confusion about where files will end up.

Another factor is that (for some mind-boggling reason) it's still acceptable in some office jobs to "not be good at computers" despite working with them 40 hours a week. Whether it's laziness, learned helplessness or something else, people seem to accept that anything beyond the most basic functionality you need for your day job is left for the IT department or techy family members. There's no incentive to even try to learn, even if learning would increase your productivity and make your life much easier, because "computer stuff" is considered too difficult.

On the other hand, a lot more people are using computers today than they did 20 years ago. If you used a computer around the 2000s, you either had an interest in them or your boss had sent you a manual or a training course with instructions on how to use them for your work. Today, almost everyone owns at least one computer, regardless of their training and interest. People are just expected to know how computers work, despite no effort being spent on that in many educational facilities, while content consumption devices get ever more dumbed down.
> The test suite is not dependent on the frontend framework.

I have yet to see a project that changed some underlying framework and kept the tests intact. Nevertheless, i think a more realistic approach is to decouple your react components from the buisness logic, thus being able to at least keep part of your test suite if you actually migrate frameworks. Another practice I've picked up is wrapping the react-specific test utils into my own module and re-exporting them. I hope this will make it easier to make global changes such as when an api is changed or even the whole framework.

Generally I don't disagree with the overall sentiment, i just think there is simply too much value in the jest tests to just ignore them. The feedback loop you get when running jest in the terminal is way faster than cypress.