Plus there is another 1/3 coming from Latin which French speakers has no issue understanding either. English is basically akin to a dumbed down pidgin of French (exponentially less verb conjugation, no gender agreement, less pronouns with the thou/you merge, less articles and annoying small words, etc.) starting over a Germanic core.
Harsh but that rings true. In it's defense i'll point out that English is exponentially more useful in the modern world and even French has started borrowing nouns from English. Also English has more words then
any other language which in my mind makes it the best. (to clarify i know a little of other languages and i understand that there are concepts which English is not even equipped to express properly but i stand by what i write)
I'm still learning, English is huge and it can be a delight to discover.
Most words in foreign languages that most people believe don’t have an English equivalent often do, but the English word is so obscure that almost no native English speaker knows it, and as you point out, English vocabulary is so large that no one will ever come close to learning it all. English is the C++ of human languages.
What interests me is the prominence of words in foreign languages that have an extremely obscure equivalent in English. Like, why do they devote common vocabulary to it and what does it mean that they do?
I have been conversational in languages almost no one learns from parts of the world no one cares about. They are full of words like this and I still use those words in English because that was the first word I learned for the concept. But when I’ve taken the time to see if an equivalent English word exists, it always does. Ironically, it is safer to assume that my ignorance of the English language (my native language) is more likely than the lack of a word in English for a thing.
That's exactly what I'm alluding in my other comments thread but referring to Chinese language and writing system complexity rather than English for the C++ and Rust, but on second thought Rust probably be the Chinese equivalent.
> But when I’ve taken the time to see if an equivalent English word exists, it always does.
It's the same happen with C++ that has been ripping up Dlang features for quite sometimes now including its new module system [1].
[1] Converting a large mathematical software package written in C++ to C++20 modules (42 comments):
A few weeks ago people were discussing here how their typing speed was making them code faster. On the other hand I haven't been limited by writing code, the linked article match my professional experience.
You have to be fluent on the keyboard, to type without thought or 'hunting and pecking' if you want your ideas to flow from brain to pc smoothly and uninterrupted.
Speed is part of fluency and almost a shortcut to explaining the goal in real terms. Nobody is hunting and pecking at 80wpm.
I often out think my typing pace and have to cache ideas. The faster you can offload cache the less you end up having to manage. It's an effective way to rapidly reduce cognitive load and if it isn't in your toolbox then you're missing out on a valuable bit of kit.
I think the better question is, "do I benefit from improving the speed here, for the cost it takes".
Improving typing speed from "fast" to "faster" is very difficult. I think it's worth distinguishing between "typing faster is not useful" and "it's not worth the effort to try to type much faster".
There are sometimes cases where it's worth paying a high cost even for some marginal benefit.
Sure. In my 20s I remember telling my boss that I had so much fun programming that I would do it even if I wasn't paid. (That was probably a mistake, but at least it was a state job with salary guidelines.)
But having fun and playing as part of work is doesn't mean I was "playing programmer." Even had I been an unpaid trust-fund baby.
What does "play Viking" mean to you, and how do we know that's what this researcher is doing?
Would you also say that he "plays sailor", given that he's an actual sailor?
Should we say the people building the 13th- century style castle at Guédelon are playing serfdom?
Those trying to rediscover ancient building techniques are playing Egyptians, Romans, Eastern Islanders, Incans, etc.?
Was Thor Heyerdahl was "playing a 'Tiki person'" in his famous raft voyage, when that culture doesn't exist, or was he trying to demonstrate that the raft hypothesis for human migration could not simply be rejected as impossible?
I said that describing the researcher's work as "play Viking", done as a way to monetize one's PhD, is dismissive.
The more so as the researcher was partially self-funded, and didn't have a PhD.
I don't think it's right to characterize everyone doing experimental archeology about Norse practices as "playing Viking", nor to only pick out those studying shipping routes.
The same for other fields - I wouldn't say that people researching how the ancient Romans made concrete are "playing Romans".
I’m not sure why you seem so fired up about this turn of phrase using the word “play”. But, in recognizing that you are, I’m simply going to let you do you and wish you well :)
> The initial setup effort in LaTeX becomes minimal as this cost is "amortized" over the document.
I'm still sour about the 3 days it took me to have something usable for my thesis, and I was starting from an existing template. And it's still not exactly how I want it to be; I gave up on addressing a bug in the reference list.
I wrote mine in Latex, along a team mate witting in Word. Her onboard was way faster, but she had to fight really hard in the end for Word not messing up everything on the smallest changes.
Meanwhile, when I had a decent setup I could move a whole section from the intro to the results and the overall layout didn't suffer (floating tables, figures and code still in place, references still pointing where they should). I had code snippets with colour highlights imported from the actual source code (good luck trying that in Word). I could insert the companion papers with a single line of code per document, and they looked great. I even had a compilation flag to output the ereader version.
My take was that Word enabled my team mate to kick a lot of cans down the road (but the cans eventually came back), while for me the reverse was true: build a decent foundation, and after that it was all pure write-cite-compile.
My school just had an official cls file, so my initial setup was just to download the template. So if that's where you're coming from (the journals I submitted to also had official templates), it's really minimal setup.
Yes it's defined for fictional characters, but I have the feeling it's more due to their obsession of details. I've never been asked my blood type there in years, whereas some Taiwanese girls asked me the question.
Oh, they definitely believe in that stuff. Maybe you haven't been asked, but I have, and have been explained how your blood type defines your personality.
I'm pretty sure there is way less regulations in the US in respect to France where going over the legal 35h/week requires additional capital and legal paperwork.
In France most white collar jobs are categorized as "management" ("cadre"), and they have no time limit. It is very common for workers to clock 12h days in consultancies (10am-10pm) and in state administrations, for instance.
This is not true. Government workers or factory workers can limit to 35h (with some salary loss or days off loss), but else than that (especially in tech) it is very competitive and working 50 hours+/week is not exceptionl.
La durée hebdomadaire de travail calculée sur une période quelconque de douze semaines consécutives ne peut dépasser quarante-quatre heures, sauf dans les cas prévus aux articles L. 3121-23 à L. 3121-25.
It seems that 20% of employees in the private sector are "cadres" and half of them are on "forfait jours". That makes around 10% of the private sector employees working 218 days per year without the 48/44 weekly hour limits. It's more than I thought but I doubt that many of them work more than 10 hours per day. Whether that's "exceptional" or not is a matter of definition, of course.
What do you mean with work more than 10h/day for intellectual work? You don't stop to think the moment you are away from the production machine. And the exact opposite can often happen: you go away from the computer/board/paper/office, make a walk trying to wander at something else as far as you can stear consciousness, and then the solutions/ideas land in your mind.
You’re not wrong but what did the commenter above meant with “50 hours+/week”? Weeks have three times as many hours. Years also have many more than 218 days.
Anyway I found an official survey saying that 40% of them work more than 50 hours per week (but fewer weeks than regular employees) so I guess it’s not so rare (around one private sector employee in twenty).
In the USA most software engineers are FLSA-exempt ("computer employee" exemption).
No overtime pay regardless of hours worked.
No legal maximum hours per day/week.
No mandatory rest periods/breaks (federally).
The US approach places the burden on the individual employee to negotiate protections or prove misclassification, while French law places the burden on the employer to comply with strict, state-enforced standards.
The French Labor Code (Code du travail) applies to virtually all employees in France, regardless of sector (private tech company, government agency, non-profit, etc.), unless explicitly exempted. Software engineering is not an exempted profession. Maximum hour limits are absolute. The caps of 44 hours per week, 48 hours average over 12 weeks, and 10/12 hours per day are legal maximums for almost all employees. Tech companies cannot simply ignore them. The requirements for employee consent, strict annual limits (usually max 220 hours/year), premium pay (+25%/+50%), and compensatory rest apply to software engineers just like any other employee.
"Cadre" Status is not an exemption. Many software engineers are classified as Cadres (managers/professionals) but this status does not automatically exempt them from working time rules.
Cadre au forfait jours (Days-Based Framework): This is common for senior engineers/managers. They are exempt from tracking daily/weekly hours but must still have a maximum of 218 work days per year (including weekends, holidays, and RTT days). Their annual workload must not endanger their health. 80-hour weeks would obliterate this rest requirement and pose severe health risks, making it illegal. Employers must monitor their workload and health.
Cadre au forfait heures (Hours-Based Framework) or Non-Cadre: These employees are fully subject to the standard daily/weekly/hourly limits and overtime rules. 80+ hours/week is blatantly illegal.
The tech industry, especially gaming/startups, sometimes tries to import unsustainable "crunch" cultures. This is illegal in France.
I think there is theory and there is real life.
As tech worker, in 20 years career, in private sector, I have always been on forfait jours, working more than 10h/day on average, during many years weekend included. I never got paid extra hours. So I get what you say about the perception and the law. The French law is protective (i.e if I can prove that in a court I'll get my extra hours paid for sure but my career would end. Period.
Some State services, such as the "Trésor", which oversees French economic policies, do not respect this at all, and require 12h work days most of the year. The churn is enormous, workers staying there less than a year on average.
Even in government; I've worked 50+ hours weeks working for the healthcare branch of the providence state, with a classic 39h/w contract. No compensation of any sort, despite having timesheets.
There are a lot of myths about French worker. Our lifelong worked hours is not exceptional; our productivity is also not exceptional.
Excellent way to get blacklisted and never work for the State again if you're a contractor, or end up in a low impact, boring job if you're a career worker.
>the branch of science and technology concerned with the design, building, and use of engines, machines, and structures.
Not this one.
> (alt) a field of study or activity concerned with modification or development in a particular area.
"software engineering"
This one ^^^
Too many people seem really triggered by this. I don't know why, but it's weird. It's just a term. It's well understood by now. The first 5 pages on google all state the same thing. Why bicker about something so trivial?
Using exactly the text you quoted. Since it's about Hitler, Nazi and camps the TV channel ARTE will fund it in a heartbeat. (The current top movie on arte.tv/fr/videos/cinema is "Lili Marleen, un chant d'amour dans l'Allemagne nazie)
Very outdated view. Csproj files got hugely simplified with dotnet core, and thanks God they kept the XML format instead of the JSON they tried at first.
