I Am Low Level Engineer. As Such I Am NEVER Let ANYWHERE Near A Costumer Or ANY Decision That Involves

I am low level engineer. As such I am NEVER let ANYWHERE near a costumer or ANY decision that involves "How do you feel people should use computers?". I am a low level engineer. When you ask us such questions, answers like "Working in the shell is most of the time nicer than a GUI" or "No I DO think forcing the consumer to insert the settings for their automatic curtains in a hex code they generate based on several tables in the manual is a reasonable way for this system to work". So AS a low level engineer, I can only say... yep, put it up to 12. I once used one to melt tin and used it to solder with, and I am sure many users will face simillar needs of their toasters since that is completly reasonable behavior.

Oh this is GREAT. I am a big fan of diagrams to get a grasp of what is happening with code (Learning to make UML diagrams was the best supporting skill for learning and communicating code for me) :D People learning git for the first time often have trouble with what the local and remote repository is, what the difference is and which is which. Also, first and most important git command everyone should learn: git status It tells you what git thinks is where. It is THE command for starting to use, and learn, git.

Git cheat sheet guys 😉

Git is a powerful version control system widely used in software development to manage source code and track changes. Whether you're a beginner or an experienced developer, having a handy cheat sheet can be incredibly useful to quickly reference common Git commands and workflows. Here's a comprehensive Git cheat sheet to help you navigate through various Git operations:

🌐 www.certhippo.com 📧 info@certhippo.com 📱 https://wa.me/+13029562015 ☎️ +1 302 956 2015

Vocalization of your thoughts can help you solve problems. In the same way that writing them up or making a diagram of the problem can help you fix it. Try tricks people recomend, and if they work for you. Great! Use them! Here is my duck by the way :3

He is so sassy!

Source For more posts like this, CLICK HERE to follow Ultrafacts

Going to make a "Getting started with GIT" Post

(This is my getting the "why are you making that post" out of the way, so that the posts with the actual information does not get polluted by it. And also polling people on what they find confusing about GIT so I can target that a bit better) So I re-blogged a post with a really nice GIT diagram, showing what commands sends what where. And I noticed 3 things in the replies and reblog. 1: A lot of people seem to be intimidated by the perceived complexity of GIT. That is fair. But I promise, while HOW it works is complicated, using it is not. 2: Many have it on a TODO list for after they learn to code. Which is... backwards. It would be like waiting with learning how to use a keyboard until after you have become a good writer. Trust me, learning GIT as one of the first things will make it EASIER to learn to code. 3: Several people suggested that GIT is overcomplicated. That is... simply not true. It is one of the old school pieces of software (Meaning it does 1 thing, is open-source, free and is impossible to monetize). It does something very very complicated in the simplest way possible. I think people simply do not understand how complicated the problem GIT solves is. I am not saying "People are dumb" (I think... anyone thinking that is fundamentally missing something in how the world works.), I am saying "People seem to be either misinformed or not informed". And that I can help with!

I WILL make a "Getting started with GIT" Post, but if people want an easy explanation for something more, then I will also make posts for those later... Or maybe they fit in as part of a getting started post. We shall see

C++ SUPPORTS object oriented programming. It also supports Procedural and Functional programming. ( A fair criticism of C++ is that because it can do everything, it is also very complex. Often using a more focused language is simpler and better for a task )

You can ( And really should ) mix and match programming paradigms. Using the right tool for the right job and all that :)

OMG ALL THIS TIME I'VE BEEN DABBLING IN CODE AND ONLY NOW I UNDERSTAND WHAT OBJECT-ORIENTED PROGRAMMING ACTUALLY MEANSSSS (honestly I've been scared to learn C for the loooonnngest time and I've only now used it for cs50... it's actually REALLY good for comparing/contrasting with modern languages...like even C++ which looks very similar to C syntax is apparently an object-oriented programming language?? and you have dictionaries so you don't have to make your own hash tables???? those are HUUUUUGGGEEE upgrades imo [i still don't really understand hash functions tbh...])

This is... horrifyingly accurate....

Going from being an introverted lurker on reddit to trying to post my own stuff here is so wild. I keep typing out a post, deleting it, then retyping because I think it's not good enough but then I look at other posts and why am I so worried?

It's like I'm at a fancy Italian restaurant and keep glancing around the room to see which hand people use to pick up the forks. But then I realize that everyone is shoveling spaghetti into their mouths using their bare hands and I'm like ah okay so I'm clearly overthinking this