skysight-inc/HackerNews huggingface dataset:
That's a bit hyperbolic.

Would ECC have avoided the issue in this case? If so then it's hard not to agree that is should be considered a minimum standard. It looks like Yeti 2022 isn't going to survive this intact, and while they can resolve the issues in other ways, not everyone will always be so fortunate and ECC is a relatively small step to avoid a larger problem.
Have you ever worked at an org that size? Because many devs completely fail to even consider legal, let alone actually reach out to them before they implement something.
Good defaults are one of the most important, yet overlooked parts of programming languages IMO.

For example, no nullability or mutability by default is one of the main reasons why I like f#.

https://onor.io/2012/03/27/why-the-defaults-matter/
Analysis of 150k letters from the Founding Fathers and how their lives changed
All of that is true, my comment was based on US Housing trends as the context of this discussion is around the American Suburb.

Other nations have other issue, largely that they are locked in with limited amounts of land that can be repurposed for housing, thus this supply restraint is some of the cause of the price increases there. For example the nation of France is SMALLER in land area than the State of Texas yet has over 2x the number of people occupying that smaller land area

The US has TONS of underused land that is continually being developed for new suburban housing additions
I know what you mean, and that is probably still true for the majority, for the US at least, and in large corporations, but I think the world is changing.

Linux is the standard OS at my work. We use it on servers, so it makes sense to use it on the desktop too for maximum dev familiarity and compatibility, since it now works well there... it's even started to be used by some of the non-devs to reduce windows/mac update fatigue and general performance issues even though they only need office apps... I'm at a small company but I know of other large companies with big IT depts applying the "locked down OS image" approach to Linux for desktop too.

I find the concept of "windows" as the only safe OS image IT depts are willing to use, as fairly antiquated. Much like IE used to be the only browser you were allowed to use in many big old corps and gov agencies for "security" reasons.

Although this is an aside, the original context of the article was only "hackers" machines, and whatever your interpretation of that is, it probably doesn't involve fortune 500s.
That stings so bad. I’ve had this exact same experience of pressing somebody for proof, some measurement, a paper, some post mortem, anything. And I literally got the response “I read that in some book by some author in some chapter on some page I don’t remember”. I just told the CTO “sorry, but what do you expect me to do with this?”.

In some company where we offered a web API I couldn’t get the cto to publish statistics about endpoint usage. I became great friends with one of the ops, who I passed an awk script to run on all the web servers’ access files. Turned out that most of the supposedly critical endpoints with tight deadlines were used almost never. But for some reason people REALLY don’t like measuring.

By now I’m in charge of a software team, and I instill into everyone that programming should be engineering work, and emotional judgements are unprofessional and signs of a bad programmer.
Detect When a Website Changes with Visualping
https://news.ycombinator.com/item?id=27724389

https://news.ycombinator.com/item?id=27727150
this is the opposite of my experience at any large workplace.

you can look at merge commits on the history to achieve the same without losing power or data.
Hey, just wanted to tell you that the code you have currently doesn't compile.

`SentryHelper.h` is required for `ADD_EXCEPTION_CONTEXT` macro, which can be empty.
`HelpMenus.cpp` has a syntax error in preprocessor directives and an extra comma.
> I deleted my GitHub almost a year ago, after they offered me the option to do that or adopt a Code of Conduct on a single contributor project of mine.

Can you please elaborate on this?
Dell makes hardware that easily rivals Apple and sells it with Linux pre-installed and officially covered by their support services.
Public means a very specific thing in this context, namely Public Domain: https://en.wikipedia.org/wiki/Public_domain

Anything that is licensed has some level of exclusivity on it, and therefore it is not Public Domain.
With regards to Murkas Gem, the cloned horse, I'm kind of surprised that anyone is surprised that he's shorter than the original horse. When you geld a horse at the correct time, they often end up bigger than they would have if left a stallion.
Wonderful idea in spirit, albeit nearly every proposal runs counter to the social media company's profit incentive.
I currently do and have before actually, so I'm unsure if you have?

Devs can ignore legal for a very short time, but the moment you have a team working on it, you need legal approval to continue. And if there's going to be a public launch, you have an entire legal, data, and privacy team to vet it first.

Put simply, there is no universe wherein MS's legal team hasn't cleared Copilot before launch, and I'm disappointed HN groupthink believes otherwise.
The first note they provide is just about Burning Galileo at the stake. This strategy does not work and the only correct way is to inform the public. Education is the ONLY solution and this indoctrination path will only result in war.
>Only paying 10% on maintenance and then having perpetually potholed roads or a bridge collapse means the true cost is much higher.

The numbers out there suggest that for 50-100% more spending we could fix everything. That means spending 20% or less of the budget instead of 10% or less. Even a worst case scenario is not the apocalypse Strong towns suggests.

And more to the point it ignores the things that are a threat. As an example, today Flint spends half the budget paying pensions for retired workers. Then there's things like Social Security, Health care costs, education costs, and housing costs. We have a lot of large and looming problems that defy a simple solution. Infrastructure is easy by comparuson.
> are often called "cosmic rays".

No! This exact issue is a classic example because at one point the fault was attributed to cosmic rays by Sun before the true cause came to light. As another commenter has said, terminology matters.
Tell me about it, but this is nothing new. I am constantly being asked to make "just a little" change. In most cases, the cost is easy to see, but every now and then, I get a sneaky one, like the first example.

This is the biggest issue that I encounter:

> We run in to a complicated bug associated with what we're trying to do - so then we have to deal with the bug to get it done

Very often the "little tweak" executes a line of code that has always had a bug (AKA "Tech Debt"), but was never found, as there was no code path.

That's why code coverage tools are important (but they tend to be hard to find).

A lot of what I write are reusable tools, SDKs and APIs. I tend to write a lot of code paths that will only be of interest to certain clients. It's incumbent upon me to test them all, but I often miss one or two.
That is simply not the same thing as basic due diligence.
I've contracted and consulted for several SMB's in the past, and none of them had software engineers on staff. They would get software built/maintained via an agency that used contractors, or less often, by managing their own contractors without an agency's help.

Several SMB's had employees that had a job title unrelated to SWE, but still did lots of SWE tasks. Often these would be one individual maintaining an intranet portal, or some UI program for data entry that sales staff used.
Did anyone else read the full Twitter thread?

Companies have problems occasionally, it sucks for sure, but trying to place all the blame on Best Buy for you not being able to take delivery because you are in a hospital is nonsense.

The author has his entitlement bar set to the max and needs to come back down to earth.

Can we change the title to something like:

Random guy and Best Buy both contribute to delays of a shipment.

or

How the Amazon instant delivery model is causing people to set unrealistic expectations.
Ah yes we need to “rescue truth” by “policing content”
Doesn’t do anything about the viral nature of the GPL.
@epilys Could you please tell me which Huion Tablet do you use to take notes? I have wacom tablet. But it does not have a screen, so I am unable to use it as I am unable to coordinate my eyes and hand as I can't see what is getting written on the tablet (what is written shows up in the laptop). Any tips?
Check out Olber's Paradox. Basically, if the Universe were infinite, any line of sight would eventually intersect a star. Since radiation decreases in intensity with the square of the distance, but the area of "shells" of the universal volume increase with square of the radius, the light level of each shell would be roughly the same throughout the volume. In other words, everywhere you looked would be the temperature of the surface of a star, evenly paved in your sky. The fact that it is dark at night speaks against an infinite Universe.
Public transportation, bikes, and car sharing all make sense when cities are designed for it
Are you seriously not?
Agreed, very counterproductive to their mission.

I was able to get the site functioning with uMatrix still operating by using the vertical three dot menu and disabling referer spoofing. Even then it wasn't clear how to get to the content, since all that shows is a huge map with a timeline of events.
offtop:

What's the point of using google groups?
Yeah, I call BS
A widely used, large framework having really good code coverage is important, especially if not everyone uses all of the framework.
Worse. Collusion and election inference.
Tim Ferris's recent interview of Pollan is excellent, definitely check it out: https://tim.blog/podcast/

I think I might finally have the motivation to read his earlier book How to Change Your Mind
It matters if their online service has incorporated AGPL code.
> also when I disconnect CarPlay, it immediately turns on the radio at full blast.

Me too. Subaru?
On working too hard: finding balance, and lessons learned from others
> There are also many junior developers outside of big cities who have salaries more in line with the $60K range you listed.

My first job as a SWE was for a small startup in NJ (just outside of NY) for ~$50k/year. This was not even an area with a low cost of living.

The unfortunate truth is an employer will pay you the minimum they think you think you're worth if, and only if, that's above what they think you're worth.

Within 6 months I told my boss I wanted a performance review and I got a 50% raise (to ~80k) because my performance well exceeded the perceived performance at my original hiring.

Now that I'm more "senior", something else that I've realized is that hiring an engineer who has been around the block and has a wide breath of knowledge is a much larger force multiplier than hiring 20 engineers and having them scramble. When I look for my next gig some time in the future I'm not going to be pitching myself as solving just their technical challenges anymore. The business case will be "Not only have I solved the problems you're having currently, I've also failed at solving them. I know all the footguns of team leadership and technical stacks. If you want to spend your money efficiently and converge on a solution to your business and organizational problems I can help you get there... for a modest fee"

That is how you make a business person think you're worth your salt because, despite it not being true, "anyone can code" is a common sentiment among that crowd.
In my experience, as an American expat working in the EU, these countries have an extremely low level of churn. In most cases the only way to get a raise is to be hired away. So most developers put up with the annual CoL raise of 3-5%. Instead of changing companies every 2 years with a $10k-50k bump you stay 10 years in one company and eventually get a $10k over that period.

I know most Americans feel its the strong worker protections in the EU that cause the pay stagnation. It's far more complex than that. SWEs can leave for another company whenever they want. In some cases there are deep structural issues* that can keep you at a company.

* One example, in France there is no upper limit on the caution for an apartment. It can be as high as 20k-50k€. If you need to rent a place and don't come from a rich family your employer can provide the caution. Now that your employer has solved your housing problem you feel a certain loyalty to them and the 10-20 year career starts.
Leaked source code isn’t the same as licensed source code.
what does unit testing have to do with whether or not you instrument the test with fake responses? those points of contact that you're mocking out at the perimeter, that data will sometimes need to reach a particular function through a collaborator...which you may want to mock?

sometimes the dependency is not a third party, but it may be code that requires a ton of setup (as mentioned in article) that's not worth the cost. it may make sense to just mock at that point to actually test the rest of the business logic in a function. I don't think i'd say "well, that's no longer a unit test!". You can argue that it's a more brittle test, sure.

update: also, i'll be honest that comments like this really rub me the wrong way. This type of dogmatism around what is or isn't unit testing (which is a pretty ill-defined phrase in industry) is something that needs to stop. I think it hurts new practioners in the field who are mislead into black and white thinking.
no need to grow in this case, I prefer to stay where I am rather than going to a toxic env

that's one of the reasons why I like my existing company, they don't lie, pretty honest and transparent
> Got it, simply devise the correct level of modularization for an increasingly complex project at the beginning of time, to avoid annoyances. Easy peasy. /s

I know you're being sarcastic, but this is the "you know what every late project has in common - it should have started earlier" observation, just applied to program design. A killer thought terminating cliche.
Why the Defaults Matter (2012)
So what does he mean by public? It seems to me that he is essentially saying because he can see it publicly I can use it to train anything without caring about the license?

Based on his assertion, can I take a copy of windows (or github for that matter) and train an ML on it to replicate its behavior (assuming I have such a powerful AI)? It seems to me that is essentially what follows. In fact I'd argue that this is more akin to clean-room reverse engineering.

It also seems to fly in the face of case law for using soundsnippets in songs. Isn't what the model is doing really just a sophisticated algorithmic rearrangement of samples?
My current team does it, and it is so enjoyable.

We practice atomic commits that change only one thing, and in one way. We separate Fix, Refactor, Change, Add, Move and Remove commits from each other. Our commit summaries begin with those keywords so we can tell what "type" the change is. Each commit must pass CI 100% on it's own.

There are specific characteristics we've noticed. For example, for us, a "pure Refactor" commit either touches code or tests, but not both at the same time. If we touch too much we try to split it, or we call it a Change and it gets even more/different scrutiny.

Reviewing by commit allows me to give my full focus to each without having to keep all state in my head at once. I can step through and understand the series of changes. It's like telling a story, once I've stepped through each commit I am better able to understand the whole picture. If I only look at the summary some of the finer points are missed.

Also we've found we can extract commits more easily and get those merged early while we work on our main branches. If we see a Refactor, we can just do it, extract it and then keep our main PR focused.
Ask HN: Have you created a profitable B2B SaaS product? If so, what's the story?
Real PDF rather than crummy web viewer: https://www.yumpu.com/en/document/download/65717082/a63ac-8c...
> Given how hostile it is, it seems unlikely we'll go back anytime soon

NASA heard your July 4th plea, and sees you Discovery Mission 15 (VERITAS) and 16 (DAVINCI+). Targeted to launch in 2028 and 2029/30 respectively.

https://en.m.wikipedia.org/wiki/Discovery_Program

https://en.m.wikipedia.org/wiki/VERITAS_(spacecraft)

https://en.m.wikipedia.org/wiki/DAVINCI%2B
I don't have an incontrovertible proof and I secretly hope I'm wrong. A few observations:

* We already observed a techno "Green Revolution" in our recent past. Norman Borlaug, starting in the '60s and '70s. Directly maps to wild unprecedented population growth rates and population levels. 12 years to add 1 billion mouths to feed, 4 billions in a row.

* There are fluctuations in the growth rate over time and space, but this has less impact than our intuition usually grants because we don't intuit exponential processes well. Low growth rate populations are quickly (in historical terms) taken over by high growth rates populations. It's the very logic of biology: the eternal race between exponential growth and entropic decay is won by the populations with highest growth rate * entropy resilience. We can observe it with out fail in a Petri dish. We can also observe this all over the industrialized world, with the (temporary?) exception of insular nations like Japan and South Korea. The Amish will inherit the world.

* Adapting to the industrialized world may have temporarily created the illusion that the carrying capacity is much smaller than it actually is. People started to think that they need 5000 kWh / capita / year instead of the traditional 50 kWh. In the long run, as populations bulge, people will come to terms with reality and accept, out of necessity, much lower per capita energy consumption. In socioeconomic terms, more and more people will get used to "poverty". Techno-optimist socioeconomic palliatives like UBI will, inadvertently but likely, accelerate this process.

Edit. A few words about "poverty", seen as low per capita energy requirements. There are worlds of difference between:

* 2000 BC. Running for food in the big plains / forests.

* 1000 AD. Working the fields in a medieval setting.

* 1950 AD. Living packed in small pockets of industrial high rises.

* 2200 AD (?). Living in a world-wide sprawl of high rises.

* 2700 AD (?). Living in a world-wide artificial dome, Trantor style.

Perhaps the limiting factor will turn out to be that our mammal brains break down before the nigthmare landscape that our ever more efficient techno world will eventually produce.
If the average is raised in a process that is described in as implied form by say a gaussian distribution, the tails of the distribution increase by far more than the average. And for climate change the std deviation will increase too.
>>electric lines, gas lines, water lines, sewerage,

All of these are for profit business that should not need tax money to maintain..

>There are endless projects that need money to maintain and the current system of sprawl spreads that money too thinly.

If you look at where the actual tax money is being spent, is not being spread thin due to "system of sprawl" far from it.

In fact if you look at the actual data most of the time smaller cities have better maintained roads, schools, hospitals, and community centers than the more densely populated area's.

There is somewhat of a bell curve here, there is a sweet spot in population density, too much is a bad thing, and to little can be a bad thing.
> I also assume the parachute on the bombs were not for safety.

The parachute is to delay the descent while the airplane departs, although I'm curious if the plane can escape the blast of a 1 MT or larger warhead.
In fact, it would probably hurt their "fair use" argument to make a token effort to comply with more permissive licenses while failing to comply with the GPL. They're better off continuing to argue fair use.
I do work at a reasonably large one, yes. Less, then a month ago a new thing was announced, and among the comments, someone asked if legal was involved. The answer was: oh, right, we'll ask them.
Your reply is useless, but I'll rephrase to clarify anyway: how would one determine what percentage is appropriate for planning long term? I.e. so that I don't see potholes in 10 years, would I need 12% or 18% or 44% or <>% ? What factors would this depend on? E.g. is it always above 10% or only if the town has a very low density?
It wasn't clear from the article whether or not the released their Shot Manger plugin as FOSS or kept it an internal tool. I found a plugin called "Shot Manager" but it seems to have been authored by an unrelated Australian company (although some of the features sound very similar).

I am not saying they are obligated to release their custom tools. It would just be very interesting if they did. I am not in this space at all other than my kids are learning Blender and love it.

Tangent:
Completely unrelated to this, I am truly hoping that a large company takes interest in KiCAD and helps push development to the "production ready" stage that Blender seems to have achieved. The EDA market is in serious need of a solid FOSS tool that isn't driven by the latest shinny thing companies go after.

To be clear, KiCAD is absolutely fantastic and I am looking forward to version 6.0. We are planning on migrating our work from Altium Designer to KiCAD, likely starting around the end of this year. I'm sick and tired of what has been happening with Altium and the other tools are just as bad or worse.
There are also meta-analysis that show invermectin to be ineffective and even deadly. Perhaps you should educate yourself regarding the different meta-analysis available and how they differ (in particular, the one you cite is noted for its high bias.) Feel free to try [1] or [2] and assess the differences in outcome of the analysis when obviously garbage studies are removed or weighted less. Thankfully, we have several _real_ studies happening that are being conducted by people who know what they are doing and are not just surveillance studies but are directly looking at the efficacy of invermectin as a treatment option.

[1] https://www.researchsquare.com/article/rs-148845/v1
[2] https://cadth.ca/sites/default/files/covid-19/RC1336%20-%20I...
I've been lucky to have a number of great role models in my career, some of which shaped my opinion on hard work and how to find balance. I know the concept of "hard work" has come up recently, so figured I'd share my experience and some of the advice I received.

This is a polarising topic, and I won't be surprised if a lot of people disagree. These opinions are shaped by my experience, my context, and I'd be shocked if everyone found them equally applicable.
That's not how fair use works.
It's entirely possible that the slowness is on Netflix's end, especially if they're doing the English dub themselves. They frequently take 6+ months to release English versions of anime they license.
That assumes attribution is the only issue here. It's not. Code under open source licenses comes with other conditions (warranty disclaimers, release under open source license, etc).
> Public CAs are not that type of people

I think you hold public CAs to a higher standard than many hold themselves to.

There are hundreds of CAs and many (if not most) are shockingly awful.

Which is why we have had a huge push back against the PKI cartels.
Two AIs talk about becoming human. (GPT-3)
A human won't "accidentally" retype the source code to Quake, including comments, changing only the license - so no, it isn't like that.