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.

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.

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.

I would doubt that. Github for organizations becomes rather expensive rather quickly if you want to retain some level of control, so I doubt Mozilla will opt for the minimum “free for open source” offering.

Sure, if you regard scientific studies and statistics as conjecture, then your right, it’s pure conjecture.

Wrong. Yes, typing speed does not matter when counting up lines of code. Code programmers however are not just code monkeys. They write documentation and comments, communicate with peers and potentially users, take notes on their own thoght processes when pondering on the best solutions for hard problems, etc. On all of these point and many more, typing speed matters. People who can type and type fast(-ish) communicate more expressively, document more comprehensively, make less mistakes when spelling, etc.

So yes, typing skill matters.

Your claim is that there is value in using a metric that has zero meaning and validate your own negligence in claiming that it makes your choice better than random through popularity. I claim this is lazy and negligent. Please tell me what I misread.

Actually, IBM and Germany have a long history of state driven digital innovation …

https://en.m.wikipedia.org/wiki/IBM_and_the_Holocaust

Github offers the Insights tab on every repository that provides you with actual data in those points. There are countless repositories out there that have thousands of stars and literally on person contributing to it. If you go by stars to sway your verdict, you are simply to lazy to do your due diligence which in turn makes you a bad developer.