skysight-inc/HackerNews huggingface dataset:
Once it has been determined that your position can be effectively filled with someone working remotely, you will be competing with all those in the same timezone/jurisdiction.

If the current tolerance for remote work persists, I fully expect salaries in companies of the S.F. Bay Area to drop significantly. With a fraction of the rent, this might still work out for the employee.
Don't double down out of pride or get flustered when you are wrong if you know you are wrong. To boot, nothing will make people remember you were wrong more than you making a fuss about whatever you are wrong about.
thx for your hint! we've adjusted it on our page (you may have to reload with clearing your browser's cache before). we will deploy a new version in the evening where we'll also include a link to the license. cheers!
It's possible that performance would be an issue with some use cases, startup times, etc. Eventually this will probably be a reality, in the same way you can't run DOS binaries without an emulator or VM
Remote job during pandemic and remote job are not the same things.
Discrete Optimization for On-Call Scheduling
Fair enough - however I haven’t heard the scientific community talk much of this problem. The unfortunate side of gated communities and information.

I will be more mindful of my ranting. Thanks for sharing.
I won’t remind them of my feedback but I’d never give up on telling them where they should improve.
So essentially, the onus of upgrading is on the person running the node. Which I guess is the more intuitive solution. But then what happens if someone doesn't upgrade, will they be just shut off from the network till they are on the latest version?
So long as the health threats involve UV exposure, so far.

But hey, I'm all for continued research in this area!
How does this differ from other similar sites?
Agreed. I grew up in the PNW, but in a predominantly black neighborhood. I married somebody who was from a very white new england suburb. They were downright intolerant of folks with a southern accent and literally called them stupid (the most memorable was an expert scientist being interviewed on NPR). It took several years of me bringing up that bigotry for them to come around and try to work on it.
Entrepreneur Raised $53M to Deliver Cannabis to Your Door
I guess I was using the historical view of magic - something unexplainable must be magic.

Technically nothing can go against physics, only against our current understanding of physics. Thus it would be similar to my example - just too complicated.
Do you

A) Trust the competence of the government to understand the nuance of technology to not pass a law that takes into account all of the Nintendo’s consequences. During the dog and pony show when the house had the 4 tech CEOs to testify, one representative asked Zuckerburg about Twitter’s policies.

B) The impartialness of judges, prosecutors and regulators? Trump is now trying to get a law passed because he didn’t like Twitter’s policies. Would judges appointed by the current administration be more likely rule in favor of “Planned Parenthood” or”Black Live Matters” if they both made a claim over @blm?

As far as a third party. I would much rather have an independent non profit set up and FB, Twitter guarantee funding for them over 10 years and they do binding arbitration. They woukd be hopefully better informed.
My experience learning Perl and Python after C/C++ and C# was okay I really get the obsession with unit tests now.

One thing notable in C you usually don't have to type the type name twice. But C++/Java/C# you do. That's when I think about it was a really bad grammar mistake. Java and C# shouldn't have propagated it.

Mentioned above I agree with, designing good types is non trivial. I think that's part of the problem that designing good API's is non trivial. I can see programmers getting the hate on when dealing with code bases with crappy types and crappy API's.
I would encourage you to put the idea of building a startup aside and just learn / have fun building things with no business utility first.

1. It sounds like you're already really curious so you've got your number one skill taken care of. If you're looking for a curriculum, start with something you're interested in and find the fastest, tightest feedback loop. Basically you want to be able to make something that activates all the reward centres in your brain or build it in small increments so you stay engaged. That might be learning how to write 3d graphics, build a website, basic javascript, etc. Find the smallest piece and just learn that.

2. Don't worry about doing everything "the right way". The whole point here is to try something, get a feeling for it, and then figure out how to make it better, how to write it differently, etc. You're going to end up realizing that one persons "best practices" are better than other peoples "best practices" and where you can make trade-offs (no1 skill imo)

3. As far as things to learn, that list is never ending. Just learn whatever you need to accomplish your goal.
Try https://fastrt.nilu.no/VitD-ez_quartMEDandMED_v2.html
and err on the low side if you're worried. Regular self-examination is always a good idea for everybody and essential for very pale skins.

Vitamin D productive begins immediately when the skin is exposed.
Running COBOL on AWS Lambda
I will never go back to commuting, and find very little need for on-site meetings or interviews.
Ligatures pretty much work this way.
Thanks for making that video emphasizing the idea of resonance and commercial design -- as well as social change.

Parts of the video on resonance reminds me of this one:
"This equation will change how you see the world (the logistic map)"
https://www.youtube.com/watch?v=ovJcsL7vyrk

Some other parts on design remind me of videos by Charles and Ray Eames.

You might want to consider adding Dialogue Mapping using IBIS to your design process if you have not already?
http://cognexus.org/id41.htm
This is complete BS, as the system learns to detect if a user answered "Yes" to the question of "Are you lonely?"
General rule: if you have remote participants, everyone participates in the meeting remote unless there is a good reason otherwise.
It depends. When I have a good idea of what I want to draw, and I want to put it in a document, I like to use TiKZ in LaTeX because it is fairly easy (depending on the domain) to produce something pretty that is consistent with the style of the document and easy to change if the surrounding text is edited. The overhead of going through an external diagramming tool is often not worth it in this case, unless it's a quick one-off note.

If I want to get an overview of a data structure, I like to write code that generates dot, which I then render using graphviz. I have successfully used that for debugging a few times.

When I use diagrams as a tool for thinking, I prefer paper and pencil, or, if I need to make many changes, yEd. I also use the latter for system diagrams (I prefer loosely following the C4 ontology) or for quick dissemination of ideas to colleagues when we can't be in front of the same physical whiteboard.

The only text-based diagramming tool that I use for thinking is plantUML, although I have only used it for sequence diagrams.

I don't have a lot of experience with using embedded DSLs for diagramming. I have used 'diagrams' in Haskell which is nice, although knowing the host language didn't mean that it was faster to learn the DSL compared to, say, graphviz or plantUML. It doesn't take a lot of time to learn the syntax of these things, it's all about learning how the primitives work and how they can be combined. An EDSL is mostly convenient if you need to programmatically generate the diagrams from data structures, since you can call the diagram library directly and avoid icky string interpolation.
Energy storage into hydrogen always made sense to me. Would make vehicles more attractive. Could be converted back to energy later onto the grid when it was cost effective. Certainly not efficient, but it is still useful work.
I've been working at a company that was remote for 7 years. We are DEALING with remote work. We're making it work, over many years of experimentation. It only works because everyone is remote. And the only reason they hire remote is because new startups cannot compete with FANG for talent in hubs.

Remote work is a compromise, not an advantage.
This 100%. If you're married with children, you most likely have less than zero need for an office-based social life.
Back end Frameworks with the most stars on GitHub
I don’t know if this is pedagogically useful, but I think of types as shapes, variables (including struct fields and function parameters) as a shaped hole, and values as a shaped thing that can fit (or not fit) into those holes. Kind of like the children’s toy. You don’t want to pass a circle in to a function that needs a square shaped thing, and the type system helps make sure you don’t do that by accident.
For what it’s worth, a significant part of my not seeing the value of types back in the early 2010s was the combination of my own immaturity with the pretty poor quality of the systems I was working with. You can make C++ do a lot of this work for you (albeit not quite as far as a language influenced by Standard ML). But none of the C++ I ever encountered in the wild in that era did. It was all the effort with none of the benefit. I spent many, many months of my life dealing with the exact same kinds of bugs in Fortran, C, and C++ systems that I was dealing with in PHP and JS and Python. So the feeling that resulted was: why do the extra work I have to do in Fortran and C and C++ if it’s not actually buying me anything? No doubt if I’d been working on teams which were effectively leveraging C++’s type system, I might have felt differently. But I wasn’t, so I didn’t.

For what it’s worth, these days I tend to talk almost exclusively in terms of the tradeoffs involved with adopting any given type system vs. the alternatives in the space. Even as an admittedly huge Rust fanboy,[1] I don’t think it’s a panacea or a thing you should pick for every project. To the contrary. And I’d go so far as to say that there are some places where something like Erlang is going to help you solve your specific problems more robustly than Rust will, which likely sounds like heresy to many fellow fans of type systems.

[1]: https://newrustacean.com
Ring Mailbox Sensor: Amazon quietly introduces mail surveillance
Relatedly: meal planning. Turning raw ingredients into food is only the last step. Just as important is figuring out what meals to prepare, what ingredients you’ll need, how to efficiently use those ingredients, how to take advantage of leftovers, etc.
I am intrigued, can you refer me to where Polands parliament voted for the empires to devide the country?
bcashers still seething on their failed hardfork.
> those who are married and/or have kids seem to prefer remote working and those who miss the office tend to live alone

I would have thought to be the other way around - parents miss office as they have to supervise and educate their kids while also doing their regular job.
It's not only the user name. It's the photos, chats, etc.

Of course one should backup the photos outside Instagram or any other service but I have no idea if Instagram allows that. For Whatsapp on Android it's as easy as syncing the pictures folder on the phone to my computer. Then I backup them with all my other files.
I’ve actually already experienced this. Once part of the team is in the office they will have quick informal conversations to decide how to do things. Only the decision is recorded and not the reasoning. Now with everyone remote everything is done in writing and everyone is included. I think hybrid setups will be the worst for employee happiness and productivity over time.
Continuum Mechanics
No AWS _is_ hard. It's hard. They're all hard. They require tons and tons of knowledge before understanding what to look at, how to use it, when to use it, etc. Everyone who thinks these systems are simple completely take for granted the years and years of knowledge they've acquired. Even in the form of shared vocabulary, AWS is insane. IAM is a whole other nightmare of complexity that is insanely powerful, but I wouldn't dare point anyone in that direction if they were just starting out.
How about OCaml, Haskell, Scala, or F#? All have pretty decent type systems, with Scala and Haskell even supporting higher kinded types.

I'm at the point where I refuse to write production code in a language that doesn't have an expressive type system. Dynamically typed languages are even worse.
Sept 27th Beat Pack and Free Streaming Calculator
CTO of Rainforest here. Having only recently done some MiniZinc, it's super fun and actually pretty accessible to get started with - but totally different to "normal" programming! Tyrant def made a difference to how much time / well we do on-call.
I’m disappointed in Sundar’s tone deaf vision for the future of work.

A hybrid model requires employees to be on site some of the time, and forces them to live nearby. It will also make people feel like they HAVE to come in to the office so they aren’t othered.

This also sacrifices some of the major benefits for employees like the freedom to live wherever we want, suiting our financial needs, familial needs, political/cultural needs, etc. We need to avoid having gigantic concentrations of our society in a few locations, and COVID lockdowns have proven we can make it work in knowledge industries.
I agree with this - I did udacity's original cs101 (http://www.cs.virginia.edu/~evans/cs101/), then cs253 on web apps, taught by Steve huffman, the co-founder of reddit. Then when my co-founder and I decided to work on our first startup, we decided Rails was the best option for noobs like us, and it probably took us just a few weeks to learn the basics of rails because we'd already completed cs253, I think it might have been harder if we had tried to learn it straight away. But rails was enough for us to build a telemedicine web app, and it wasn't until around 6 months later when our view was starting to turn into a mass of jQuery spaghetti that we started to learn and apply react. jQuery is great for doing simple user interactions in the browser, but as you try and build more complicated functionality, react is a much better tool for the job.

I agree about staying away from mobile to start with if at all possible at the beginning.

No rush, but sometime after or while learning rails, definitely take a look at the book "beginning database design" by Claire Churcher. It's the best book I've ever seen to learn how to design your database schema for a sql database. But you don't need it until you've at least made a few web applications, and like my experience with react, the best time is when you are trying to figure out what format to store all your data, and finding it too complex - that book gives you a great way of thinking about the problem that simplifies things greatly.
Capitalism is an economic and political system.

An economic and political system technically literally cannot care about people, same way as temperature, gravity, philosophy or history cannot care about people.
Has there been any research into the vitamin d levels of patients after periods in hospital? Do vit d levels fall quickly enough for being admitted to hospital (and so being indoors) to become an issue in treatment?
I think that ends up as user unfriendly as requiring the dot after the TLD. I don't read up on all the gTLDs so I didn't realize zip was one for the longest time. I think ICANN just went nuts with TLDs, especially ones like .app and .zip that have long-standing associations with ubiquitous file extensions. That combined with the "smart bar" just leads to trouble.
Not everyone, but it certainly is a cultural thing that needs to be managed, and a group being mostly in-person and a few remote is indeed problematic. Best-working example I know wildly combines people from different offices - so while many "go to the office" and have a local group of colleagues there, the work is always done mostly remote and not in-person. And even then, you need to pay attention to include remote people in the informal information flows.
WAL-E/WAL-G are another option if you're looking for PITR.
same. I started a remote job in 2018 and was just looking to go back to onsite when covid hit.

I'm a very enthusiastic engineer and love bouncing ideas off others, whether they are in sales, marketing, or other engineers.

Remote has made "connecting" much less natural and makes it difficult to progress in my career.

If you're the type of engineer who likes to be given requirements and sit in your home office and code all day in silence then power to you. Not for me.
You mean Amazon?

What do you mean?
Well, in certain ages, like after the fall of Rome, most knew less than before...
Honestly I think people who object to typing are lazy and inconsiderate to other people who will need to read use and maintain their code. They often haven't had much experience and haven't worked on large code bases in my experience.
Elon Musk slams Microsoft exclusively licensing OpenAI's GPT-3
Learning about nutrition and fitness, even if you don't do either rigorously.

Patience and also how to firmly and kindly say, "no."

Art is a pretty nice hobby that works your ability to observe and visualize. Sort of like meditation when you're in the "flow" of it.

Playing an instrument is similar. Having a hobby that is active, not passive, and relaxes you is great.
1. How to spend less than you earn. Lots of people desire “financial freedom”, meaning they can spend what they want when they want it. Solving this via revenue leads to the hedonic treadmill, and you’ll never out earn your growing wants. Instead solve this by controlling your wants, and you’ve achieved financial freedom immediately.

2. How to take risks. Finding the balance between recklessness and absolute risk avoidance is about managing downside, so you get a chance at the upside with acceptable consequences if things go wrong. Get this right, and the world is your oyster, even if this is your only skill in life. Get this wrong, and it will swamp every over accomplishment, skill, and strength you may have.

3. Know what you want, and why you want it. The worst thing in life is time wasted winning at unfulfilling endeavors. The “winning” sucks you I’m and keeps your trapped in a local maxima, where all roads look like moving backward. (Usually, this means understanding and controlling your need for status vs your other needs—-and that requires a lot of introspection.)
Yep we have done this even before lockdowns. If even just one person is remote, we ask everyone to call in rather than going to a meeting room, to force the meeting to be run in an accommodative manner. You need these practices if you collaborate with teams in different offices anyways.
Strong disagree on not learning AWS (or another cloud provider). I was partial to AWS even before I worked for them, but chances are you're going to run your startup in the cloud. For that, you should know at least the basics of the cloud you're going to use.

I'm not saying learn CloudFormation, CodeDeploy, or any of the hardcore DevOps stuff you'll be interested in once you start to scale.

But you need to know how security works (i.e. IAM), how to build networking infrastructure (i.e. VPC), how to deploy servers and databases (i.e. EC2 and RDS/DynamoDB). And, of course, how to do things cost-effectively.

If you don't take the time to learn the cloud, you're going to be stuck when it's time to push your project into production. So you're going to need to:

1.) Hire a cloud architect. This isn't cheap nor is it a good solution. If you ever part ways with your cloud architect, you're going to be starting step one all over again. Except now you have to learn how the cloud works and how your environment was architected. And that's assuming your architect doesn't maliciously make a mess of things on the way out (which happens -- A LOT).

2.) Open a support ticket for every little issue you run across. This can easily become a blocker with deployment. Not to mention you're likely going to have a developer support plan. Which means you get email-only support and the replying support engineer may not even be in your timezone.

So not only do you have to deal with the inefficiency of back-and-forth email conversations, you may have to deal with the time lag based on the engineer who works on your case.
I too have a well. For the curious, I estimate that it takes about $0.27 worth of electricity for it to pump 1000 gallons.
The title font is so heavy it's difficult to read. Also, poor vertical space utilization.

Maybe make design more similar to HN?
How can one be "accurate" in one's opinions?
Interestingly, most mainstream media had open offices way before it was cool.
> If you have the option between creating a function which accepts a string (e.g. ID) as argument or accepts an instance of type SomeType, it's better to pass a string because simple types such as strings are pass-by-value so it protects your code from unpredictable mutations

What if you work in a language where SomeType is pass-by-value?

Would you still prefer the string?
> High availibility is a bit more complicated to set up with Postgres, and I don't have much experience with that part.

There is Patroni[0], which has a Docker-based setup template in Spilo[1]. I don't have expertise enough to say anything about these, except that I've been running an HA setup with Spilo for several months without issues so far.

Would be interesting to hear what more experienced postgres people have to say about it :)

Also we've opted to just use traefik (based on spilo service registration) rather than pgbouncer.

[0]: https://github.com/zalando/patroni

[1]: https://github.com/zalando/spilo
Probably for the same reasons Rust is more popular than Ada or D.
I'm mortified too, this is a very good case for laws against ads targeting kids
> IMO it is because they are mostly used by more experienced programmers, that can already layout the types in their head.

> Try to teach the average Java programmer (I'm not saying I'm a better programmer, Iḿ just intending it as "they are trying to get through the day with the tool they already know") how to effectively use types "like in Haskell" and they will be confused at best.

Counterpoint: I don't use any ML/Haskell languages regularly, but I do use a couple of projects written in them[1]; my preferred language is Common Lisp, the It dynamic language. When I needed a feature, it was dead simple to do so.

1: matterhorn, the Mattetmost client and bower, the E-mail client, which are written respectively in Haskell and Mercury.
I’ve asked danny on Twitter if he can confirm this.
Are we seriously just going to presume that this is true based on a hacker saying "my friend works at facebook"? This feels like the Apple refund thread all over again, with the same problematic outcome if it turns out to be false - people not seeing the rebuttal and still thinking it actually happened.
Just mark as spam. I actually mark everything as spam. I don't even click unsubscribe.
Yes, low vitamin D is an indicator of frailty, so surely not all of the observed difference is causal. OTOH, giving people vitamin D in a RCT does seem to improve outcomes, so it looks like there's something real here.
The only evidence of Facebook being involved is the hacker claims it?

Seems somewhat flimsy...
>It's unlikely that humanity as a whole will be lost.

Unlikely, but not that unprobable. We're one of the most easily wiped out species... Cockroaches and tardigrades will be doing fine in many circumstances where we'll be toast...
That's why I own fakefakefake.email it gives me some minor pleasure to provide this email address to people who insist on having an email address for me.
One thing most human beings can do as a shortcut to this: have a child.
Fraud seems a stretch. Maybe if you used your handle for commerce and someone stole it & attempted to sell the same product.

It doesn’t strike me as litigation you’d be likely to win.