skysight-inc/HackerNews huggingface dataset:
To clarify, I don't think HTML should be expected to be responsible for button styling – that is a CSS concern. But I was really more responding to the "why can't I do this with a HTML library" comment, which you can but with a JS library instead. And while it's true HTML has some dynamic elements the assertion that you should be able to build advanced dynamic behaviour like this in HTML alone I think misunderstands the purpose of HTML. JS was built for more advanced dynamic behaviour, and you can absolutely do what the parent commenter is asking for with a JS library.

To defend my suggestion of a "singleSubmit" attribute – I think the form element itself which already has the ability to do some basic dynamic stuff like submit a form in various ways could reasonably include the basic requirement of not allowing said form to be submitted twice. Personally this isn't something I think is a huge issue because most of the time when we'd want to do this we're looking to build fancy dynamic form behaviour anyway and in those cases JS is going to be what you need to use for that. But there are some simple webpages out there which don't care about any of that fancy stuff and literally just want a form on a page which POSTs data to another page, and in those cases it would be nice to have the "singleSubmit" attribute I suggested.
Devices that rely on cloud infrastructure should be required to carry an expiration date right on the box. "This item guaranteed to receive support until XX/XX/XX"
> Sometimes they are literally an OCR of the print book! You can tell because of the symbol substitutions.

Not really. TEX for example does a lot of weird character substitution behind the scenes to mangle the layout.
> I prefer mutability

... Examples on how to avoid the bug ...

Notable is that you claim here is an opinion not an argument.

That immutability is not needed is also not an argument against it.

The point here is that working with immutables relieves you from some cognitive stress and repetitive work such as writing accessors and making fields private.
Another recommendation in the same vein is How To Measure Anything by Douglas Hubbard. And Superforecasting by Tetlock. Estimation/forecasting (same thing different emphasis) is a problem we know quite a lot about, and we know how to train people to issue calibrated estimations.

The first step to learning anything is figuring out how to get feedback on your performance. For estimation, probabilistic estimations are the way: https://two-wrongs.com/verifiable-software-development-estim...
> The only skill you need to get promoted is to laugh at the jokes of your boss and schedule meetings to demo your n-th rewrite of the same thing.

don't blame the player, blame the game.
One of the biggest reasons “the EU” can’t seem to home grow a tech industry is fragmentation - each member state has its own bizarre tax rules, and it’s extremely tedious/difficult, even today, to do cross border employment.

A company based in Ireland for example, has a really hard time employing someone in Germany, without spinning up a “local branch” in Germany, and thus having to comply with German tax rules as well.

Rules around contractors vary wildly and don’t simplify matters much.

The “solution” is to accept the overheads of a company like Remote or similar who act as an employer of record, but that’s a bodge.

No member state has any real incentive to simplify cross border employment/business rules, so it drags everyone down.

It gets even worse for startups when rules around equity, etc, vary wildly country to country - some countries have extremely hostile tax rules around equity that may never be realized.
If you intentionally remove functionality, why would any functionality be safe from that?
x1000 this. I find I have similar reasoning that I apply to awk. I _know_ some people get massive benefits out of using it, I just dont need it often enough to actually pick it up... GPT to the rescue I suppose
Does thread per core necessarily imply message passing? I don't see why the two need to be related.
dupe: https://news.ycombinator.com/item?id=38188614
This year 'virtually certain' to be warmest in 125,000 years, EU scientists say
Should I not be able to send money to the same person twice in a row? Unless you add a single-use token to the form, your server doesn't know whether it was a misclick or a legitimate action. The client more or less knows.
> with each allocation limited to 1/4th of the available resources so not individual peak can choke the system.

This assumes that the scheduled workloads are created equal which isn't the case. The app owners do not have control over what else gets scheduled on the node which introduces uncontrollable variability in the performance of what should be identical replicas and environments. What helps here is .. limits. The requests-to-limits ratio allows application owners to reason about the variability risk they are willing to take in relation to the needs of the application (e.g. imagine a latency-sensitive workload on a critical path vs a BAU service vs a background job which just cares about throughput -- for each of these classes, the ratio would probably be very different). This way, you can still overcommit but not by a rule-of-thumb that is created centrally by the cluster ops team (e.g. aim for 1/4) but it's distributed across each workload owner (ie application ops) where this can be done a lot more accurately and with better results.
This is what the parent post is also talking about.
You make some very good points, and I agree with your conclusion, viz it's a trade-off.

I'm still wondering if the OP (@duped) meant the same thing as you did, or if he had another use-case in mind when he said "calling conventions".

FWIW ...

> But the Ruby code needs the arity of the code that's being called to be passed along. Putting it in a register that's not used for arguments in the standard calling convention means that when calling out to e.g. glibc the C code just won't be able to access those values.

In general, when a call returns you can't trust the register contents for those registers that are unused in the calling convention, because the callee might clobber it (for example by calling back into your language before returning).

What I did[1] when doing the ffi to the external C functions was emit a `setjmp()`, call the function, and emit `longjmp()` when the callee returned.

That allowed recursive calls no matter how many times that FFI boundary is crossed in a single function call: The language calls into C API, which calls something that invokes a callback in the language, which makes another call to a C function, etc.

[1] IOW, this is not the usual way, as far as I know. All a bit hackier than when I (for a different toy language) used `libffi` when emitting the code to call external C functions, which (IIRC) makes certain gaurantees about some of the registers.
Sorry, my question is if Matter is baked in or can be stripped. Not sure if they can remotely kill the Thread radio or not.
Just a couple of advices. Feel free to ignore. It won't harm anyways.

- linkedin profile looks weak. Elaborate on what were the duties in form of showing up your professional achievements. Like how you improved the product with your work. How you increased company revenue. Did this -> it lead to that. This approach shows your real impact (at least a sign of it). "reduced infra cost for 20%", "latency decreased which lead to more registrations", "hired and structured 2 team", etc..

- use recruiters. 99% of time their help will be useless but because there are a lot of them this 1% will cover the rest.

- don't spend your time on no-name-another-job-list-platform. it won't work. approach company recruiters directly, apply via linkein or connect with recruiters there.

- "I can do everything for 60k" might sound like a red flag. Avoid it during the conversation.

- Interview passing is a skill. You need a time and a volume of interviews to train it. Doable.

- don't listen to "oh yeah that's a terrible market I can't get a job as well we gonna die poor" comments. you don't know who is behind the comment. like I don't know who are you btw :)

Market is not that bad. It's totally ok. Approach it as a project. Code, code, code, read, watch related videos on youtube. Acquire some clarity that you know your shit.

I wish you all the luck, you will make it!
- if your government does not do what your community wants then you don't live in a functioning democracy.

Democracy is rule of majority and make inequalities by definition. Minorities needs to accept rules that they do not agree with. It's like monopoly except it is forbidden to do competition by law. Decentralisation of taxes or financial system could solve many issues that escalate recently.

- i'd like to see a specific explanation how a free market can take care of those issues.

I don't think free market solve issues. Decentralisation and gathering in local communities could. Less mandateds = less laws = less taxes = more personal responsibility which means more effective solving problems that really matter for you and your close one.

- to get these things taken care of, the community will have to enact rules or delegate someone to do it. how it makes that decision is is up to the community. it doesn't require a government that is not under the control of the community. nor does the existence of taxes imply the existence of such a government.

I agree with that.
Maybe. But if the accounting is accurate, this person refused valid, and urgent criticism. They refused all input, and eefused to care that there was an issue.

This would make a very poor team lead. Imagine this person taking the wrong path, then refusing to acknowledge so. Imagine them upset that "their" path was being constructively criticized.

This is how companies go bankrupt, how months or years of work result in garbage.
One of the key ways that single-payer government healthcare influences costs is precisely by refusing to offer treatments that are too expensive for the benefits compared to the next-best option. In particular, the NHS in the UK - which is often pointed to by US politicians as an example of how single-payer can save money - refuses to offer treatments that cost more than a relatively low amount per quality-adjusted life year saved, which is specifically illegal for US healthcare providers and insurance companies to take into account.
? MySQL, in this case, is simply a protocol. Planetscale and Vitess are not affiliated with Oracle at all. I don't understand your point.

Furthermore, we use Planetscale from an ORM. I don't think I have "read the MySQL docs" in years.
I want to visit this so bad.
That section of the article unfortunately conflates two types of not switching off.

* Late at night, quick check of my email or Slack and maybe even reply (either to get it out of the way or to show off how hard I'm working).

* While I'm in the shower, thinking about some interesting logical problem (can be something mundane like how to clearly express something in a report).

What is healthy and what isn't is subjective. But most would agree the first is not healthy, while some would say that the second is OK. Personally, I think it's fine (nice even) and certainly doesn't interfer with social or family life.

You (comment I'm replying to) have added a third which is quite different: "chronic workers" are those that are flat out working for extended hours. That's not really the same as not being able to switch off.
Fucking finally. The quality of macOS has been questionable for a while. Especially the new features, but there are also a ton of glitches that have been there for many versions and I experience daily.

It feels like Tim Cook has been selling off the reputation of reliability (their moat!) for a few years now.
I keep recommending “Compiling to Assembly”, by Vladimir Keleshev: https://keleshev.com/compiling-to-assembly-from-scratch/

The author chose TypeScript for the Compiler, which makes it somewhat more accessible to these days programmers.
I don't really recall because I don't think our database has needed much on top of stock MySQL. Maybe JSON columns? I don't really care. Just being candid as a user; it has not worried me, no.
without the player there will be no game. blame the player.
In the past as a JavaScript developer they are happy if you are smart enough to spell your own name or color within the lines without eating the crayons.

This year though things have been far more competitive. I wasn’t getting interviews at all until I focused on a combination of my development experience, my TS, and my certs. Since then I have had many interviews and several competing offers. In one case I given an offer to write test automation in Java with 0 years experience writing Java at this big rocket company, I do have experience writing test automation utilities though. I have since taken a work from job on API architecture for this massive data enterprise.
Kubernetes Case Study: OpenAI
> The only skill you need to get promoted is to laugh at the jokes of your boss and schedule meetings to demo your n-th rewrite of the same thing.

You can't choose your colleagues, but you can choose your company. Some of them have fair evaluation processes and try hard to avoid biases. Same thing for meetings, not all companies/teams have long meetings.
> & telling people who don’t agree that they aren’t welcome

Are you familiar with the Paradox of Tolerance (https://en.wikipedia.org/wiki/Paradox_of_tolerance)?

It is best understood as a social contract - in order for a group to function, people need to tolerate each other. People who don't obey that social contract are therefore not eligible for being in the group.
Well, being the middle man is kinda the manager job. The situation you describe happens when the manager does a poor job and is both submissive to the business requests and unable to comprehend technical issues.

Ideally having a competent person acting as the middle man for most daily operations is desirable though
"GDPR blocks American companies from operating in Europe."

Actually it does, because of extraterritoriality of US laws.
you kidding me. have you heard about 24/7 oncall?
Thanks. So, AES-CBC + HMAC would prevent this, but AES-CBC does not.

How do the following methods compare when using constant IV?

AES-CBC + HMAC (encrypt then MAC) vs AES-GCM-SIV vs AES-SIV
https://selectcommitteeontheccp.house.gov/sites/evo-subsites...

This is the letter and it's as stupid as you imagine.
Are we sure they wont just shoot MOST of it in Liverpool, and other scenes in Bristol?
I'd just like to comment on these points on a 30 year perspective...

Point 4 - incompetent people. They are great. When they fuck up, which they do often, you can save the day by simply being average. Just make sure people know that you saved it.

Point 5 - meetings are great if remote. You can sit there muted on a zoom call for hours tweaking with your bike or playing games on your other computer.

Point 6 - estimates are always wrong so don't put too much effort into it. What people value is how long you spend making up lies so spend some time on it!

Point 8 - Uncertainty. Let other people handle that and hang themselves with it. That's what software architects are for. Be there to clean up the mess afterwards or at least complain about it.

Point 9 - Eventually you do become able to disconnect from your job. One day the fucks just run out. Embrace that early on and save yourself a lot of stress.

Point 10 - The only soft skill is politics. Any sufficiently large organisation employs many politicians. The best way to deal with politicians is analyse the factions and stay neutral. No one can drag you to their side then.

There is a missing point though: objective one is getting paid. Anything else is secondary. If they stopped paying you how much of a shit would you give about all the other concerns? There you go now you understand. Nothing matters so don't get too wrapped up in it or upset about it.
Another one on the shame list. You can use the public api, but only if you send your local data through our dogshit online channels, so we can sell it later
>> I genuinely think that meetings are the only way management can justify their existance and therefore commercial projects consider them as an "important part".
reply

Wait until you join management at some point in your career.
I agree with the author's statement, like probably a lot of people who already understand how e2ee works under the hood.

I'm not sure if writing code on GitHub to be run in a terminal is going to change policy makers' minds.
Ridiculous, and shameful.
Bad eIDAS: Europe ready to intercept, spy on your encrypted HTTPS connections
Lots do it's called help. But then they would all have to use the same spec, which we know would never happen.
Have you tried changing companies? That sounds like a very toxic environment.
Comments are for telling the reader why something is the way it is. The code doesn't do that.

It's also a lot more effort to dive into the code to understand what a method does (again, this typically includes background information related to things outside of the method itself) than to read an ideally well-formed sentence that precisely answers the main questions about the method's usage.
> You can run linux on Windows but still can't install a dual boot system with Linux first. IMO that says it all

Long time Kubuntu user dual-booting with GRUB, never experienced this.

I have UEFI enabled and both OS's on separate physical drives.
While many points are true (but IMO not all) I would not see all of them in a negative light. Especially for a new grad just starting in the field.

For example, yes, you will likely work with existing codebases, but in most other professions you will work within established constraints, not all of which are fun, etc.

On the flip side, a good knowledge of software engineering offers excellent money and opens a lot of doors. Want to live and work in Europe for a few years? Take 3 months (unpaid) off to surf and recharge? Negotiate remote options? A good software engineer is likely to manage those with some negotiation and planning. Not many other professions would allow that today. My 2c.
Couldn't agree more. Worked with a guy and he would respond on slack almost immediately-he was addicted to work and having the app on his personal phone. he had nothing else going on in his life.

Personally, if I shut my laptop there is no way to contact me for work related issues nor should there be.
“Basic error handling” is distressingly rarely present, and when present, regularly broken.

In general I do think it’s mildly irresponsible to not mention error handling at all and (taking what this article does) to show reenablement only via linear code flow that assumes success. But when it’s in an article about the problems of disabling submit buttons, then it’s even more perplexing.
A major difference between a long function and multiple short helper functions is that when you look at the local variables in scope in the long function you do not easily know which of them are used by which parts of the function. You see a variable used on lines 756-762 but the function continues to line 900 and perhaps it's used again further down?

Some languages have block scopes that can make this better; my position is against long functions in languages that lack block scopes or written by programmers that do not avail themselves of block scope.

I really struggle to see why anyone is not attracted to that form of abstraction: if local variable foo is computed in 10 lines using local variables bar, baz, and qux, and those 3 are not used for anything else, then clearly matters are improved in a 100-line function by replacing those 10 lines with

foo = computeFoo(bar, bax, qux)

Authors of long functions are not embracing appropriate modularity, but that seems inexplicable, since modularity is the basis of the software revolution.
The scary thing about that is that folks actually use them and think they are good.
Sure, then don't use any earbuds that contain batteries.

We're dealing with tiny batteries in the 100mWh range here, which is less than 1/100th of phones famous for their... combustibility. Ejection of hot gas requires there to be quite a bit of energy present during the failure so that a certain extreme temperature can be reached. Below that, you'll just get a warm earbud.

> hot gas and flames

flames are hot gas
i think the problem is it doesn't have easy to find documentation, if any at all, that introduces it as a formal language so everything is just a very hard guessing game of easily forgettable syntax.

You know, a list of reserved words, what their functions are, how the structure works, etc ... the kind you'll see if you pick up some "intro to <language X>" book from no-starch or o'reilly or the kind that GNU Awk/sed/dc have.
A lack of ability to police one's own levels of internet usage is something I've brushed up against in my own life. Someone with ADHD may be harmed by the constant availability of distracting content, but may not be able to set effective strategies for curbing one's usage of said content, or may find ways to get around those strategies in order to access or justify accessing the internet. A vicious cycle.
"unauthorized users". They are authorized if they are trying to control their own garage door.

The company I work for has a policy where we don't block third party clients, as long as they use a uniquely identifiable user agent and API key that we provide to them. That way we can easily monitor if they're calling endpoints excessively and make sure that our alarms don't go off when they did something wrong, but still offer power users flexibility. Power users are the users you can get good feedback from, and they spread the word more than a regular user would. If keeping them happy doesn't require active effort, it would be silly to start a cat-and-mouse game just to keep them busy and angry with you.
You have to go where people are.
> why isn’t being a customer also considered parody

I'm pretty sure you can claim that in a court. However, making an offline appointment with a hitman and then making them an offer and even making a first down payment for the service is probably difficult to explain away as parody.
I disagree with this statement in general. Institutions/nature (the game) cannot be held accountable. Persons can be. If we want to change the world, it starts with changing the behaviour of individuals, slowly changing the institution.
Here you go: https://edpb.europa.eu/news/news/2023/edpb-urgent-binding-de...
I prefer to have an e-waste law that says that if you stop maintaining the service, you have to open-source it :)
It's strange how Patrick, one of my favorite writers in the tech business, is stating a lot of his anedoctal experiences as fact.

I've been in banking longer than he was, I think (15 years in my case) and a lot of what he says isn't true for many institutions out there. The overall view is somewhat accurate - there are such issues in a Bank, usually stemming from how big they are, but details are not necessary what is being described.

Take the article with a grain of salt.
For even easier (and still reasonably robust) text-based music composition, look into ABC notation:

https://en.wikipedia.org/wiki/ABC_notation#Example
That's very far from "filling them up" and the practice is decades old.
>Point 5 - meetings are great if remote. You can sit there muted on a zoom call for hours tweaking with your bike or playing games on your other computer.

You dont have to tell people about it...
What notation rendering library are they using?
At some point in every declarative language’s life, so many features get bolted on to make it useful that it loses its declarative nature, at which point you might as well just use a more standard imperative language. In this case, just plain JS.

The same thing happened to HCL.
I will ask the obvious question: Why not make it yourself? You have a clear set of requirements and you are a developer.