HNHacker News
TopNewBestAskShowJobs

loup-vaillant

10,104 karma · joined July 1, 2009

http://www.loup-vaillant.fr

https://monocypher.org

https://elligator.org

submissionscomments
loup-vaillant··on Women outnumber men in South Korea's sports stadiums
> I clearly stated I am talking about Romania.

Sorry, I missed that part. I'm not sure where to find the official numbers there, but the sources I could find suggest the vacancy rates there are still easily less than half the unemployment rates.

https://www.statista.com/statistics/1391389/romania-job-vaca...

https://eures.europa.eu/living-and-working/labour-market-inf...

Supporting yet again that there are much fewer open jobs than unemployed people. Now I don't know how trustworthy the sources I just linked to are, but from what I've seen so far your current model of unemployment and vacancies seems to be wrong.

loup-vaillant··on Women outnumber men in South Korea's sports stadiums
I have some official numbers for France, and they directly contradict what you’re saying: https://www.insee.fr/fr/statistiques/4805248 https://dares.travail-emploi.gouv.fr/donnees/les-emplois-vac...

According to our own government, the number of unemployed people in France at the end of last year is estimated at 2.3 millions (7.5% of the active population). the number of open positions for private companies of more than 10 employees (excluding agriculture) is 331,700.

I don’t believe for a second that including agriculture and smaller companies would raise this number even close to 1M, let alone 2.3M. The total number is most likely well below 500K. So it looks like in France, there is there is at most 1 open position for every 4 unemployed people able to work. Likely less. Given these numbers, if all the unemployed French people filled every open position overnight, at least 75% of them would remain unemployed.

I really, really have a hard time believing your numbers now that I have checked the official numbers for my country. I suggest you check for yours.

loup-vaillant··on Women outnumber men in South Korea's sports stadiums
My question is how many?

How many unemployed? And how many opened positions? Your wording suggests that the number of opened positions exceeds half of the number of unemployed workers, but what’s your actual numeric estimation?

loup-vaillant··on Women outnumber men in South Korea's sports stadiums
Don’t miss the part where there is only 1 vacancy for 10 workers.

Lowering standards would not solve anything here, even if everyone accepted any job and relocate accordingly to fill every single vacancy, unemployment would hardly go down.

loup-vaillant··on Women outnumber men in South Korea's sports stadiums
We regularly get the labour shortage argument to push retirement age later and later. There's just one problem: if there's a labour shortage, where does the 10+% unemployment comes from? Can't be explained by unfulfilled positions either, we counted in France, there's one open position for 10 unemployed worker.

And bloody hell, if push comes to shove, we can give up on optional niceties and reallocate labour to the more important stuff.

loup-vaillant··on Women outnumber men in South Korea's sports stadiums
The downvote is surprising: e-sports is big in South Korea, so there's an obvious question: what's the female to male ratio in e-sport stadium? I personally wouldn't use the regular sports stadium as evidence of anything before I know more about South Korea.
loup-vaillant··on Nintendo is suing the creators of Switch emulator Yuzu
Ah, found it: https://en.wikipedia.org/wiki/DADVSI

TL;DR: it's more complicated than I thought. First, the law was introduced in 2006, so before it, circumventing DRM and publishing how to do it was not a crime. (Of course, publishing copyrighted works with no proper authorisation was already a crime, regardless of DRM.)

Then for a brief time, circumventing DRM was outlawed. But fear of foreign monopolies (most notably Microsoft) and free software lobbying eventually had those articles amended, effectively exempting research and free software from any sanction. The exact limits of the current law are still fuzzy, but it seems pretty clear that using VLC to make copy of a DVD I own is 100% legal in France.

loup-vaillant··on Nintendo is suing the creators of Switch emulator Yuzu
> […] but you don't have a right to circumvent copy protections to get that private copy.

Since when? Do you remember which law? I don't recall anything like the DMCA being ported to French law.

> So ripping a DVD is still illegal, despite the tax.

I'm pretty sure it used to be legal.

loup-vaillant··on Nintendo is suing the creators of Switch emulator Yuzu
Indeed it isn't: digital goods are non-rival, and as such fundamentally un-steal-able. Property as we usually understand it simply doesn't apply to them. There's still copyright infringement, but "unlawful breach of a state-granted monopoly" doesn't sound nearly as bad as stealing.

You wouldn't steal a car, would you?

loup-vaillant··on Nintendo is suing the creators of Switch emulator Yuzu
Here in France, as far as I know I have a right to private copy, which I pay for through a specific tax whenever I buy storage. I can rip my DVDs, Blu-rays, or even Nintendo Switch cartridges or hard drive, perfectly legally, even if it means cracking open the thing and circumvent stuff. It's awfully less convenient than downloading the stuff, but it is legal. Or at least it was 20 years ago, but I'm not aware of any change on that front.

Now there should be some ground rule. When you buy something, it's supposed to be yours, and you should be allowed to do what you want with it, especially studying it and sharing the results of your study. Any rule that allows some big corporation to retain power over something that's supposed to be yours is serious overreach and should be shut down.

Now Nintendo does have a big problem here: without the exclusivity of their form factor (which is arguably difficult to improve upon[1]), all they have left is the exclusivity of their game library.

[1]: https://loup-vaillant.fr/articles/ideal-computer

loup-vaillant··on Clean your codebase with basic information theory
The "problem that needs solving" as you put it, is I believe fundamentally not solvable. Not at the human level, not at the computer level, not even at the we-made-a-Dyson-sphere post-human utopia level. Because the speed of light.

No matter how efficient we are overall, what we can access the fastest is fundamentally limited, because what we can keep closest is limited. If you want to access information in less than 3 nanoseconds, a copy of that information must be stored less than a meter away.

More prosaically, the reason our screens offer only a small window, is because our eyes only offer a small window. The problem would not really be solved even with infinite resolution VR googles.

> Code is a database of functions. This approach is like trying to design a database in denormalized form.

I believe I disagree for the most part.

loup-vaillant··on In Defense of Simple Architectures (2022)
It's not that I wish I was there to prevent past mistakes. I just wish I could be allowed to fix the mistakes I see with the power of hindsight.

But there's worse: most of the time they already know. The various issues I balk at were often bothering them for years, and yet fixing it was never the priority. Week after month, there always was something more pressing, generally about some deadline. Such issues often have gone long enough that the cost of keeping the current cruft have long exceeded the cost of replacing it. But this cost is gradual, so the fix keeps getting pushed further and further into the end of times.

Perhaps my biggest mistake is not seeing that such organisations are beyond helping. I keep getting fooled by promises of doing things right going forward, when I should instead extrapolate the past. Either they're already work in ways that I can approve, or at least live with, or I should seek something else on the spot.

loup-vaillant··on In Defense of Simple Architectures (2022)
We can definitely ask for clarification. But fighting back is a grounds for being moved up the ax list. One workaround is trying stuff for free and present the results. Free labour for the employer, yay!
loup-vaillant··on In Defense of Simple Architectures (2022)
(Thanks for the compliment!)

I should be able to try this the next few weeks (new gig). But again, I'll be working on a prototype where such projections have already been made, the plan have already been laid out, and I'll mostly have to follow orders with relatively little wiggle room (they also expect me to hit the ground running). My only expected impact there is whether the stuff gets done on time or not. And assuming it is, the main company will throw the prototype away and rewrite everything anyway (at least they're supposed to).

loup-vaillant··on In Defense of Simple Architectures (2022)
I wish I could have that good timing, but I'm rarely hired early enough.
loup-vaillant··on In Defense of Simple Architectures (2022)
The reason I speak of "neurotypical bullshit" is because people around me have several times suspected I'm on the spectrum, and I noticed I have a hard time dealing with subtle social cues. One manifestation of this is when someone asks me something with a straight face, I tend to assume they actually want what they asked for.

When someone asks them feedback so they can improve, I tend to concentrate on what could have actual impact, and this heavily biases towards negative feedback: the build system is bulky and not well documented, newcomers waste time on it, we should replace those global variables by messages if we actually meant to do an actor model, this piece of code is 10 times bigger than it needs to be and will drag us behind if we port it as is…

To be honest, phrasing the above in a nice way that avoids hurting people's feeling is exhausting. They want to know how to make their system better? Well, here are the parts that suck the most, addressing those should have the biggest positive impact. Short and to the point. Oh you didn't want me to tell you that? Why did you fucking asked then?

loup-vaillant··on In Defense of Simple Architectures (2022)
It's how most people had me work. It's how most of my colleagues had to work too. Just doing what my manager tells me to work on is what is considered normal and expected in… 8 of the 10 or so places I've worked at.

The empowerment you speak of is but a faint dream in my town.

loup-vaillant··on In Defense of Simple Architectures (2022)
I rarely got to know the actual deployment scale of anything I've done. Let's make a list:

Ground software for an observation satellite. My internship was about implementing a dead simple neural "network" (2 hidden layers, no feedback), everything was specified from up top, we didn't even get to touch the learning algorithms. Impact? I guess a big flat zero, since all the differentiators was in the learning parameters.

Peer-to-peer social network before Facebook. Never made a cent.

Geographic Information System for the military. I was for obvious reasons not allowed to know enough to estimate the impact of my work. And even then all decisions was made by the customer, and once the user (a different entity) saw the Rube Goldberg contraption we dully made for them they predictably balked, and we did what we could from there. Which was, not that much. I did some useful stuff for sure, but mostly I participated in a system that was arguably worse than the one that preceded it.

A visualiser for civil radar data. Data in, little planes in the screen out. And other nice stuff. I designed a simple C++ API that allowed the client to write business code faster than we would have ourselves (if only because of communication overhead), saving weeks of work. That contribution was utterly ignored for personal reasons, and I was eventually out. I have no idea what my actual impact was, because I don't know how far the project even went, and how widely it was eventually deployed.

The maintenance of ground software for small civil observation drones. I did some cool stuff, but then was asked to transfer ownership of this software to a recently bought team (that did stuff similar to the company I worked for). I could have known how many drones were actually deployed, but to be honest my thing just saved a few minutes of flight, while most of the cost is to get the drone and its operator on site. That company was never really profitable, I hope the good people I met there are doing well.

Scripting language for a programmable logic controller test environment. For the military, so I don't think I was allowed to even know the size of the team we'd deliver the software to. I got good feedback from them (they were happy about what I did), and I'm pretty sure my static typing made things easier for them than if I had just picked Lua or something, but how easier, and how much money it will save in the long run I have no freaking clue.

Stuff in a missile company I cannot disclose. I believe my impact was almost nil, I couldn't stand their abysmal tech environment.

Maintenance of a ground troops training system (a glorified laser tag, with debrief helpers and so on). Good luck assessing the impact of a better system, and I was just asked to do small tasks I could barely chose anyway.

Prototype ADAS system. It was never deployed. Actual impact was therefore basically nil. Cool stuff to work on though, the CAN bus is a think of beauty. One of the rare instances where I could actually learn from example, instead of seeing yet again one of the gazillion obvious ways how not to do stuff.

Ground software for some IoT device. Impact fundamentally uncertain, we had yet to sell it to anyone.

Incident reporting software, based upon a more generic distributed base. I made the encryption layer (between users & company server), with a security based on PAKE (thus avoiding a PKI, which simplified the work of the sysadmin, at a slight loss of security). Impact fundamentally uncertain, we had yet to sell it to anyone.

Charging stations for electric vehicles. I did the TPM provisioning, and mentioned a low-key security issue along the way. I participated in a questionable micro-service that was meant to help user interfaces (yeah, their IoT stuff had a micro-service architecture). Impact: whatever I did didn't save them: one year after I left, they're now going under.

Preliminary study on the possible use of AMD-SEV to prevent users from peeking at our secret sauce (DRM). I don't think I was allowed to know the list of clients, and it's not even the only alternative. I don't think I could ever have assessed the long term impact of my work there.

Flight recorder for trains (not a flight recorder then, but you get the idea). I just did little tasks here and there, didn't get the chance to have a good bird's eye view of the thing or its environment. Deployment base was knowable, but the business impact of my work was likely minimal, beyond "finish this step so we can show the client we're on track for the next short term milestone". The whole thing is a heap of technical debt, common components are impossible to update (user projects aren't locked to a given revision, they all pull from trunk), the build system is a home made monstrosity that doesn't help more than the standard monstrosities (I hate build systems)… and I was just axed from a round of layoffs.

Cryptographic library I did on my free time: https://monocypher.org/ Nice little thing with a significant user base in the embedded ecosystem (not even my primary target). I controlled everything from start to finish, and I have no idea how many users I have, let alone how much time and money I saved them. In part because it is so simple, with such an outstanding documentation (which I mostly didn't write), that most users don't even have to bug me.

---

To sum this up, my resume looks fairly horrible with respect to what I know of my actual business impact. Most of it, I think, was entirely outside my control. And I don't think I'm exceptional in this.

loup-vaillant··on In Defense of Simple Architectures (2022)
I must be doing something wrong because most of the time, getting interested in the wider impact of my work is held against me. I just ask why they want the stuff, suggest alternatives, point out issues, and the next day I'm an uncontrollable Maverick that means to rewrite everything and waste a ton of time…

This also happens after explicit requests for feedback. Maybe they didn't actually meant it and I'm supposed to "take the hint" or some neurotypical bullshit, but when I hear such requests I tend to take them literally, and provide real feedback on the real issues. Unfortunately for all of us those tend to be stuff that ossified years ago and cannot (or will not) be fixed any time soon. Ever, in my experience. Quite the downer.

Last time this happened I ended up being axed from a wave of layoffs. Whether their short term workflow and subsequent technical debt finally caught up to them, or their parent company just wanted to cut costs, I will never know. I do know my technical expertise was highly praised, and middle management felt I wasn't quite aligned with the goals of the company, whatever those were. (I think one significant cause was that I only emailed them about significant problems, and kept to myself and my team lead when it was smooth. I think in the future I will stop trusting them with anything negative.)

So yeah, I can bet they love it when you act interested about their work, but start questioning their decisions (even just the one directly related to your own work and its likely impact on theirs), and the tone of the conversation changes very, very quickly. At least where I've worked.

loup-vaillant··on In Defense of Simple Architectures (2022)
Yeah, a sense. A guess. A gut feeling. Based on what exactly? I sure do get a sense of what will require less effort in the long run, or what will makes the user's life easier, or even what is likely to decrease the defect rate… but I dare 95% of programmers, even the subset active here on HN, to reliably assess the monetary impacts of those decisions within one order of magnitude, especially compared to the alternatives.

Not to mention the monetary impacts of decisions totally outside my control. I can tell the architect "you suggest A, but B is simpler to use and makes the API 3 times simpler at no loss of functionality", what's the point of estimating the impact of such a no-brainer when the architect answers is "you're correct, but we'll do it my way" (real story)? And how do you expect me to estimate the monetary impact of pointing out that their TPM provisioning is missing a verification step? That stuff happens inside the factory, a problem at this stage is unlikely anyways. And even if I could somehow divine my monetary impact, the best I can say now is "I did good work for this company, they didn't listen to me, and now they're going under". Not even kidding, they are going under. I just ended my gig there because I couldn't take it any more.

What are those wonderful places you worked at where you could estimate your impact with reasonable accuracy?

loup-vaillant··on In Defense of Simple Architectures (2022)
> Your goal isn’t to be intellectually stimulated at your job. If you want that, read a book. Your job is to deliver reliable, lasting value.

That's not my goal. That's not even what my employer wants most of the time. Most of the time, it's just about a bunch of rich dudes (and fewer ladies) wanting me to make them even richer. That's how the system works, no need to write the "C" word, or call me with the other "C" word just because I say it so bluntly.

My goal is to enjoy my life. I have various ways of enjoying life, many selfish, some altruistic, very few aligned with the will of the rich people up top. My job takes about a fourth of my waking hours (if I worked full time it would be a third), valuable time that I'd rather spend for me and my loved ones, instead of giving it to people who already have way too much. The only reason I can sometimes tolerate unrewarding work is because I don't have a better way to pay the bills.

The reason I don't over-complicate architecture isn't because it will make more money for my employer (sometimes it means making them less money, especially in the short term). I keep it simple because I can't stand wasted effort.

loup-vaillant··on In Defense of Simple Architectures (2022)
> Instead of “Built boring tech” try “Delivered $5,000,000 return 2 months early”.

How do I do that without lying through my teeth? 17 years on the job, I never had the data to even begin estimate that kind of things. It was never my job to know it (I'm a programmer, not an accountant), and it was often actively hidden from me.

And how did you do it? How did you get your numbers, and what did you tell recruiters when you didn't?

loup-vaillant··on In Defense of Simple Architectures (2022)
> In my experience the boring "I delivered a project very fast with X,Y and Z and saved the company $100mil" will win over "I rearchitected a massive system to run on microservices

Good luck having the opportunity to work in a project where you have even the faintest idea how much money your contribution will make or save. I don't know about you, but never in my 17 year career have I had enough information to even attempt computing these numbers. And even if I could have, it was never part of my job description.

So how did you know your numbers? Or if you didn't, how did you made them up for your interviews?

loup-vaillant··on Clean your codebase with basic information theory
Here's what I have to say about locality: https://loup-vaillant.fr/articles/source-of-readability

TL;DR: locality is likely one of the most important concepts in all of knowledge work. Of course we're a little obsessed with it.

loup-vaillant··on Non-code contributions to open source
Oh crap, I meant to reply to @LtWorf, and somehow botched it. I’m moving my comment, let’s say no one will ever know.
loup-vaillant··on Non-code contributions to open source
Then you're (unfortunately) not quite the target audience. Broadly speaking my library lets you secure communications and authenticate stuff. It does not however provides a turnkey solution for most of that. It has signatures, but no certificates. It has key exchange, but no protocol handshake. Thus as it is, it requires some familiarity with cryptography.

At your (apparent) level of understanding, you're probably better off reaching for a higher-level alternative, possibly even full applications like Age (that let you encrypts files), or Signify (that let you sign files).

loup-vaillant··on Non-code contributions to open source
That depends on what we're testing, and how thoroughly. Tests as documentation are amazing when the specs are in flux and we'd rather document stuff in one place instead of duplicating it between tests and user manual. But when the specs are fixed this is much less of a problem.

Then there's how much you need to test. Good tests go way beyond readable examples, they usually involve generating tons of tests with more or less random data and running them in a loop (property based tests). I do this, and to be honest I wouldn't recommend end users read them.

loup-vaillant··on Non-code contributions to open source
Edit: Oops, replied to the wrong user. Diplacing it here: https://news.ycombinator.com/item?id=39375470
loup-vaillant··on Non-code contributions to open source
As the dictator author/maintainer of a tiny library¹ (45 functions total), I can confirm the manual wouldn't be half as good without external contributions. And I daresay this manual is a major contributor to the usability of the whole project.

As a new user of libcurl, I was recently able to quickly implement FTP upload and adapt it to our specific use case thanks to their tutorials and API documentation. I was even made aware of the lack of thread safety in old versions thanks to that same documentation, so I could warn my team that we should update.

Documentation is bloody important. Almost as important as the code and the test suite themselves.

[1]: https://monocypher.org

loup-vaillant··on Pandoc
Is there a way to lock documents in some way, so that direct formatting is disallowed and only styles work? Not that we could truly lock a document, but at least having some sort of header that lists allowed features, such that one would get a warning whenever they veered off course?
← PreviousPage 7 of 34Next →