Inebriated again this week, is it becoming a pattern? Only you can find out by tuning in again this week to the Talking Tech while Poking Smot podcast featuring your host, chad_$yntax. This week we discuss dependencies, and when I say discuss I mean waste the first 5 minutes ranting about some bullshit that I can't even remember. I do eventually start talking about dependencies. How they are important, annoying, somehow complicated and potential vulnerable. We then pivot to retreading some ground from last week about docker, kubernetes and environment variables. Then we quickly move on to a question about "web dev basics" which really sounded like "dev ops basics" to me. We end on a question about databases which I give somewhat of an answer to. I'm not entirely sure I answered the question, but to be fair I am also not entirely sure what the question is asking. Who is to say. Not me. See you next week!

Email me questions on software engineering: query@ttpspodcast.com

If you know your stuff and want to come on the show and chat guest@ttpspodcast.com

If you want to collab or sponsor: business@ttpspodcast.com

Another week with ya boi chad_$yntax bringing you the best software podcast available in a format of exactly 31:33 seconds. No one else can top me at that. I would like to see them try. Other than that, we talked about making bots. Chat bots, twitter bots, discord bots, whatever. It's all about the learning experience. It's good practice and not a bad idea for a side project. Some bots can even make money, like moderation tools or bots with integrations. We then move onto a full-stack question about downloading xcel spreadsheets and the ways in which you can accomplish that. After that thrill ride we move onto an abridged "day in the life" of programming. If I made one of those cringe youtube videos all those other software engineers make it would be boring as hell. People who post those kinds of videos are trying to highlight their neat-o office and social life. All that time you spent recording videos of your snacks at the office could have been spent un-fucking your MR I have to review you fucking dipshit. Enjoy your fucking corn flakes, you better be able to deploy and chew at the same time. Otherwise your shortfall becomes my responsibility, and I fucking hate that. Fucking guy. Where was I... Oh right I have meetings and code every day, see episode 2 for the nitty gritty on scrum and tickets. We then move onto the final boss: koo-burr-net-eez. I kinda stumbled through this one ngl, but I think my general advice still stands. As I'm writing this I'm thinking of better answers. I guess I'll handle my own shortfall next week and re-answer it. Fucking guy.

See you next week!

Email me questions on software engineering: query@ttpspodcast.com

If you know your stuff and want to come on the show and chat guest@ttpspodcast.com

If you want to collab or sponsor: business@ttpspodcast.com

It's me again, Chad $yntax, back again for some good ol' rootin' tootin' SOFTWARE_ENGINEERING. This episode we discuss GraphQL and it's pros and cons. After going over time like usual, we quickly segue gracefully to the modern junior dev stack. What you need to know as a full-stack engineer is usually database, back-end language, back-end framework, front-end language, front-end framework. We then go over some example of such. We then somehow spend the rest of our time talking about front-end performance again. I like front-end performance. I like seeing the little checkmark in the lighthouse be green. I like fast loading pages. I like optimizing. Maybe that's why we talked about it too much this week. There's always next week for more coherent answers!

Email me questions on software engineering: query@ttpspodcast.com

If you know your stuff and want to come on the show and chat guest@ttpspodcast.com

If you want to collab or sponsor: business@ttpspodcast.com

This week I dump on stadia but not necessarily on video game streaming. It's kind of a solid rant without any main points. Like a 4/10 kind of rant. I blame the edibles, I should not have taken the indica ones. We then hard pivot to a classic question of "how would you do it all again" that I regretfully took seriously, but at least I didn't make a whole fucking youtube video about it. We answer a quick question on a utility function without a return in javascript and just as quickly have an existential crisis with the next question on "the sheer volume" of required knowledge. We cap it all off with a question on debugging dev vs. production builds. Those are never fun, I hate those bugs. Half the bloody time it's some asshat recklessly upgrading shit.

Until next time.

Email me questions on software engineering: query@ttpspodcast.com

If you know your stuff and want to come on the show and chat guest@ttpspodcast.com

If you want to collab or sponsor: business@ttpspodcast.com

This week's rant is about the amount of RAM I don't have. Silver lining is that the rant has a purpose: to educate you on the prevalence of our lord and savior, JavaScript. Lots of desktop apps nowadays are powered by the same stuff in the browser, you can't escape JavaScript! We then move onto questions about documentation and what it is and why it is important. We go over certifications and whether or not they are worth getting. Then we go over a not-so-stupid question about deciding css values. Then we move onto programming outside of work and how to avoid burnout. I think the real trick is to know that you will burn out so you can control it. Then again I do have ADD so my brain might work different than yours. SEE YOU NEXT WEEK.

Email me questions on software engineering: query@ttpspodcast.com

If you know your stuff and want to come on the show and chat guest@ttpspodcast.com

If you want to collab or sponsor: business@ttpspodcast.com

For the love of god, just get a password manager already. This time we go into detail on why a password manager is good. After a stark bit of news coming from Uber, we also highlight Social Engineering attacks. Be wary of all fishing! We also highlight how much info someone could access if they had access like we engineers do. There are a lot of internal URLs, tools, and secrets we have access to. So getting hacked is no bueno! We then move onto questions about git branches and how to keep our flow flowin'. We then answer a question about failing at leetcode as a college grad. Sorry to disappoint, but from my experience college is pretty shit at preparing you for programming interviews. Gotta do that on your own, chief. We end with a question about engineering culture. What a week.

Email me questions on software engineering: query@ttpspodcast.com

If you know your stuff and want to come on the show and chat guest@ttpspodcast.com

If you want to collab or sponsor: business@ttpspodcast.com

We explain what a CLI is and how a lot of the processing in our world is done through scripting. You will most likely run into shell if you haven't already. It's used from ops to front-end and it's worth learning. At least the basics. You also get to look cool like a hacker man I guess. We then move onto questions. I finish the second part from last week, "what aspects really get under your skin [of software engineering]?" We then move onto the daily routine for a senior guy like myself and what I remember my routine being like as a junior. Turns out I mostly remember Imposter Syndrome. We cap it all off with a question about MongoDB usage in the year of our lord 2022.

Email me questions on software engineering: query@ttpspodcast.com

If you know your stuff and want to come on the show and chat guest@ttpspodcast.com

If you want to collab or sponsor: business@ttpspodcast.com

Why did I get absolutely blitzed last week? Find out now by using a tactic used by software engineers! We talk about Root Cause Analysis (RCA) and what that means to an incident. If only I could describe the abject terror one feels when receiving a PagerDuty notification. We go over that for quite some time before I finally move my ass on to half-answering a half-question from last week about software as a passion, a.k.a. (SaaP). Logistics brother. Figma is dead. Long live Figma. We then move onto a question about what to learn for being a front-end dev and cap it all off with a question about passion again wow, would you look at that. Two SaaP's in one episode. Perhaps I will elaborate on the things that absolutely KILL my passion next episode...

Happy Listening

Email me questions on software engineering: query@ttpspodcast.com

If you know your stuff and want to come on the show and chat guest@ttpspodcast.com

If you want to collab or sponsor: business@ttpspodcast.com