gw99

It depends how you interpret it. There is some dynamic range compression on over-exposure which can save you if you blow something out. If you underexpose Kodachrome you are screwed.

I prefer the crutch of 12 bit RAW and Lightroom which usually gets me out of the same sticky situation :)

There are Kodachrome presets off the shelf for Lightroom. I did a double-blind test a couple of years back with a few friends who shoot film only and no one could reliably tell the difference. It's another audiophile thing.

Incidentally I still shoot film myself occasionally, Ilford B&W on an old Praktica w/ Zeiss lens. It's slow, painful, I screw up 1/4 of the shots and occasionally destroy a whole roll while developing it. But it's fun. When it's no longer fun, out comes the Z50...

Send in more lawyers!

I've used a tiny subset of vim for about 20 years that sits just above plain vi. It has been a very comfortable place to be. And it works well on Windows with gVim as mentioned.

Someone came up with an idea to make money and you're getting it if you like it or not.

Welcome to corporate America.

Yes. This is the first I've heard of it and I've got a ton of scripts that are probably going to break.

This is probably the most unsurprising thing I've heard all year.

Still a parenting issue! Just a bit late.

That point is recursive...

No - people are cheap and lazy. Pay for the support, do the work.

This is quite frankly utter bullshit unless there is a lack of parenting going on i.e. you brought your kids up to be judgy assholes.

My kids and their friends have a right mix of all sorts of phones. They don't even talk about it. They just work out how to deal with it. Mostly that results in them picking a common platform, usually Discord or Snapchat and using that.

This is not a technology issue!

What's even worse is that IAM and Trusted Advisor will tell you what stupid things you have done. At no point does their article give guidance in turning that on. Because it compromises their sales pitch.

Also if you push AWS keys into github (this does happen from time to time at the best organisation), github will nuke the rev. And even if you did it successfully there should be no damn keys which are usable because anything human issued should be via SSO and windowed or have MFA required set up. Everything else should be assume role based.

Something I learned a few years back: Never read vendor or conference blogs.

The number one cause of AWS security issues is human error or not understanding what you are doing. AWS provides a hell of a lot of tooling, documentation and guidance to manage those risks out of the box. What doesn't help is buying a vendor product first and assuming it's going to do magic unicorn farts and make everything ok. What it will do is cost you a ton of money and time to tick a box somewhere that seemed like a good idea.

Someone selling a solution to those is selling you snake oil.

All of the issues identified will be picked up by Trusted Advisor or complain loudly on the IAM dashboard. If you don't notice that or don't use it, then your funeral.

This is the worse than the corporate dystopia I imagined back in the 90s.

Isn't that the intent of it?

Same as purchasing Twitter?

Found a similar rig set up years ago. The old Tektronix TDS scopes used to lock up in a go/no go test rig and stop responding to GPIB commands. Someone unknown got fed up of it so they wired a relay in a box up as an inline switch for the scope power and drove it from a spare port in a GPIB switch box that the test script talked to. This turned the scope on and off again before each test cycle so it was less likely to crash. This saved hours and hours of failed test runs.

So you can use nice tools to bake a poop cake :)

That's not particularly pointed at PHP that. There is a big problem in this industry about where we get our software from and how it's built and managed but that's well outside the topic of this thread. Fundamentally everything is fundamentally broken with dependency management, trust and competence.

I was being paid large amounts of danger money to undo damage.

That's the Visual Basic guys who do that.

The PHP developers spend most of their time outside smoking.

I spent most of 2005-2013 doing contract work getting people out of near business ending buckets of shit thanks to the PHP community's inability to produce a product that was fit for purpose and the awful staff contracting building on top of the wobbly pillars of excrement. Slither is exactly the word because they were the first people to slither away and point fingers elsewhere when something was wrong. Now ten years after that I am in regular contact with people actively getting rid of it and it's the same problems. And here I am now on Sunday evening eviscerating another failed nodejs stack left by the same slithering fiends.

Oh no it's exactly right. Slithering is the word.

I don't get anywhere near this level of sheer incompetence on a daily basis in the Python, .Net or Go ecosystems. Nor do I have problems sleeping wondering what shit show am I going to face on a Monday morning with them.

I'm sure I'll get downvoted for this one but quite frankly it's where the PHP developers all slithered off to. It was inevitable.

I avoid to the point of refuse to work with any JavaScript platform at all. They are a universal shit show.

Edit: honestly I stand by this comment. I literally have spent hours this year dealing with fucked up messes in nodejs, package security issues after repos were hacked and code made it into NPM that displayed banners on commercial sites. My comment is toxic yes but quite frankly both communities are as well (PHP and NodeJS) and utterly earned that ire and discontent. The fact people lean on the stack and produce stuff that handles critical aspects of people's lives is utterly frightening. So yeah toxic, I don't care. Feel free to be annoyed. It's still a turd, just been rolled in glitter.

Yes I have a project manager that operates it for me.

JIRA does not suck as bad as that thing following my cursor on that site and believe me I dislike JIRA a lot.

They'll hire all Rocky contributors in under 3 years and turn it into a rolling distribution.

That's how Redhat works.

This is one reason I switched to Apple's mail services. Apple's client is 100% offline and it all just sort of works without having to fuck around with IMAP settings.

That would have been nice. Cached 9P perhaps.

Instead we got OneDrive, Dropbox and iCloud. Ugh.

I worked over RDP for a couple of years. It's not terrible but it's not too good either. You pretty much have to have a wired Internet connection and there are still problems with Alt+Tab and high DPI displays.

That's a reasonable compromise from your org. Good on them. I was suffering with corporate OneDrive. Fortunately everything I do ends up in git anyway so I just turned it off and don't use it.

Yep. Having worked in these environments, this solution is almost always sold to companies that are working around shitty hard to reproduce software stacks, staff trust issues, scale up difficulties and checkbox security cargo cults. The resulting outcome is usually increased staff turnover, increased cost and decreased productivity. Most of this they are having trouble rationalising or acknowledging still.

You don't want to work for those companies.

It's notably different if you have a cloud VM running linux and you're connecting to it with VScode or something over SSH. That's borderline acceptable. The reality is usually some horrible AWS, Azure or Citrix portalised solution however.

No wasn’t them. Similar concept though.

When you are in a regulated industry it’s better to be sure than incur the wrath of the regulator.