Markizano.NET

The messed up part about AI that nobody's talking about is how it slows down senior engineers. While it may be great at "Hello world" and simple algorithms, many times, senior engineers are way past this, and don't really need help building boiler plate code because it just doesn't scale. I find myself more often than not, fighting with AI in some cases rather than using it to write stuff for me that I need done quickly. From custom algorithms or complex situations where scale, multiple contexts or hidden details about how computers and coding works that you don't gain from the RactJS tutorials, even design patterns that are gained from learning other languages cannot be captured and implemented by AI just yet (learn how C and C++ works and then tell me you know how to code properly in JavaScript) to its inability to write in Angular vs ReactJS or even use a different language other than Python for a product solution. We all know JavaScript and Python are not...

Scope creep: When the scope of the project exceeds the original instructions and additional features get added in the sprint. Be mindful of this because its very common in various places. Ways to protect yourself: Document every meeting. Don't just take notes, identify action items, who's responsible for them and a summary of what's expected. I usually email them to the team as well, so I have a paper trail of the discussion to be referred later. Identify the full scope to the best of your ability. What will it take to get started? What will it take to completion? Are there any blockers? Are there any dependencies? Where are the blind spots in the project? Stick to the immediate task of the sprint. I have historically been really bad about this because I want to be able to do everything including deliver the moon! However, when assigned a task for a sprint, its important to stick to the ask at hand to avoid having added responsibility mid-sprint and then being ...

I've had a lot of folks around me say they are jumping from their current careers and wanting to get into IT, but don't know where to start. My advice: JUST START. Just like learning a new language, any new skill is going to take time. There's no perfect entry point. With something and rapidly changing and evolving as IT, you will never find solid ground that will give you a lift off more stable than your own workstation or home lab and whatever documentation you can throw together for yourself. You will be your biggest blocker to learning anything. The very first thing you need to do is Dispel, Dismiss and Disprove is the idea that you are stupid and because you don't have any exposure to this you can't learn it or get to know any of it. Let's get one thing clear: you are smart, intelligent, and you CAN do this. I believe in you. And if you don't believe in you, believe in the me that believes in you! (yes, I totally took that from Gurren Lagan, for...

 YaY! Test pass!!! Photo is from last week. As of last Thursday, I renewed my CompTIA Linux+ Certification As of an hour ago, I'm now AWS Cloud Practitioner Certified! Now to study for the next step in the certification path. AWS Certs I am aiming to complete: - Foundational: AI Practitioner - Associate: SysOps Administrator, Developer, ML Engineer - Specialty: Security, Advanced Networking, Machine Learning Other than AWS, coming soon: more AWS certs, CCNA (Cisco Certification Network Administrator), and CISSP (Certified Information Systems Security Professional) and finishing my Bachelors in InfoSec. Man, being sober is so amazing 🥳🤩 You can see my badges and certs here:  https://www.credly.com/users/mark-e-harris-jr