Thankfully, it sounds like the child's mother won't be required to go to prison for a year - as long as she agrees to always have someone physically watch her son, and additionally surveil her son 24/7 using an app installed on their phone.
I wonder how many people these days think that they're going too light on her, and are thirsting for stricter penalties?
Maybe, but, I've never heard of any cases like this.
Granted, I'm only 32, have only lived in Canada for 32 years, and haven't checked to see how common it is for parents to be sent to prison for things like this.
It's worth noting that the person who said that they'd only hire junior developers who know git isn't the President of the United States or anything, and can absolutely make their own hiring decisions.
It's perfectly reasonable to make your own hiring decisions, IMO, and asking people to know git, or the fundamentals of version control seems totally fair, IMO.
If people are willing to spend a few weeks solving leetcode problems, or answering mock interview questions, I feel like they could absolutely spend 15-30 minutes learning how to use git.
This is the nuance that people aren't able to understand anymore - something happened when the Internet came out, and we've never been the same.
The OP was just surprised that people don't know git, and indicated that he wouldn't hire a junior engineer who didn't know git, but, there's very likely nuance to this, and I don't think that one person's personal preference necessarily needs to be discussed and debated extensively on Twitter, HackerNews, etc.
In my opinion, git is a very popular tool, and lots, and lots of people use it - and it only takes 15-30 minutes to learn the basics - for this reason, I think that it is fair to be surprised that someone doesn't know it.
This has proven to be an extremely controversial topic, but, in my opinion, it's perfectly okay to use git in college or university, and we should encourage, not discourage people from using technologies like distributed version control software.
You could substitute git with WhatsApp, Google Drive, or e-mail for small projects, and get by just fine, but, why not spend 15 minutes learning the basics of git?
As far as I know, the use of git and other distributed version control software is very popular, and we don't see the same hesitation when adopting technologies like Google Docs and its collaborative editing features in college or university.
Is distributed version control software truly a controversial technology?
If distributed version control software is not suitable for use in college and university, what would be a more appropriate technology?
The university could even setup their own private self-hosted Gitlab and use it as part of assignment submission.
10 years ago, my no-name college had a CS degree that required us all to take a "Software Engineering" course that covered the fundamentals needed once you graduated, including Git. We did group-style large coding projects where teams had to submit their GitHub repo at the end.
The prof was able to review who committed what and then hammered us on good commit messages, clean coding style, testing, etc.. I feel that a large part of my career success was due to the early start I had from that course.
I think that this would be a great idea, and could also help combat students not doing anything in group projects.
I lone wolfed most of my group projects in college, and don't have any regrets, but, of the projects that I didn't loan wolf, most people didn't write a single line of code, or only contributed in relatively inconsequential ways.
I think that adopting distributed version control systems in higher education would be mostly good.
I noted that a function wasn't available in the snippet in my post, but 2 users still voted to remove the question without any feedback, person-to-person communication, etc., because it broke the rules.
While I'm a rule-breaker, and the problem, maybe GPT4 is where to go for code reviews.
I was moreso thinking of review comments like "this is the worst code I've ever seen", "give up now", "ignoring the hundreds of errors, this looks fine", Dreamworks villain laughter, etc.
Ugh. I feel you, which is why I unfortunately had to hedge with l "Often one or two of the reviews...". I think the best way to handle that is to understand you'll have to separate wheat from chaff, period, that's just the price. The good news is, once you learn to ignore comments like that you don't really need to worry about it ever again.
I get what you mean, and agree with the idea of Just Building Things, but, I also want to make sure that I'm building things "the right way" if that makes sense.
For example, I'm not new to programming, but am new to Go and have been struggling to figure out how to model messages as structs using composition rather than inheritance.
As one of, if not the most senior developer in the team that I work on, I have nobody to ask questions to, and even though the answers are out there, on the Internet, I'm still confused by them, which, IMO isn't super anomalous, but, still leaves me in a place where I'm yearning for feedback.
My preferred approach for that kind of difficulty is just to look at how existing open-source projects have solved similar problems. You'll either figure it out or come away with specific, informed questions that you can ask on a Discord or Reddit or something.
That makes sense. I'm trying to wrap my head around Dubray's State-Action-Model and have reduced it to rewriting examples from different perspectives (first starting with the model, for example).
I found this answer on StackOverflow about Go structs for composition. It's interesting because at least there's an example of how not to do it (in Go) and a detailed answer:
I wonder how many people these days think that they're going too light on her, and are thirsting for stricter penalties?