I Love Being At Work And In A Good Mood.

I love being at work and in a good mood.

Whistling happily as I look up the contact information of work safety authorities so i can hand in my firms insane and careless breaches of basic safety.

The process for setting up hardware that can kill you is: "Whoever can do it. No knowledge or training required. The checklist for what to do is inside the heads of some people in the firm... Probably...maybe, and if those people randomly are near they will tell you what they think they remember they know"

I had a hardware setup that KILLS YOU if you touch the wrong parts. And it had been running FOR A MONTH before someone said "I... seem to remember us being told that the rules say you have to print and fill out a risk assessment and hang it on the safety rail?"

Goodie!

Yes

Its working out quite well so far

(Correct me if I am wrong) That means a mix between mechanical, electronic and software engineering right?

Maybe some business managment and certification procces knowledge?

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!

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?

The word "Mu" can be used as an answer to a question, with the meaning" The question is wrong".

Like, the answer to "is facism a great, or very great idea?" is not " facism is great... since that is the most negative to facism option"

It is mu. The question is invalid.

You develop tech skills the same way you gain any other skill. You use them.

And if you program, that means you most likely work in teams... with people...

Do you know what you develop when you work with people? People skills.

It is not an question with a answer. The answer is not "Both". The answer is "The question is invalid, since it pretends these skills are seperate"

With problem solving being equal, what’s more important for a developer? Tech skills or people skills?