skysight-inc/HackerNews huggingface dataset:
Always have a contract, even for smaller bits of work. That’s the foundation of a good business relationship.

If they have the money to pay, but are ignoring you then escalate from your contact at the company to someone higher in the chain. If that doesn’t work and it’s a relatively small amount of money then you can try to enforce the contact.

I’m in the UK and there’s a small claims court for specifically this. I’ve not gone through it myself but from those that have it’s simple enough to do yourself without paying a lawyer, but it’s time consuming. Im not sure where you are but look into if there’s in in your jurisdiction.

If the client likely doesn’t have the money to pay, then it’s likely a waste of time to pursue it. I had this happen recently when a client went under and ended up just writing it off as a loss. Luckily it was only my time that was wasted so not the end of the world.
How's the employer disposable? An insignificant portion of people can find a job in their field whenever they want.
> Curl checks the https certificate.

Which is not the same thing as a signature on the package, is it?

> Distro maintainers in general do not audit the code they package.

First, it depends on the distro. Second, they certainly do at least some kind of due diligence before packaging a new project. So there is some amount of selection (which you don't find in npm, cargo or pypi).
some of yall really need to get your sarcasm meter tuned up
It's vanishingly rare for an employer to be more reliant on an employee than the employee is on their employer.
Ah thanks.

That's chunks of a single layer though, not multiple layers right?
The obvious one is that it is userland-only, you don't get to play around with custom kernels being emulated on the hardware layer.
"that can’t bother testing it on like 2 browsers"

Current browser market share: Chrome 64%, Safari 20%, Edge 5.3%, Samsung Internet 3.5%, Firefox: 2.2%

https://www.similarweb.com/browsers/

It is hard justifying extra effort for those 2.2% marketshare, unless you count in idealism. And most companies are there for profit.
Ah, good to know. Thanks.
The article was clearly written by an enthusiast, but is a bit muddled. I see nothing in what he has written that supports the idea that Color Wheels are wrong.

Color wheels are, in essence, highly abstracted slices across the equator of a color space. Only two color wheels are commonly used: the RGB and the RYB (aka the artists color wheel). Color from pigments and color from light are two wildly different things, but easy to confuse. For its absence of green as a primary, CMYK can be understood as a version of RYB. Black is used not just because it is cheap but also to add opacity to the inks (printing inks are more like dyes... very thin and transparent).

The color opposites the author describes are red/cyan in RGB and red/green in RYB.

One property of these opposites is that they mix to neutral. For this, the RBG pair works best. The other property is that they are perceptually antagonistic, for which the RYB pair works best.

Interestingly, the perceptually antagonistic pair set (red/green, yellow/purple, blue/orange) were spoken about well before Newton placed these colors in a circle. Leonardo Da Vinco refers to them as 'retto contrario', literally exactly opposite.

The author asks 'why a wheel'? which is a good question, and the answer he gives is reasonable. But... Newton was the first to employ this device, and he did so almost certainly because the harmony structure of the musical scale was commonly visualized as a wheel, and Newton was keen to draw an analogy between music and color and harmony and the music of the spheres and god etc etc. He may have been the first physicist, but he was also an alchemist.

Color is a frustrating beast... so many different ways to understand the same thing: perception, physics, aesthetics, chemistry etc. Truly the seven blind men and the elephant.
Also most of the work is done by the CIA and NSA.
In my early career, I used to believe in doing whatever it took to stay with a company, becoming emotionally invested in every line of code and system I developed. However, after a few negative experiences with bosses who didn't treat me well, I came to realize a few things:

- My code is disposable, and I should not become overly attached to it

- Loyalty should be mutual and based on a healthy relationship where both parties are willing to invest
So, GitHub is preventing me from creating an account with “@simplelogin.com” domain to supposedly protect themselves from spam/abuse/“something something security” and forces me through captchas and when I finally create an account somehow they close my account without a reason but… apparently it doesn’t work!

Why make my life difficult then?

I tried to create an account to sync my vscode settings. After about half an hour trying to create an account without some not “big tech” email provider I finally succeed, but they delete my account the next day for no good reason.

Now I just manually set settings on my different computers and manually copy over changes when I need. Microsoft can take a hike. I don’t need your sync. I’ll find a way around.
I have a feeling you havent worked long because in the last 20 years of my experience I cant remember of one example where "but many employees don't hesitate to quit when the company needs them the most." was correct. It was always employees being let go suddenly and on a whim.
Ok, so why are you still employed.
Employees are more likely to quit than get made redundant. Therefore it would seem that employers are more disposable than employees. You can't quit a job for another job with a higher salary and then moan about being made redundant.
Generally I think you hope for the best and plan for the worst. If you're a good employee then employers won't want to lose you. If you're not then what do you expect? You wouldn't stay with a shitty job.
Sony had plenty of awful stuff at different times for audio CDs, despite being a co-developer of this wildly-successful and long-lasting format.

I think you're referring to ActiveX, yes. It's the only thing I can think of where "web" stuff and "hardware" stuff commingled back then in a semi-transparent way.

And famously, as you surely know yourself, Sony once published some rootkitted audio CDs: https://en.wikipedia.org/wiki/List_of_compact_discs_sold_wit...

Anyway, I'll just assume that you aren't the rootkit guy -- or even if you are, that your heart is in the right place.

---

And yes, CD+G is is important. As are the mixed-mode releases with video. All things CD audio are important if we are to talk about an ideal archival (and playback!) format for audio CDs, and archiving an audio CD is not always quite as simple as ripping a folder of FLACs -- there's a ton of diversity here that FLAC (and cue) can't accurately embody.

We're fortunate that we still have so many CDs right now, and that they're still being sold today. This will change. (It must change. It can't not change.)

The good folks working on the Domesday Duplicator have a relatively uphill battle for the often-older (and often rotting) LaserDisc media that they're working on tools to properly preserve.

It would be good to get ahead of the curve and get something with a practical workflow working sooner instead of later.
Compile-time safety is not achieved which is the point.
I missed the "startup". My bad :)
Have you done an abx test on what you would consider bad mp3 from a "regular" store and the flac version?
I think this guy is the kind of person that will fire an employee out of spite, even if it will damage the business.

‘the peasants should know their place’

I am not clear on this whole ‘employees want too much’ issue - we are still talking about companies like FANG that have giant profits and insane capitalisation? Why is having employees claim larger share of the pie a bad thing?

The money they pay in salaries actually gets taxes and enters the real economy. The money they stash in tax heavens does not
Indeed, you are free to push multiple layers in parallel. But when you have a 1 GiB layer full of AI/ML stuff you can feel the pain!

(I just updated my original comment to make clear I'm talking about single-layer pushes here)
Of course, it also depends on the local laws. In some countries, there are stronger employee protection laws.

My employer wanted to do layoffs. They had to come up with an offer that's so good that some employees accepted it (everyone who wanted to remain in the company did).
> An argument can be made that laying off however many employees also helps to preserve the ongoing livelihood of the employees who remain.

That argument falls flat on its face as soon as you look at the balance sheet of these companies. They are exceeding expectations and still laying people off.
Do you get free soy latte, too?
Too bad this misses a "/s". I guess that's why it gets downvoted :-/.
I saw this just before you edited. Don't worry I won't reveal anything. But I wanted to say that - although I hope you're wrong about what you wrote - you might also be right, and if so it is awful. Some people cannot separate one thing from another.
Oh, but my employer is different and a union would only make business more complicated and less likely to give me raises and promotions! I’m a rising star, you know.

- A literal supermajority of software developers
I wonder if it was done with intentional irony.
It is far easier to switch an employee than employer, as decision is made assymetrically - the decision maker, the manager of your manager, for example, has zero emotional investment in you, compared to you and your being accustomed to your place, social relationships etc.

EDIT: It is also true that too frequent switching jobs will have negative consequences for your employability; and high attrition, even if it becomes a public fact, would have little consequences for desirability of the job.
It depends on the artist and their contracts of course, but for normal (non-indie) artists with labels, this is well-known and you can read all about it all over the internet.

Generally, most bands make most of their money from touring, both from ticket sales and especially from merchandise (T-shirts etc.). They don't normally make much from CDs, and very little from streaming, that mostly goes to the label.

So if you really want to support an artist, go to their concert and buy a t-shirt. If a concert isn't convenient, you can probably buy a t-shirt from their website. This will do a lot more for their personal finances than worrying about copyrights.

Personally, though, I do like to buy CDs of artists I follow, and I normally rip my music in FLAC from those. A lot of the CDs these days are quite nice, with cool books sometimes.
And if you work at a place as an employee that has made a situation where you ARN'T disposable, you should either try and change that or leave.

If there's a single point of failure like that, the company is being mismanaged. NOBODY leaving, getting sick, taking a holiday or even dying, should leave the rest of the company at risk.

Companies should most certainly value employees and treat us with respect, but they should also be setup to allow for employees not being around forever.
https://www.youtube.com/watch?v=3QbOssRq0Gs

[Chorus: Chilli & T-Boz]
No, I don't want no scrub
A scrub is a guy that can't get no love from me
Hangin' out the passenger side of his best friend's ride
Trying to holla at me
I don't want no scrub
A scrub is a guy that can't get no love from me
Hangin' out the passenger side of his best friend's ride
Trying to holla at me
I was going to say you can rotate secrets in secrets manager without redeploying all your services. But this caches the secrets so you'll still get stale results for up to 5 minutes by default. Not sure what the point is then.
"So subsecond I would say is a requirement." you do not make any specific point why you came to that conclusion.

You can easily entertain users to show them that the system is doing something in the background without loosing them and if they are collegues who actually need to search, you don't even need to keep them as they have to use your setup.
Half a million
“Shareholder value” reigns supreme in this late-stage capitalistic world. The executive class lives extraordinarily well off the fruits of the enterprise while the rest lives off the scraps.
I was in such a company, do not pass go, do not collect $200, just go.
+1. Here is another alternative. I find this generator more lightweight and better syntax (generated benchmarks and tests are also nice):

https://github.com/nikolaydubina/go-enum-encoding
I'm not sure if this is a good idea, just like pretending a network request is a function call, it hides a lot of elements that shouldn't be ignored. I still prefer to clearly explicit embedding, LLM generation, etc.
> The low end models are so cheap that Apple is definitely subsidizing

Depends what do you mean by "subsidizing".. Obviously their margins on entry level models are lower but I would still bet than they are much higher if not several times higher than the industry standard. They are certainly not selling them at or below cost, they can probably upgrade the base config to 16GB and still make more per unit sold than Dell/HP/etc.

Even MS get rid of 8GB with the new Surface: 13.8, Snapdragon, 16GB RAM, 256GB SSD is $1000, the equivalent 13.6 M3 Air is $1,299 (8GB is $1100). So if Apple is subsidizing their lower-end Macs what on earth is MS doing? Surface is already a premium(ish) tier device and I'd assume their are paying more to Qualcomm than it costs Apple to make an M3 chip.

> the base model would have to be much more expensive

Why? I don't really get this logic. They are pricing their base models at what the market will bear, it wouldn't make sense to sell them at a discount just because they have more expensive models, they'd hike their prices even more if they could.

What they are making from memory/storage upgrades is basically free money on top of already presumably very reasonable margins (by industry standards).
My working career spans ~25 years. Less than 5 of those years have I been a permanent employee.

Most people view this sort of employment pattern as being risky. It certainly has it's ups and downs but it does also mean you are never tied to an employer or really that vulnerable to layoffs or similar. I have had contracts cut short because of organisational crisis but moving on is usually trivial.

People make choices and trade-offs when they choose their employer/how they are employed.

I don't understand why people think a large or even middling organisation is going to consider individual employees over other likely more pressing factors like short and long term survival. I do understand why it would be painful and stressful.
The OCI Distribution Spec is not great, it does not read like a specification that was carefully designed.

> According to the specification, a layer push must happen sequentially: even if you upload the layer in chunks, each chunk needs to finish uploading before you can move on to the next one.

As far as I've tested with DockerHub and GHCR, chunked upload is broken anyways, and clients upload each blob/layer as a whole. The spec also promotes `Content-Range` value formats that do not match the RFC7233 format.

(That said, there's parallelism on the level of blobs, just not per blob)

Another gripe of mine is that they missed the opportunity to standardize pagination of listing tags, because they accidentally deleted some text from the standard [1]. Now different registries roll their own.

[1] https://github.com/opencontainers/distribution-spec/issues/4...
It's not news and I think it's fairly widely accepted, but there are plenty of corollaries that people still reject.

I had a coworker who was actively hostile to the practice of writing documentation, for instance. He wasn't up front about it but he was plainly doing it to reduce his disposability. I think it probably worked because they kept him around longer than they clearly wanted to in spite of his very prickly personality.

As a strategy I thought it actually made a decent amount of sense given his circumstances - lots of debt/outgoings, he couldn't hop jobs easily and the company treated employees as extra disposable.

As the developer who came after him I was perplexed at the cries online people would make that "this practice only hurts the developer who comes after you" or "if the company does well you'll do well" (which I think is bullshit).

It definitely made me a LOT slower, but I still got paid the same.
Installing/maintaining mysql or the others is a pain in the ass relative to sqlite (essentially no cost at all). For a personal media library, all write operations are trivially serializable. Sqlite DBs are the easiest to copy to new machines when you upgrade hardware.
Honestly it's just a nomenclature or convention to define hierarchies.
I've had certain projects where it was useful to get teams aligned on how to view a particular project. That being said, sometimes it's also heralded as something super life changing, which it isn't.
> easy business to get into

Good luck getting rental rights.

The very reason modern streaming sucks so much is that every other production company wants to be a streaming distributor; pulling rights from other streaming services.

Just holding a DVD does not give you the rights to lease it out. At least, that's if you believe the legal spiel on the disc.
It is the exact line the US is taking on Russia. “Ukraine need help now or soon Russia will be in SOME_NATO_COUNTRY” and “Russia is loosing hard” at the same time, often in the same “according to government officials…” speak.
Workflow from Contract Creation to Compliance – RazorSign
Learn the concept of contract workflow, including its steps, and explore how RazorSign Contract Lifecycle Management (CLM) software can enhance the efficiency of managing contracts.
The various phases of the Contract Lifecycle Management (CLM) workflow, exploring how each stage contributes to the seamless management of contracts and the role of technology, such as RazorSign, in simplifying and optimizing these processes.
Yes, if the server uses kTLS, it'll be easy for such a probe to get the plaintext, because the syscalls themselves will contain the plaintext. It won't have to do TLS library-specific shenanigans to hook userspace functions or extract the key material like this submission does.
fruit basket.
> They might be subsidising

Any (even the slimmest) evidence that this might be the case? Because it seems like an extremely far fetched claim... And year RAM/Storage upgrades seem like a clear example of market segmentation.
Doesn't that make it easier for a California company to just ignore you?
OpenDiLoCo, globally distributed low-communication AI model training
First Official NYC Trash Bins
The problem isn't so much the lack of enums, it's more that there is no way to do exhaustive pattern matching at compile time. I have seen production systems go down because someone added a variant to an 'enum' but failed to handle that new variant everywhere.
I don't want to be "equalized". I'm happy to negotiate my own terms. In my experience the union leaders negotiate better terms for themselves than for the people they represent. The company prefers to have a good "shepherd" for the flock - the union leader.

If you look at where the good salaries are, you will not find them in France, Germany, Italy where the unions are strong, but the Bay Area, London, New York where unions are not really a thing.
Work for yourself, not for your employer. Your employer will fire you the second it is profitable for them, that's how it is.

It doesn't mean that you have to hate your job. Just stop and reflect from time to time, and make sure you are being compensated for what you do. If not, you need to change something (ask for a raise, look for another job, work less, ...).

As developers, IMHO you should always push for open sourcing as much as you can, ideally with a copyleft license and no CLA. Because it is beneficial for you personally: it means that you can reuse your code after you leave, and if you manage to make it copyleft and accept external contributions, it will force your employer to keep distributing the sources after you leave.

I really don't get why developers sometimes go out of their way to help their employer keep their code proprietary, it should be the other way round.
In my experience, artists have a very fuzzy understanding of color, even those who use it wonderfully. At art school we were taught 'color theory', almost all of which was hand-wavey fluff.

> instead of thinking in primary colours [Painters] will be much more familiar with the mixing of the pigments they use. (Cadmium red, cobalt blue, burnt sienna, etc)

Absolutely agree. A red is never just the abstract red, it is a cadmium red, alizarin crimson, rose madder etc.
Corrigendum: Consulting Rochkind's 2nd edition of AUP book it says; the 1st edition included about 70 system calls while the 2nd edition includes about 300 gleaned from SUS (https://en.wikipedia.org/wiki/Single_UNIX_Specification).
But at that point your problem isn't needing a better lifeboat, the problem is why it's sinking. At this point solving the problem of why it's sinking is the problem you've got, solving it before you had that problem seems silly.
> it's the company's responsibility to make sure the employee and their family are living a good life

Ultimately that's why the person is going to work, no?
IKEA regularly shuffles around it's layout. They won't let you learn shortcuts and exploit experience.

I learnt this the hard way several times in my local IKEA, but I also read an article about how this is absolutely strategic in their thinking. Unfortunately I couldn't find it to back me up.
No it just means that they need to appear in your courts via a local law firm if they want to contest.

This is good advice.
It's not why do you need it, it's that there's 2000 people that know how to do it with docker for every person that knows how to do it with cgroups. And your question is probably just signaling you're in the second group (I'm in the first).
AIs are still not able to understand negations.

Try "ramen without egg" or "ramen with no egg" and it will show ramen WITH egg.

Or "man without striped shirt" will give "man WITH striped shirt"
You probably don't need full text search, but only exact match search and very efficient time-based retrieval of contiguous log fragments. As an engineer spending quite a lot of time debugging and reading logs, our Opensearch has been almost useless for me (and a nightmare for our ops folks), since it can miss searches on terms like filenames and OSD UX is slow and generally unpleasant. I'd rather have a 100MB of text logs downloaded locally.

Please enlighten me, what are use cases for real full-text search (with fuzzy matching, linguistic normalization etc.) in logs and similar machine-generated transactional data? I understand its use for dealing with human-written texts, but these are rarely in TB range, unless you are indexing the Web or logs of some large-scale communication platform.
Which is not surprising, since porn is a multi billion dollar market. So there are hobby enthusiasts going to optimize their own kinks - but also professional players who want a share of the cake.
Spain is a bad example, but lots of countries have bilateral legal arrangements for this sort of thing.
Can confirm. I myself am older and, admittedly, came into the job market as a very naive individual. But over the years I have watched the younger cohort and I am actually kinda impressed with the realistic ronin-like attitude. It is a lot more transactional for a reason; companies themselves have mostly destroyed it.

If anything, it is a perverse expression of US 'fuck you, got mine' system.