skysight-inc/HackerNews huggingface dataset:
I find remarkable how simple it appears to be. You could take any existing Pico-based board, find two unused pins and solder on those four components. You update the software and suddenly the project is network-connected! For most other micro controllers this would either be impossible (dedicated pin already occupied with another function), or would require installing another PCB.
> Your rhetorical questions don't match OPs story. According to OP they did pay, manually, not even by credit card.

That's fair enough - somehow I completely misread/understood that part of the post.

But my main point was that you should never be using credit cards for services that you rely on - particularly when billing/payment is automated and hidden from you. Credit card payments and checks fail regularly (10%+ for recurring payment charges) for legitimate (you don't have funds) and less legitimate reasons (a banks AI system thinking the charge looks fraudulent due to something outside of your account etc). Vendors are likely to stop the service as soon as they can get away with so they don't loose money.
The idea that there is only one way to propagate errors, namely "up" in the call stack, is totally misguided. IMHO. It leads to function call dependencies, and ultimately to the kind of code where we're thinking to much about the code and too little about the data structures.

There is an alternative to returning error codes or throwing exceptions: Put the errors on some context handle - e.g. set an error flag. This taints the context where the error occurred, and if you do it right you can contain the error and replace / restart / shutdown that context in isolation.
And importantly, it allows the client to do the error handling at a more central point.

This kind of design can require that you do a little "paranoid" error checking at several entry points in the implementation of your API, but it's well worth it given that you save a lot of immediate error checking on the client side. Also, if you structure things right you can minimize the need for error checking in the implementation itself.

A simple and well-known example of this approach in C would be the FILE API from stdio.h (fopen()/fread()/ferror()).

This and returning NULL/error codes is how I structure my applications. I have a strong distaste for exceptions, for the same reasons mentioned in the other post citing Joel Spolsky. But exceptions are fine for quick and dirty scripts. And some people maintain that you should structure whole applications purely with RAII and rely on exceptions to cleanup your contexts perfectly and immediately. I'm not convinced that this is practical, but honestly as probably most, I'm content just living in my own bubble...
Having just read the headline... but to me it's not a pointless metric because it exemplifies that there's more to software development that purely writing code.
Apple workers launch petition over firm’s return-to-office stance
Jelly 2 for the win!
* If it's an actionable error, catch it as low as you can action on it. Otherwise let it propagate.

* If it's a useful error for another developer (or yourself) to see, log it.

* Use different loglevels in your code so another developer (or yourself) can increase or decrease the verbosity of your logging in different environments and under different circumstances.
Kudos to you stepping out and up and getting what you’re worth.
I tend to log errors right where they are thrown, and have a separate global error handler that deals with all the exceptions that come through from various parts of the application.
I throw exceptions for anything that isn't an expected result. Request a row from a database that doesn't exist throws an exception NoResults let the caller decide what to do.

The caller can then recover from the exception by searching else where or using a default etc.

If the exception can not be recovered then its an error. If its a user error like asking for a result that doesn't exist ill notify the user without logging. If its an unexpected error the exception is unhandled and bubbled up to a global exception handler that logs to a file.

Some times ill setup an email on error if the code is important enough.
Not sure I follow, even if coal were used for heating in Germany. Would the country be in a better environmental situation overall without the activists? I don’t doubt there’s some level of energy hypocrisy currently going on in Europe, but I don’t see how environmentalists have exacerbated the current crisis. Are you referring to their opposition to nuclear energy?
From the discussion:

> - The link says "my friend got this", so even the person who authored that post isn't claiming to have received this notice. This is a second hand report, at best. For all we know, their friend received this notice years ago, and mentioned it to the OP, who didn't realize it was old news.

There have been people confirming in recent HN discussions that they were using full 1gbps of their dedicated box for a while since Hetzner declared their true-unmetered policy a year or so ago.
Interesting. I’m learning and find yeah, most of my time is spent researching, learning, etc. but still could get in an hour - then of course, fixing bugs, mistakes, interactions with other code, better options.

Makes me feel a lot better about my progress.
That's true, I was going by dance-all-night/loud-music one
Archive.org rescued 430k tracks of music from mp3.com (1997-2003)
For a company that operates at such massive scale for their own services, Google has some glaring oversights when it comes to enterprise services.

I have a friend who volunteers as a webmaster for a charity org and they kept getting notices about their impending shut down of G Suite and the need to move to Google Workspace. The problem seemed to be a credit card and yet, when my friend was showing me on his laptop, there was no place for them to enter credit card information. They ended up losing all their email and Drive & Docs access for days and couldn't even get an email or phone address - paid or not - to address the issue.

After getting burned at a mid-sized business I used to work at with Angular 1.x and Google Glass, I learned that Google apparently sees business services as experiments rather than long-term investments.
If I'm in the office and go to a meeting room I have to bring at least one adapter to be a able to project on a screen. It's awkward in practice.
It's good to see a a return to more varied ports on board!
Soviet state implemented food rationing everywhere to help the famine in Ukraine. And, at the same time the Soviets had famine, the US also had famine during the great depression. Except, Hoover government did absolutely nothing about it, leaving it to the 'free market' to solve for ideological reasons. The amount of people perished during the period is unknown. If the same formula that is being used for calculating 'deaths' in socialist states is applied to the great depression US, the death toll comes around a 7 million people.
For perspective, my country/culture is intolerant of people not interrupting - and not taking well to being interrupted themselves.

They're are seen as precocious uptight snowflakes - and their protest at interruption (not as in "let me finish", but as in protesting the notion of interruption itself as if below them) is considered impolite and in bad form. At best it's seen like, let's say, eating a slice of pizza with fork and knife in New York.

They are seen to want to monopolize the conversation, or make it not a real conversation (with interruptions, back and forth, and genuine exchange) but a series of monologues from each party.

If we're discussing, we're not there to hear a diatribe in silence. We're there to engage in conversation.
That's the point of the fiscal multiplier figure: according to their estimates it improves the economy by a multiple of 2.6x the cost of the money transferred.

-

Seems like reverse "trickle down" in another respect too: the poorest recipients got better off but the gap between rich and poor still widened, presumably because the poor spent much of their increased budget buying things from the rich.
Having the similar logic, most CEO/CTOs have 0 coding time, would we say they're not productive? Nope

Having some metrics is good, but coding time is definitely a wrong one
Gren: Documentation as a First-Class Citizen
What a strange critique point. Do you have to pay in gold for each dependency?
The whole thing started because the EPA reported that the software that controlled fuel injection on diesel engines was intentionally programmed to detect if the car was running in special lab conditions. It's on the first paragraph of the wikipedia page[0].

[0]: https://en.wikipedia.org/wiki/Volkswagen_emissions_scandal
It's not portable then. If I have a Dock, then it's a desktop. When I move to a meeting room I loose all my ports.
> There is an alternative to returning error codes or throwing exceptions: Put the errors on some context handle - e.g. set an error flag.

Ah, the OpenGL way. I don't think there are many fans of that, except for perhaps low-level/perf-critical code.
I don't type for a living, I think for a living, and then type the results. If that is 52 minutes a day, so be it. That isn't a valid measurement of what I did that day.
I guess it depends how much distraction you used to get. Personally there were times when people from multiple teams were queuing at my desk to speak with me. Same happens during remote but at least I can choose when to respond and prioritise them accordingly. Ironically I forgot this issue existed at the office until I went back for one day and it started happening again (at a lesser extend since less people were in). On that day I decided that going to the office at least for my current position is not viable. Thankfully the company is still happy allowing remote work.
Feedback about Nixpacks – an alternative to Buildpacks
Maybe because it's harder to test the interactive features in a website. Sure, Selenium and Playwright exist, but they're not perfect solutions. There are a lot of moving parts to a typical website, and also maintaining these tests is a nightmare.
For Google a customer is a data point in their machine learning set (hopefully weighted by revenue). The decisions are made by a ML model. If you treat your relationship with Google as such from the beginning, you can extract some value if you use Google for near zero value use cases - spam/marketing emails, disposable non-real time computations, Adwords/AdSense on spammy sites.

Not sure if having an Android phone is safe enough for critical use, because it's entirely tied to a Google account.
But they’re more likely to be impacted.
I think there are some self-checkout solutions where you scan the barcode while taking the product off the shelf instead of at the end. The price should, of course, not change between picking up and payment.

Basically, like online shopping works.
I spend almost half my time reviewing code or pairing with more junior members of my team while they are driving with the IDE open, and I expect other more senior members of my team to do the same.

I don't consider that less important work, but it does change the ratio for myself and other more senior members of my team to more like 1:6
> If your dependency set is massive, you should probably have an extensive feature set.

Assuming that having a huge feature set is a desirable quality. Sometimes minimalism is a useful goal in itself - languages with few features usually make those features composable, leading to a combinatorial explosion of the ways those features can be used.

That being said, a small independent compiler/interpreter for PicoLisp would still be nice, though.
I find that a bit weird tbh. I mean, if we look at human tribes throughout the world/history, and even what is the most common nowadays in african tribes which maintain their dressing habits, they usually cover their genitals. It indicates to me it is human nature to do that. It seems to me, in some countries for several reasons, they are going against the grain, purely out of culture.

But there's something weird about it. Just like when you look at previous periods in time and now they look weird, often just reactions to previous epochs or other cultures (like the neoclacissim came as an opposition to rococo and baroque).

This feels like it. It doesn't feel natural. It feels like it is purely out of a contrarian way of thinking, about how forward thinking they are, "look how superior we are that we are completely void of instinct to cover ourselves". and perhaps somewhat of a sexual counter balance to the strictness of the rest of their culture. I'm not sure i'm explaining this in the best way. I think there is a natural middle ground, the one that we have seen throughout hunter gathere human history, and Nordic countries are just being culturally weird by going to one extreme.
I don’t think the other specs are necessarily backwards compatible. The NICs on each end negotiate the fastest commonly supported spec.

I’ve had 10G cards that would only negotiate down to 1G or only do 10G. But those were over Twinax. I’ve never use 10G on twisted pair.

Back in my day we were excited about 100Base-T and called it Fast Ethernet :).

Oooh! Now do 10Base2!
My input probably isn’t as valuable except as a data point, but the company I work for (around 100 employees) moved all employees over to a 32 hour/4 day work week without a change in salary. No negotiation involved technically, though there were a few employees who have been talking about 4-day work weeks for a long time.

They made this change with a 6-month trial period where we would determine if we would keep it at a later time based on some sort of productivity measurements. Everyone, including the CEO, seemed to agree that trying to measure productivity would yield few meaningful metrics. The consensus at the end was that productivity was either the same or a little less, but we ended up keeping it anyway.
Most mature languages have a logging system which allows the internal logging of a library or module to be silenced, redirected or almost any other action. I think there is a lot of value in libraries doing appropriate logging which can't easily be replicated in application code.

An example which comes to mind because I happened to be looking at it is the python Requests library where they log inform about when new connections are created / destroyed which is very useful when debugging keep-alive.
10G no, but all 1000BASE-T NICs require autonegotiation for 10/100/1000 to be compliant.
Coding isn't the only thing that works like that... clutch replacement (in a car) is just pulling the old one off the shaft and putting a new one on.... literally 1 minute of work, even less. Of course dissassembling half the car to get there (with some cars) is not included in this time measure.
I found it meaninful because it made me feel better about my own ratio of "working time":"coding time". I'd always read comments of people who advised spending time understanding a problem, but I haven't seen it presented as a simple %.
Generally you shouldn’t be logging errors at the point where you are (re-)throwing them. Otherwise you will likely end up logging the same error twice, or even worse, logging an error that is actually safely handled by code higher up the stack.
What is a developer? At some places developers are not expected to do much more than coding. At other places you will spend most of your time thinking about architecture, performance, error budgets, analyzing SLIs etc.

In my experience places with a devops culture will actively encourage developers to do stuff beyond coding. Places with a classic corporate culture enforce a more limited scope.
Also not sure about the seniority of the users too. Junior developers always tend to take longer time to solve a problem than the senior. Does that mean they're better?
It would be nice if Google actually told their customers that this is an option. As a result of your post, I realise that I quality for invoiced billing and have just applied for it. Thanks!

If I had an "established relationship with a sales / account team" then yeah, perhaps I would have been informed. Unfortunately my experience is that unless you're spending above some relatively high threshold (>$10k/mo? >$100k/mo? >$1m/mo?) then Google don't prioritise your business.
The datasheets for various simpler IC's often have extensive example applications with discussion of the principles. Texas Instruments' site is a goldmine.
Yeah, and a power law type distribution would be a straight line on a log-log plot, which this is not.
I don't think it's a strange critique point - dependencies are a necessary evil, but still an evil. Minimizing dependencies is always a good thing, and I can't think of a scenario where maximizing dependencies would be desirable, given the same amount of features.
> wait until the car is basically stopped

you mean like an email literally saying they acknowledge the situation and won't suspend your account?
One famous camel, likely a myth created during WW2: https://en.wikipedia.org/wiki/Kuznechik_(camel)
> The Soviet Union (and its colonies like East Germany) never came anywhere close to providing anywhere near the quality of life that the West provided

Kennedy administration thought otherwise. Their internal memos say that they saw USSR industrializing too rapidly and raising life standards of its people and this being dangerous in that other countries could pick up the same model, resulting in a 'domino effect'.

Which is the origin of the 'domino theory' and the Vietnam war and all the wars that followed it. Along with the arms and space race plan that Kennedy administration started to starve the USSR out of GDP in 1960s.

The capitalist system in the us NEVER provided everything that the Soviet system provided to its citizens. At the peak of American prosperity, there were blacks and minorities from the 'undesirable' groups suffering poverty, discrimination and actual apartheid. Whereas every Soviet citizen was entitled to every single creature comfort that was available in 1960s. But even today, a white collar couple in well paid white collar jobs, have to work for 40 years straight to get and keep all the comforts and benefits that socialist countries' citizens had been entitled to from birth. From housing to cars to guaranteed employment to paid vacations, maternity leave, reasonable retirement to entertainment. Today even retirement is a thing of the past in the US as people see that the workaround that has been the 401ks may be shaky.

http://graphics.latimes.com/retirement-nomads/

The 'success' of the system in the West was mainly built on propaganda: Soviet intelligence, propaganda ministries were never able to convince their people that behind the gilded and luxurious lifestyles from 5th avenue and manhattan that were being portrayed in the American movies, you encountered people sleeping in cardboard boxes if you just go two streets up the block. Even today, many Russians still don't believe that there are homeless in the US even as ~30 million people are calculated to be effectively homeless, ~3 million chronically homeless.

And its not coincidence. Its by design.

https://www.theatlantic.com/entertainment/archive/2016/07/op...
That lecturer was spectacularly good at teaching, and stood out from the rest of the pack so much that it was almost hilarious.

He used a digital projector in an era where that was still rare in even computer science courses so that he could demonstrate the basics of the edit-build-debug cycle. He'd deliberately leave small errors in the code to "fix" and he'd get the class involved with suggestions on where to look and what to try.

All of his projects were competitive, because it got the students much more engaged if they were racing each other. I believe the year after mine had to play a monopoly-style game where trucks were going around a "game board" and could buy and sell stuff for profit, could run out of fuel, borrow money, etc...

Meanwhile all the other lecturers would drone on and scribble unreadable gibberish on a blackboard. We had one lecturer give us a final exam where half the marks depended on converting 7 lines of C to assembly, except that 7 lines had 5 errors in it. Two of the lines were just the braces, which means effectively every line was faulty.
Error states are the worst of all worlds, and an excellent way of hiding bugs in rarely exercised code paths. They simply don't work, at all, in any kind of concurrent application, even a single-threaded one. That way lies "Error: Operation completed successfully" hell.

Please don't take this advice.
In the eyes of a PM, it is a useful metric. Because they think more code = more work. And in a way they're right, every solution will involve some amount of code (unless it's some menial task like changing a config file). So perhaps in their ideal world, devs spend less time thinking and more time coding (suboptimal) solutions to ship stuff faster.
I think HN would say 2 is wrong here—people often argue that piracy actually helps sales as it promotes the media. if that is accepted, then the court would be correct in asserting 1.
An archeaological dive through a software copyright concern
Stable Diffusion source code released (Open version of DALL·E)
Tracking and locking things within ones own system.
Yup, it's also basically a requirement for "asynchronous" APIs. Or the other way around, returning immediate error codes requires synchronization, and therefore increases coupling.

I don't care how many fans there are - when I can reduce error checking clutter by a factor of 5, and do error handling where/when it best fits, I know it was the right approach.
Is the socially conservative institutions-distrusting party doing without institutions? Or they aim to replace everything (including democracy) with their own institutions?
I use two levels. I log the closer to the error the better, with severity levels to filter non-error exceptions, only what I want to know if I get an incident report.

Then I free resources and let the exception reach user action level, where an informative, actionable error is shown to the user.
Yeah but answers like “thats what landed in my inbox” dont paint the whole picture do they now?
Many thanks to all
Can e-bikes transform our cities?
Fair point.. and the response is also right on. I'd edit my original comment to say "...creating full interactive scenes of geometry and textures..." if I could :)