When I started doing open source software, that meant posting tarballs to Usenet and mailing list, occasionally mailing someone a hard floppy on request. I don’t have a github profile sparkling with emojies, but I think I’m doing all right.

I have 15+ years of experience being a software engineer and now I’m making a mid-six-figure income by going into companies who staff their “engineering department” with people who have five years or less of experience and cannot write a line of code without internet access to save their lives. So by all means go ahead and continue down the road you are going. We thought that stack overflow would guarantee a stable business but now that “AI” has come into play, we can’t even keep up with demand. We’ll probably raise prices by 25% next quarter. By the time that AI can actually produce decent results, I can probably retire twice over.

Removed by mod

GDPR does not apply to individuals.

TL;DR: you could adopt good programming practices like “don’t shadow mutable state” and “put constants first in a comparison” or you can pay us money so we show you obscure attempts to exploit your bad programming in code review … maybe …

This project is so necessary, we really need a modern, open browser engine that’s not going down the path of enshitification.

In case you didn’t know, this is the project Mozilla dropped by the developers Mozilla fired. So if you feel like at the end of the year you have some money left over, maybe consider joining the crowdfunding effort. (I am not affiliated)

Maybe Fossil might be something for you.

You probably wouldn’t. The main difference is that protobuf is structured while fleece is unstructured, so you would use it in places where you don’t want to (or can’t) tie yourself to a schema outright.

That is called a double round robin. It considered to be more fair, but also takes twice as long. You should probably set the group size to the number of players you want in your tournament, that’s kind of the point of a round robin. If you want fewer round that you have players, a Swiss tournament is probably closer to what you are looking for.

Round Robin should be what you want. In a round robin style tournament, everyone plays everyone else one. In your case, you will have a 5 round tournament, playing one of your participants every round until you have played against everyone.

Programming has very low hardware requirements, much lower than web browsing. Just don’t get sucket into the whole maelstrom of people trying to convince you that you need a bunch of complicated tools. If you are just stating out, Gedit or equivalent will work out just fine.

In terms of operating systems, if given the choice professionals tend to congregate around Linux and MacOS as the development experience historicaly has been much better due to having access to a proper terminal. This is something you want to familiarize yourself with if you haven’t already. Other factors may apply, especially in professional environments, where clients / employers mandate the use of Windows or something else, but this probably does not apply to you.

Universities usually have their curriculum, which is rather narrow in the beginning and widens in later terms, especially in masters classes. When it comes to teaching fundamentals, language and tools really does not matter much. It’s more about keeping things manageable for the teacher.

It’s a very good lesson- to the point where I wouldn’t be surprised if the teacher is deliberately putting an arbitrary restriction on the assignment.

It’s not arbitrary. When you start out on a profession, the first thing a good instructor does is make you unlearn the things you already think you know before teaching you the things you need to know. Think of it this way: When you pick up a golf club and start hitting the ball, you’ll drive it left and right. First thing you’ll be taught is to only hit straight. Even if you think you should try to drive a curve ball, a good teacher will not allow you. Only when you have mastered the basics will he teach you to drive curved balls. So ignore your teachers advice at your own peril, but it will most likely set you up for an expert beginners career.

As a closer, I can tell you this much: I received the same advice almost 20 years ago and now, after being a professional developer for two decades, I can not recall more than five times when a break statement actually made more sense than to rethink the algorithm.

Aaand… blocked

Given we know very little about the problem and runtime constraints, the second approach has the potential to have better performance, as with case 1. the average duration of the requests in a batch is equal to the worst case for all requests, while in case 2. the average duration of all requests is, well, the average.

I disagree. With licenses that are “straight proprietary”, it’s obviously whats going on. The FSL is proprietary but tries to gaslight you into thinking that maybe its kinda not. That’s clearly worse because it relies on manipulation and can only ever be useful to someone acting in bad faith.

Except its not like Linux at all. Linux uses the GPL which imposes no usage restrictions. This is why the GPL is a free software license and the FSL is a proprietary software license.

I would actually entertain the argument of protecting themselves against free-riding if and only if they would publish a transparency report detailing how they reimburse open source projects for the “common infrastructure” like, say, Linux, that they use to build and run their commercial offering and how they arrive at the amount they consider fair for their use. So far, I have not been able to find anything remotely like that, so their while argument is marketing and gas lighting.

This. Unless you generator guarantuees reproducible code generation and your build environment does the same across developer machines and CI, you are opening yourself up for “works on my machine but fails on CI” issues that are hard to debug. Since most developers don’t pay attention to these things (they really should), I would always advise to check generated code into version control.

Has anyone been in a similar situation - how did you resolve it?

I have been there and after half a year of lobbying for changes, the only real solution was to change jobs.

That is how fakeHash is defined, its just a bit more clear whats intended.