Yeeeep. I Get Quite Grumpy Whenever I Am Being Told How I Will Use My Pc.

Yeeeep. I get quite grumpy whenever I am being told how I will use my pc.

I will break code and hack shit until it works however I think is reasonable.

And the fact that microsoft tries to resist is just adorable.

“program is preventing shutdown” ..heh… i tried playing nice….. i tried giving you the chance to die on your own terms… but now, you’ve done it. now you’ve Reeeally done it. so here’s what’s going to happen. i’m going to hold down the power button. manually. and i’m going to hold it down for as LONG as it takes…. for you to QUIT. RUNNING. you think youre important? you think your program is.. IMPORTANT?!?? listen to me. no program…. no matter what. no matter how… “important” you THINK you are…. NO. FUCKING. PROGRAM. is ever gonna stop ME from shutting down THIS. COMPUTER.

That where safety matters ( Medical devices, aircraft and so on ) it is a legal requirement that the Quality Assurance department is separate and independent of any other department.

And the reason for that is: "It is the only configuration that works"

What are your thoughts on dedicated testing teams vs testers within the team vs software engineers owning the testing?

Ooooooh! What kind of engineer?

Gday, I’m Emile (she/her)

I’m here to get inspiration and motivate myself to be a better version of me by tracking my progress. It’ll be a weird mix of studyblr, productivity, self improvement, etc.

I’m studying to be an engineer and am based in Australia. Please come have a chat!

I made a crash course about this.

I use this!

Like using the kitchen after I cleaned it, or using a table I cleared to do a project on.

I counter the dumb "But it took efford to get it clean, so I should not use it" thing with "Eh, sucks to be past me. Like I know what that moron did, he can freaking deal with it"

bored of "that's a problem for future me"? try the fresh and dynamic "that's a problem for past me" - consequences shmonsequences, let yesteryou figure it out

SQL nearly always.

SQL is based on relational algebra, meaning you have a mathematical garantee for data validity.

And it is well tested, and many automation tools to do it for you. No-sql sacrifices that. ( Note, any category which starts with "no-" is a badly defined category. Always"

No-SQL really only have a use-case when:

1: Your database is so big it needs to be on multiple servers and cannot be broken down to smaller databases

2: You need the database to sync very quickly within itself.

If both of those are true, then SQL might not be the right choice.

And... 99% of databases do not need this. Unless you are making Facebook, twitter or similar you have no need for this.

No-SQL is mostly a bad choice being pushed by Google and Amazon selling cloud solutions ( "cloud solutions" meaning "You have no right to know anytjing about how we store your users data" ) which is done so the big corporations do not have to put too much work into their services and to keep their users ( developers ) in the dark about what is actually happening.

It is much easier to steal your users data when they have no idea about access and what is stored where. Google SPECIFICALLY writes that they WILL access the data you store on their cloud solutions for "business purposes".

Learn SQL, it is not hard, get a automation program to set up your database on a server you actually control. Which can include renting server space.

That is not only the cheaper and more efficient solution in nearly all cases, it comes with the added benefit of not selling YOUR users out to big corp.

If a corporation say they take good care of your data, and use Google, Amazon or certain Microsoft services... they are lying.

Software engineers, how often do you find you’re using SQL vs NoSQL solutions for your systems?