Funny thing I had a paranoid freakout too before I got hacked on AWS, I had bought a visa gift card and that’s what I put in as a payment card on AWS. Of course they know where I live and could still screw me, but they would have to do it on their own dime.

They make it really hard to leave or just use a specific service only. I use them for DNS, objectively it’s supposed to be cheap AF pay yearly, but now I have to pay $2 a month just to do all the auxiliary stuff to notify me that I got hacked.

I’m buying a server rack soon and just got a full symmetric fiber line put in so I can do my own hosting.

It’s not fun, I got hacked through an archived git repo, for when I was learning to use AWS, following tutorials and whatnot.

Forgot about it for years, then out of nowhere got hit for 27k…needless to say I said good luck collecting that shit.

They waived it all granted I logged in and deleted all resources that were running as well as removed all identities. Sure as hell I did that and saw a ton of identities out in the middle of nowhere. Fucking hackers ran up a shit ton of AWS sagemaker resources trying to probably hack some dude’s wallet.

Every time I see a tutorial on how to deploy x in AWS, I get pissed. The newbies need to learn about administration before they start deploying shit on cloud infra.

Free market ftw rite?

Sorry dude…writing simple queries is what I said was easy…and for the record they are. That example is probably not a great example. Simply from my experience, I never started my career in IT, I was in healthcare and far from it all.

Anyway, I’ve had some idiots approach me about their shitty ideas before too…most notably was one person asking to create an app that “uses AI” to help a person search for the right individual when they send a text message. Couldn’t explain how it would know that it found the right person? There was another one that wanted to track the origin of “content” and how it changes over time on social media… again “using AI”.

For my team I have a mirror that I set up and have a bunch of ELT jobs that load the deltas every night. Queries don’t ever run in PROD, if someone needs a specific view or more data, they go through me and my team. I also set timeouts, precisely to avoid the ahole from using Select * from. Also have a bunch of reports I created to see who is running what queries and timings. We review them quarterly or when someone complains or when a project that needs our data asks us for access.

We also have an autogenerated data dictionary for folks to use as well. Generally I don’t entertain any “it’s slow” complaints unless they go through the documentation, provide their exact query and write what it is they’re trying to get.

My assumption was that OPs shop does the bare minimum in terms of making sure they don’t shoot themselves in the foot.

Ooof my guy if you got folks running queries on your PROD db you got bigger problems even if they were the best SQL writers in the world.

You can’t fuck up step 1 and complain the rest of the steps aren’t working. I write and maintain a set of ELT jobs and a bunch of front end dashboards. By default, we never run analytics queries in PROD db. I create views and such for the simple queries to run.

I picked up SQL a few years ago for a school project. It took me a week. The DBA stuff just came by itself as I went along. Query optimizations took a while but you don’t need to write every query super optimally. If the DB tables are set up correctly your users will not have to worry about it at all.

My previous comment assumes you guys already have a db set up for analytics where folks can run queries. If you don’t then IDK how the director of IT got their job…That’s very basic shit.

SQL isn’t hard to learn unless they’re asking you guys to do T-SQL and PLSQL.

For simple queries it’s pretty easy.

Twitter’s lawyers argued that the company made only an oral promise that was not a contract, and that Texas law should govern the case, according to Courthouse News, which first reported the ruling.

Are you shitting me? They argued that it was a fucking lie so they shouldn’t be charged? Also no one gives a shit if you’re a Texan company…But you’re doing business in California with California residents, you have to follow California rules. Else don’t do any business in California.

Can’t fucking believe that not honoring an employment contract is not a fucking violation in Texas…Go figure.

So they can’t sue you after the crash cuz no one survives it.

They’ll probably have kamikaze mode for when it detects a crash about to happen it speeds up.

This sounds like an interesting project, what programming language did you use? Was the endpoint relative to the person making the query, how was the data stored?

Haha thanks for the good chuckle

This brings back some nightmares. Once I get them working I never upgrade or even look at them.