And then managers go “why does shadow IT exist?”

…you have my condolences

Yep, being familiar with the data model is 98% of the effort.

The remaining 2% is the query

But it’s genuinely what we were all doing not so long ago

Jokes on you, my first job was editing files directly in production. It was for a webapp written in Classic ASP. To add a new feature, you made a copy of the current version of the page (eg index2_new.asp became index2_new_v2.asp) and developed your feature there by hitting the live page with your web browser.

When you were ready to deploy, you modified all the other pages to link to your new page

Good times!

I disagree unless the tests are reasonably high level.

Half the time the thing you’re testing is so poorly defined that the only way to tighten that definition is to iterate.

In this sense, you’re wasting time writing tests until you’ve iterated enough to have something worth testing.

At that point, a couple of regression tests offer the biggest bang for buck so you can sanity check things are still working when you move on to another function and forget all about this one

Wow, and here I was trying to set breakpoints using the devtools debugger and faffing around with sourcemaps.

Wish I knew about this 10 years ago!

Actually, it makes perfect sense.

The loose terms like morning, noon, night etc are related to the suns position in the sky and exist regardless of what the wall clock happens to say

var context = RuntimeSingletonFactory.getCurrentFactory().getCurrentRuntimeSingleton().getContext()

A good project manager also returns 403 forbidden to middle managers trying to scope increase projects or poach project members

Only the ones that work for the BBC

As someone in Java land, you might be more impressed about its memory footprint rather than its performance.

Your Java hello world that takes 4GB of JVM heap space or it will fail with OutOfMemory would likely be only a few mb in Rust (or even less)

Came here to mention this

There’s nothing wrong with putting Rc<> or Rc<RefCell<>> around data

It’s mainly the visual pollution that bothers me. Wrapping everything in the reference counting smart pointers just because you can’t be bothered dealing with the borrow checker seems like an antipattern

At the end of the day, the first thing managers do is convert story points / tshirt sizes / whatever other metaphor back into time estimates. So why bother with the layer of indirection.

I’ll die on the hill that most teams do not need scrum / agile and all the ceremony that always goes with it.

A kanban board with a groomed Todo column is all you need. Simple and effective and can easily adapt to unexpected scope changes a.k.a production incidents.

*yes I’m aware that if you’re getting bogged down in ceremony you’re doing Agile wrong. I’ve never seen or worked in a place where I’ve felt it’s been done right

Don’t avoid JVMs for “security” reasons, the security industry will raise CVE’s against anything they think will look good on their CV.

Avoid JVM’s because they are synonymous with overengineered, bloated, overly verbose code with crazy memory requirements for what they deliver

They have played us for absolute fools

Refer to the meme - “Linux users and other Linux users”

I use Arch btw

No way, Debian stable is completely useless as a distro unless you’re in to time machines and like the feeling of being stuck 5 years behind the curve

endSegmentation fault. Core dumped

Got 'em!