The names of the two pictured: Laurel and Yanni.

🤨

I have no ties to Newfoundland, but I absolutely love their unique phrases. Looks pretty nice too.

There are no absolutes, and most of these “myths” are at least true to some extent. Much like any paradigm (worse is better, whitebox testing, lbyl vs eafp, etc), none are universally best. And all are helpful to know about.

How awesome / terrifying is it that this is a question which no longer has a clear answer?

How to keep the Winamp’s back.

Even:

No

Would be better than nothing.

That works great as an adjective. Don’t be such an octopussy.

I gotta respect anybody using the proper pluralization.

You may want to add a 👍 to the request.

Yes true, but people that don’t know what terraform is are probably not the target audience of the beta to initial GA release announcement. The website should make clear what it does for anybody stumbling into the project, and if it doesn’t that should be improved.

The primary audience here will be people already using or about to use terraform that prefer an open source license and have been waiting for this replacement.

Love his videos and this one is even more superb than usual. Love how he decided to handle the monetization of exposing the raw theft uncovered.

It was. And I really appreciate that.

This is to me an question lacking very precise requirements. But you say you need batches, so it sounds like option one (batches) is the only option that satisfies the “batches” requirement.

This is one of the most legendary videos. Numa numa / Leeroy Jenkins club.

Author is MonkeyUser, but is cut off because the world is brimming with assholes.

https://www.monkeyuser.com/2018/final-patch/

There was something like that on Reddit but I can’t remember the sub. I haven’t seen one here. The best way to get reviews of open source is via contributions to larger projects. That of course doesn’t answer your question directly but is worth noting.

I’d recommend joining some discord or matrix servers for the language you work in or likeminded folk. They tend to have channels for that, and some have really helpful communities.

eta: I just checked my local instance and saw a community with very few subs and zero posts called /c/reviewmycode. Somebody has to post first.

100%, but my understanding is that most often applies to fields of engineering outside of computer science like mechanical, chemical, structural engineering etc. But there are licensing bodies for achieving Professional Engineer of FE in some cases for CS.

I am not a lawyer but I presume most laws apply to claims of such certifications rather than job titles. In either case most people don’t pick their own job titles. Just don’t put PE, after your name, same as you should not just randomly throw BSN or MD unless you have a registered licensure.

I rarely read comments in code, that is from within source code anyway. I of course write comments explaining the behavior of public facing interfaces and otherwise where they serve to generate documentation, but very rarely otherwise. And I use that generated documentation. So in a roundabout way I do read comments but outside of the code base.

For instance I might use godoc to get a general idea of components but if I’m in the code I’ll be reading the code instead.

As others have said, your code generally but not always should clearly express what it does. It is fine to comment why you have decided to implement something in a way that isn’t immediately clear.

I’m not saying others don’t read comments in code; some do. I just never find myself looking at docs in code. The most important skill I have cultivated over the decades has been learning to read and follow the actual code itself.

Poorly defined nomenclature. Simple as that. I’m an “automation engineer”, have had many other titles, but anytime I write what I do, like LinkedIn or such, I write “programmer”, because it is simple, descriptive, and I like it. I’m old, but I used to like ”hacker” until it came to imply nefarious programming.