MajorHavoc @ MajorHavoc @lemmy.world

Posts

2

Comments

996

Joined

2 yr. ago

perhaps 1 in 100 software developers that might apply for a job are really up to snuff.

Lol. This is not the calibre of the developer pool, it's that the company sucks and the great developers can tell that by the time they finish reading the job post.

Edit: Let's all say it together: "Great developers land at great jobs with great bosses and great pay and great work/life balance." Then they spend decades telling anyone asking them to change jobs to go fuck themselves.

Source: I hear a polite version "go fuck yourself" all the time. Usually over a shared lunch that I paid for. As it should be. The talent is out there, and mostly happy where they are. They just don't want to talk to a shitty employer. Heck, they usually don't even want to talk to my excellent employer.

Holy cow! You've done it! You could wrap this (static text block) in a web API and sell it.

Edit: /s, I guess. But that text really is easily an 80% solution for meeting summaries.

Hell yes! I'll join the front of the hype train if they can demo an AI fielding questions while a project manager reviews a card wall.

You just defined it perfectly.

"Elegance" early on ends up being a mistake. The chosen abstractions look really nice, but turn out to be the wrong ones for the unique problem domain.

The first six times I encountered it, I thought the team got unlucky. Then I recognized that it's a pattern/mistake that pretty much every new formed development team falls into.

Even when I'm on the team, I end up being "old man yells at cloud", and they add early abstractions anyway. (Which I don't mind.. As they point out, there's no harm trying to get it right on day one. The harm comes from believing we got it right.)

The benefit I can bring is introducing patterns that support refactoring: regression test automation, strong ruthlessly fast test pipelines, and chat-ops.

Considering the almost complete lack of standards, certification, licensing in most areas of programming, I don't think there's a ton of difference.

I've held both titles without rhyme or reason between the two. Even in areas requiring high compliance - HIPAA, PCI/DSS, NIST Standards, FERPA, etc - training achieved doesn't tend to be reflected in a programmer's title. (Even while the same level of training turns into acronym soup among their IT peers.)

One way I try to live up to the title "Engineer" - even when I don't wear it - is by holding myself to the Engineering Code of Ethics.

That's the most evil thing I've heard in awhile, and I would absolutely make use of it anyway.

"I just serve him warm milk."

Mind blown... Everything else... Also blown up.

This joke has layers, is quite funny, and kind of hurt. Just like my pointer handling code!

Yep. Incredibly powerful, and it will not hesitate to help you blow your own legs off.

The big difference is that git will save your legs in reflog for a couple of weeks.

Everybody thinks that this time will be different, and we will definitely build an elegant solution from the ground up.

It's a helpful delusion, because we feel good knowing we won't have to waste time refactoring later, once we actually understand the problem space.

Actual elegant code earns it's existence by retaining and enabling thoughtful developers to work from one hack to another, with enough breathing room to try out the fixes they think of.

If I inherited your team tomorrow, our top priority would be fixing anything that causes slowdowns - especially lack of CI/CD and lack of test coverage.

My top priority would be enforcing collaboration patterns over grandstanding (and probably building the case to fire my worst grandstander), while telling every stakeholder that their pet project is on hold while I put the delivery pipeline in order.

Fun times, but also extremely usual in development shops.

I predict that, within the year, AI will be doing 100% of the development work that isn't total and utter bullshit pain-in-the-ass complexity, layered on obfuscations, composed of needlessly complex bullshit.

That's right, within a year, AI will be doing .001% of programming tasks.

Who has four thumbs and a top tier business plan? This AI!

I'm not doing anything particularly specific to PowerShell - I just like the web-request module, and excellent JSON handler, because I do a decent amount of web API stuff from the command line.

I could curl+awk+sed this stuff, but the equivalent PowerShell is so much faster to write, and more concise to maintain than i.e. my zshell solution would be.

Even in a few places where I'm using zsh as my term, I'll still call into PowerShell if I already have a nice piece of PowerShell that does what I need. The two interoperate well, but I lose the object oriented pipe once the data is back in Zsh, of course.

I can imagine it.

I can already hear the compelling argument why their chaotic good cleric should be able to use 'purify water' on their own piss to pass the test.

Honestly, I would probably just allow it, but force the party to make a bunch of stealth tests to not get caught passing their pee samples to the cleric.

That's a good solution. Python is an excellent, and very portable solution, for sending emails.

True, you're certainly not forced to learn PowerShell if you're about to switch to Linux.

That said, PowerShell is my preferred shell on Linux.

PowerShell is open source, works great on Linux, and is even one of the pre-installed shells on Ubuntu.

And yes, I'm not sure what to think of all that, either. It's weird. It's also really useful.

Gotta let it know we mean business! /s

If I were GM, I would rule that it can technically use swimming through concrete to gain advantage on a sneak attack - but only after completing a DC 20 Will Save against spoiling the surprise by shouting "Jawesome!".

I'm not sure I perfectly understand... But I plan to ship my son off to live forgotten with my adoptive parents in a culture totally foreign to him... Just in case. /s