skysight-inc/HackerNews huggingface dataset:
Judging experts because you won't be doing most things on the basis of your own original reasoning.
Prioritization otherwise you get attention hijacked too much to accomplish your goals.
Emotional stability or you get jerked around by current events.
Communication or you don't get any buy in on your positive visions.
If they did, Microsoft sues, and the programmer is asked under oath, everyone knows. Unless the programmer decides to lie under oath, which will only make matters worse eventually.

If they claim they just reverse engineered the code, they're in an equal amount of trouble. Reverse engineering is illegal in many jurisdictions, unless you manage to do it in a very specific way which should still results in different code than what Microsoft wrote.

The more source code leaks, the harder it becomes to claim plausible deniability. Ethically, I think that's wrong and should be fixed, but the copyright and software protection law is against compatibility projects like these when it comes to legislation.
Drawn ahead as of August: https://www.iea.org/data-and-statistics/charts/global-electr...

Strong sales in July and August, particularly in Europe.
The question is: What do you want to build? What problem do you want to solve?

If you don't know yet, then figure this out first. It is useless* to spend your time reading about how blockchain solutions on AWS work when you don't have a plan what to do next with this knowledge.

*) except if this interests you personally
"Climate refugees" keeps being repeated ad-cliche as if it were a guaranteed near future event, but I'd love to see the concrete scientific evidence backing up its inevitability. Also, please, show me one single movement of climate refugees to have occurred so far who moved place specifically because of human-caused climate change.

By example: I live in the tropics, and while many people leave this country for assorted reasons of economic opportunity and bad local/national government, nobody has yet left because of global warming.
> "Let them eat extensions" is a recipe for fragmentation.

not neccessarily

in machine mode (think firmware or hypervisor level) you can trap on unrecognized instructions and handle them retroactively in software), so maybe fragmentation wont be (at least technically) a big issue....
Now scale this for a family, 3x per day for different tastes. Can be done, but this is where the true skill of cooking and planning shines.
Learn about building a company, product market fit etc. and start using no-code or low-code tools. Get traction, then get really good at finding a tech co-founder.

I think it's probably easier to find a good tech co-founder nowadays than spending 50+ hours a week learning how to code. There are so many ways a startup can fall apart even if you know how to code!

(I'm a tech co-founder, and for better or worse, I spend more time building relationships, sending emails and business models and planning than writing code)
Yea, I agree and for this reason when I teach type systems to new programming students, I tell them that a type is somewhat analogous to a building material. You have brick, wood, steel and iron. You want to build a house that has solid bedrock and has easy forest fires in the area. What material would you use? Most would say rock.

Then I tell them about strings and ints. You can represent 66 both with strings and ints, but one is usable for computation where the other one is simply usable to write Alice in Wonderland with it, or simpler forms of text. Sometimes I get the question then: why can't a string both be computational and as a means of character display? And then I list the upsides and downsides of such a system, just like the upsides and downsides of mixing brick and wood to build the outer wall of a house.

I'm curious if people can think of other analogies that they use for teaching.
About the rebar, yes it would oxidise and rust but would it not then react with the surrounding concrete and leave traces, "patterns" behind? Become a special type of mineral, just like so many other minerals that have categorization and names, etc.
Coffee shops, too. I have a friend who owns a coffee shop (I live in Europe) and I was afraid that he’d have to close it down for good. He’s been allowed to open again since 3-4 weeks, and even though the first couple of weeks after re-opening things were slow lately I’ve seen more and more people going there during the day in order to work. Things are not yet at the pre-pandemic level, but we’re slowly getting there.
What was the experience using Nuxt.js like?
I'm not rabidly anti-static typing. If anything, I -prefer- it. I use Dialyzer and type specs when writing production Erlang code. I actually -wish- Erlang had better static typing options.

But I recognize that as -personal preference- when it comes to Erlang. It allows me (and my teammates) to be explicit, and the machine helps me (us) be consistent in my explicitness, even when, again, via experience, I know it doesn't really effect how reliable the code is. Reliability in Erlang comes from testing, and proper supervisor patterns and reasoning. Static typing might reduce the number of supervisor restarts, but it doesn't reduce my test surface, nor the need to ensure arbitrary restarts get my system back to a good state. Even when using Dialyzer, it didn't push the needle on how reliable the system was. It just changed the characteristics of writing/reading the code; a bit more work to write, a bit less work to read.
Auschwitz memorial director offers to share Nigerian boy's blasphemy jail term
Maybe less than others but we're not unaffected. Boston is very susceptible to sea level rise and fisheries are going to be turned upside down from a warming ocean.
> Without the annotations, you can't look at code and know what is going on. Which, ironically, is the complaint against dynamic typing.

My complaint is the compiler doesn't know what is going on.

> In addition to that, you get the pain in the ass of having the compiler always complaining.

This cuts down on the time required for the programmer to decide whether to complain or not.

> I've worked with dozens of TypeScript developers and not a single one really knew what they were doing.

I'd hate for them to start committing code that can't at the least be checked by the compiler.
Isn't reporting them as spam

If you are using an e-mail provider that does something about it.

I have a GMail address that receives spam from several specific companies regularly. I've marked the messages as spam every month for at least five years. They keep coming, and GMail keeps showing them to me.
Absolutely. Somebody, somewhere used to say that Erlang is neither static, nor dynamic typing, but somewhere in the middle. I can agree to a large degree.
Previous discussion of this despicable action by Google:
https://news.ycombinator.com/item?id=24594663
This sounds to me like not a failure of automation as such, but of process/knowledge management by the team that builds the automation. No process is permanently exempt from entropy.
Expletive.
You can get a blood test from DirectLabs in most of the US for vitamin D for $50. Don't know if you think that's cheap.
I use a Python debugger in VSCode and hit the necessary breakpoints to figure it out.

Yes, it's bad, but it works. I hope there are better ways of doing it, but this is my way.
> Java is an extremely poor example of a helpful type system.

With generics added 15 years ago, lambdas with argument type inference 6 years ago, local variable type inference two years ago, and ADTs and pattern-matching [1] gradually rolling out already, Java is practically becoming an ML. I say that as someone who likes both ML and Java. The two are becoming so similar that I think it's a stretch to claim one of their type systems is more helpful than the other.

But I think people overlook type systems' biggest benefits. Empirical observation has not found any significant benefit to correctness in general (although there seems to be some in particular cases like JavaScript vs. TypeScript and I wouldn't be surprised if we find it in Rust vs. C), but the main benefits are code organisation and tooling support (refactoring, code completion).

[1]: https://cr.openjdk.java.net/~briangoetz/amber/datum.html
That’s a bug with your email client then

Don't blame the victim. GMail does this. I have the same problem, and I only use GMail's web interface.
Please see https://news.ycombinator.com/item?id=24608351 and please stop.
rep movsb
> I see a lot of comments on HN the last few years that just assume the dynamic vs static debate was settled at some time. It never ended. Static typing merely became trendy because dynamic typing was the trend for many years (Ruby, PHP, Python, Perl, JavaScript). Like all fashion, things that are trendy will once again become untrendy, and the cycle repeats.

It’s because the ergonomics of the previous generation of (mainstream) languages was cumbersome. No sum types, no type inference, nullability all over, terrible error messages, abhorrence of expressions, etc. some of those things are only indirectly related to static typing, but many people mistakenly attribute them to static typing nonetheless. The new crop of mainstream statically typed languages wed these quality of life improvements with the rugged practicality of the previous generation of mainstream languages (none of these features are new, but no serious team is going to switch from C++ to scheme for the type inference alone).

> With that said, it's important to note that type inference is not new. I was doing type inference with Scheme nearly 20 years ago. I believe the reason it never took off in a serious way is because it combines all the downsides of dynamic typing with the downsides of static typing. Types are meant to document code. Without the annotations, you can't look at code and know what is going on. Which, ironically, is the complaint against dynamic typing. In addition to that, you get the pain in the ass of having the compiler always complaining. And because it's inferring types, the error messages are towers of baffling nonsense. It's the worse of both worlds.

Type inference is very much a “sweet spot” thing. Like many things, Rust nails this: you have to annotate struct fields and function arguments, but within a function body you get inference. Changes outside of the function don’t result in type errors inside of the function. Locality is key.

> One thing that never comes up in these discussions is the idea that creating good types is a skill itself.

This is an interesting point, and I agree; however, I think the issue is less that it’s hard to do and more that dynamic typists don’t see it as a worthwhile activity at all—“why should I try to create good types? I just need to get this happy path working so I can get on with life!” Of course there are abundant good reasons (we should care about quality and maintainability and not just superficially churning through feature tickets at the expense of all else), but I think this is a sort of fundamental disagreement between dynamic and static typists.
I generally wind dark (but not black, more live a navy blue or dark grey or similar) better for stuff with lots of color (e.g. code) but light (but not white - creme like HN or a kindle screen) much better for reading paragraph text.
kwargs makes me so angry in docs. Pass in anything! Learn the whole library to use this function!
In your calculation using that table you are leaving out the income of the top 1%. The 99%ile represents the income of the top of "the 99%". In table 2.b, in the main article, you get a taste of the size of the 1% income, which is on average twice the 99%ile.

In the paper I didn't find figures that I could use to reconstruct how much money would have to end up in someone else's hands to achieve the counterfactual, just that it's obvious that the 1% average going from $1,384,000 to $630,000 would represent a lot on its own. The other groups above the median would also have received less of a share. Also note that it may have happened that between 2007 and 2018 the 90-98%iles may have already received some of the money that used to accrue to the 99%ile, who knows why.

I think BI properly quoted the article, but there would be a lot of work to do to contextualize the whole thing. If growth were more shared, would there be more or less growth? That depends on whether the top 1% are actually creating GDP or whether they are just better at capturing the income from it. If there was a system in place that had paid the bottom 98% more, would there have been more inflation, eating away at real GDP growth? What does that big swing from 2007 to 2018 really mean for the 99%ile in C1b, not reflected in C1a?

Honestly, this paper raises more questions to me than it answers.
Always take these opinions with a grain of salt.

Remember Google was the promoter of the open-space office configuration, and that trend ended up being a terrible mistake for a lot of companies that followed just because it was the latest fashion in office design.

I had bad experience with it, in the context of a Media Agency, to the point where I found that more than 10 people in an open space starts to become too much. 15 to 20 you need to have headphones cranked up in order to be able to do any work.

So bare in mind that just because it's Google doesn't mean they should be the trend setter. Google does what Google thinks will work for them.
https://www.bitrefill.com/
What I have trouble with but for a time i managed it. I think is one of, if not the most essential life skill is learning to initiate a lot of conversations with total strangers. I do want to emphasize the 'a lot' part, because this is not about being good at conversation (some people are, some aren't), but doing this a lot. Using this, you can make friends, but you can also get professional opportunities or dates or you can find your way about a foreign place. It takes a lot to get over the inner awkwardness but if you manage to do it consistently the rewards are just as consistent.
What made it miserable, if you don't mind me asking?
The first book I read about sales emphasized inquiry before advocacy. Let's get real or let's not play by Mahan Khalsa.

I read it at a point in time for my startup when we had done as many Customer Discovery interviews as we could in our local market, and were trying to achieve a first sale or pilot project with customers in more innovative markets. The inquiry phase of solution selling connected with and reinforced the customer discovery process, but provided some indication of how to move forward, and cautions about moving forward too early with a proposal.

The key to sales is solving problems. You claim to have a product that addresses a large "potential" - what problem, and for who, does it solve? Can you measure the impact of the solution?

If you have a product that solves a problem, what is the least intrusive thing you can ask of a potential customer for you to identify if they perceive they have that problem, and if they recognize the impact of solving it?

If you cannot mutually identify the problem and impact of the solution, a prospect may only entertain your talkative nature to solve the problem of looking busy to their superiors.

Track the observable characteristics of your prospective customers that are the best indicators of if they have the problem you solve, or not.

Figure out how long it takes you to identify if they have the problem, or not.
You are asking the wrong question. "Why use an RPN calculator", would be the better question.
But there are still some answers, why an HP calculator. The build quality and the buttons on a HP calculator are just so much better, there is no contest.
You say on a TI-89 you can spot a typo easily .. maybe .. I belive you catch errors better and quicker with an RPN calculator, because you allways see a result after each step.
And if you need a TI-89 to stop you from adding meter to ohms, then I don't know ..
Try a free RPN app and after a short time you will see, how it feels more natural to use this kind if calculator.
Nationalistic flamewar will get you banned here, regardless of your views or how strongly you feel. Please review https://news.ycombinator.com/newsguidelines.html and stick to the rules when posting here.

Maybe you don't owe America better but you definitely owe this community better if you're participating in it.
Great point!
USPS not only delivers xyz package quicker from the same to/from zip, but they are the only of the three that will actually deliver packages early than originally promised.

UPS and FedEx only, and I mean only, deliver on-time OR later than promised. NEVER earlier than promised. Additionally while UPS and FedEx say that there is a daily cut off time, this is almost always meaningless in that the first day never counts towards time-in-transit (which ,in terms of days, is already way longer than necessary from the start).

They both act as if they were to occasionally deliver a ground package a day earlier it would keep people from using their outrageously priced 2-day and next day services. Ie 13$ ground vs $137 next day.

Additionally UPS and FedEx (in my case mainly FedEx) are the only two where a package (generally on Saturdays) will get marked as “recipient not home” when I’ll check my cameras to see they never even attempted delivery.

both of their “guaranteed” time in transit maps are not worth the pixels upon which they are rendered.
Rambling while I drink my coffee:

Tech stack:
React + Nextjs (react-query, graphql-generate, typescript), Django (admin panel, celery for background tasks, channels, graphql), Postgres, Redis (for celery and websockets). Postgres in RDS with auto rotating secrets. Deploy as a Django as a Docker image on AWS. Access keys from Secrets Manager at runtime (this is your pre EKS setup). Deploy frontend app on Vercel. Use Stripes newest payments system for billings. Deploy everything via GitHub actions PRs and use Actions, including the new code and dependency checks.

Bam you’ve got a frontend with a busting cache, websockets for automatic updates, ability to do server side rendering, and all the content management systems from the Django admin panel you would have setup by hand with Express/Flask. You can choose to use any method of auth that Django provides or go with Auth0.

Using graphql-generate and Django Graphene you can auto generate your typescript SDK on your frontend. All you have to worry about now is your view code and your models structure.

Using celery and celery-beat will allow you to do long running or scheduled tasks. Connect it with Django channels and push updates from a celery worker to the frontend.

GitHub will keep it up to date and check for security errors with automatic pull requests.

Expansions on this architecture include:
- switching to EKS (useful especially for secrets and scale)
- Infra as code via Pulumi to switch to any K8s provider
- Using RabbitMQ for more robust messages passing over simple Redis queue
I mean, you can look at VW’s existing electric cars, which sold nearly as many units as Tesla did in Europe in H1.

The eGolf got good reviews on this; standard VW quality interior.
But it made them so much money!!
>If not, I’m not sure why you would care one way or another. This doesn’t affect you.

Say that to all teams that have been reorganised around two pizzas.
I don’t think it is possible for someone to register a gmail account name that contains dots. Therefore the mail you are getting is just people sending it the wrong address.

I also have a "${lastname}${firstname}@gmail.com" email account and experience misdirected emails somewhat frequently. I wish more websites supported a “delete and recreate your account” feature, because some of my account were principally created by someone else and I can’t edit the details (Hulu).
I think this is forgotten a little by the advocates of WFH vs in-office.

I live alone in an apartment with 2 bedrooms, of which one I converted into an office space. It's easy for me to "commute" and have a separate area for work and switch off when I go into the lounge. It's not so easy for people who are in shared accommodation or in studio flats and so on, or young families in small apartments.

Similarly, lots of people move to work and don't have a social circle yet, so their job is their social circle at the beginning. Of course, you don't necessarily need to move for that job any more, but at the same time if you have, then you lose your only social contact if you have by working from home.

It's not as simple as people make out, there are benefits and disadvantages to everyone.

I'm a big fan but I can only talk from my position which is quite fortunate in terms of circumstances.
I'd take a look at https://cushionapp.com/blog and https://cushionapp.com/running-costs/. He's posted on here a couple of times and has a setup that is very similar to what I'd roll with if I was going to bootstrap an app: React, Rails, and Heroku. People on here like to hate on the React ecosystem, but it's pretty straightforward if you stay on the paved path of create-react-app, react-router, redux-toolkit, and material-ui.
We have a free market, this isn't the DDR were only one car was sold.

SUVs and pickup trucks sell. A lot. Yes even in the cheaper segments- you can buy a new SUV for under €25k.
Clearly people like them.
The 41 is what I'm used to so it's what I use as a phone app but it's the older calculator. Leaving aside differences in the original physical form (which were partly to accommodate the HP-41 expansion modules), the HP-42 is the more advanced calculator, albeit not really a direct upgrade.
Maybe your intuition provides an analogous but different conclusion that may be more suitable to novel conceptual models of reality. Pursue your intuition I’d say. I’m in a similar path.

Oddly I find music to be a good hint of reality lately. I wasn’t too interested at musical theory but now digging into it the geometrical spaces it shadows is inspiring. Projective geometry allows continuity. Axiomatically it also allows arithmetic among other things. Very intriguing.
When will people learn that capitalism literally doesn't give a shit about people.
Forbes reporting is mostly factual. They don't employ much fact checkers, but don't do glaring errors. Forbes has some Chinese bias and has been criticized for it. It's owned by HK investor. Forbes also has some columnist's who are not very accurate in their opinions.

Those who post in blogger.com or medium.com don't have any responsibility to anyone. I think your opinion spreads the "they are all the same" message that is infantile.
I'm noticing at our company those who are married and/or have kids seem to prefer remote working and those who miss the office tend to live alone.

There are obviously many factors that can affect a person's happiness and it's always good to hear people's perspectives. Why do you find it miserable?
> think of the comp savings when you hire from outside the Bay Area

Just considering the US, I wonder how many engineers are talented enough to work for Google, are interested in working for Google, and aren't already there, even in a satellite office? I'm sure there are some, but between a variety of office locations and good pay, I'm not convinced there's a large untapped pool of rural tech talent.
I don't have to look at my static code to know that it is doing the wrong thing. The compiler tells me. This is impossible with dynamic languages. It is obvious that you never used types otherwise you wouldn't have come up with this nonsense.
Misleading title. It gives the impression that Google tried WFH, found it to be inadequate, and took a U-turn, saying 'on-site work' is the future (as well as the past, and WFH was a failed experiment).

But in the body of the article, the CEO is advocating a hybrid model, with increased flexibility for WFH, so much so that working from office are being declared special days (meetings), labelled 'on-site days' ('on-site meetings').
> ather than be the snarky one where everyone else nods in agreement

Satoshi's discussions on BitcoinTalk were definitely not snarky, but fairly well measured and objective.