Nothing is quite as sobering as a pagerduty alert on a quiet evening. We talk about the alerting process for software engineers and dealing with production outages. It feels nice to be needed, but when I am needed I end up reading a lot of logs. I then make a hard right turn to describe the effects of chronic marijuana use and addiction. It's a bit of a ramble, I'll admit, but you should be warned that you stop having dreams. It's kinda nutty when you stop smoking weed because you get an influx of dreams and they are kinda strong.

Then we answer some questions about good habits for development and collaborating with others. I put about 20 dollars in the swear jar answering a question about using paper when writing code. Stupid. I kinda run out of time because I want to talk more about "the edge" since it was a good question. There are a lot of SaaS companies popping up offering edge computing. Even Deno is doing it. But at least I define what "the edge" is. 

Email me questions on software engineering: [email protected]

If you know your stuff and want to come on the show and chat [email protected]

If you want to collab or sponsor: [email protected]

Might have had a bit too much of the ol' giggle smoke this time, but we press on nonetheless. We talk about games like Factorio or Satisfactory and how they are similar in gameplay to standing up software systems. Then I do a quiiick rant on the idea of logging right before I effortlessly segue into questions. We start with a little bit of career advice and the different paths one could take. We then jump into imposter syndrome where my best idea of advice is like "just 4get 4head". All you can really do is be the sponge. We then cap it all off with me trying my best to articulate the traditional workflow of writing software for a product. Now that I'm more sober I have this list, lol:

So yeah, pretty similar to what the question had, just with different terms and a few extra steps.

And remember! Always pet the lizard doggo.

Email me questions on software engineering: [email protected]

If you know your stuff and want to come on the show and chat [email protected]

If you want to collab or sponsor: [email protected]

A.k.a. get canned, laid off, sun-setted, separated, the boot, the pink slip, and getting fired. These are all synonymous with a "reduction in force", the most corporate way to put it. In this episode we talk about it. I give my perspective as someone who has seen this phenomenon more than once. Hopefully you can glean some wisdom from my experience. We then talk about becoming an "expert in a field" and my love/hate relationship with elasticsearch. I then shout into the void about how great "just building and iterating" is. Like anyone has had "building and iterating" for dinner before. I ended up learning a whole bunch about opensearch after this episode.

We then answer a few questions about learning cloud, and JIRA cards. God I love JIRA cards. They are so great with all of those fields that no one uses. They take so long to load it gives me time to take a piss. Really keeps a cadence to my morning.

If you know your stuff and want to come on the show and chat [email protected]

If you want to collab or sponsor: [email protected]

I ramble a bit whilst high on the potenuse about Big O notation. It's good to understand so go google it. In fact, I'll do it for you, click here. Basically means you should understand the amount of times your code may run. Bigger n is bigger problem. We then make a very smooth transition to the importance of walking. Or really any mindless process to help your brain think through your current problem. We then take a hard right to talk about the known unknown matrix. Scary stuff. We then finish the episode off with a couple of questions. "Why do developers use macbooks?", and "how valuable is leet code to web devs?".

Email me questions on software engineering: [email protected]

If you know your stuff and want to come on the show and chat [email protected]

If you want to collab or sponsor: [email protected]

I sort of bitch and moan about front-end testing and how I think it sucks ass. In my defense, I have some pretty strong points. If you are a front-end testing wizard scoffing at my notions, feel free to hit me up and tell me all about it. Portfolio websites come up a few times and we talk about the job struggle. We then talk a bit about diagrams and why they are important to framing your mind as an engineer. Ever have to navigate a massive repo to add something just to satisfy the ticket? I have! I talk a bit about some tricks to navigate a big repo and find the right place to edit the code. We cap it all off with another question about portfolio websites and the virtues of being your own boss.

Email me questions on software engineering: [email protected]

If you know your stuff and want to come on the show and chat [email protected]

If you want to collab or sponsor: [email protected]

This one is a doozy, I try my best to describe the concept of "jobs". No not the apple founder. Also no, not the means of exchanging labor for currency. I'm talking about computing jobs aka asynchronous processes. So uh, buckle in. We then talk a bit about optimizing images and videos on websites and how webp is the go to format. (Even though I'm a lazy pile and didn't convert my own dang images on my site) Ever wonder why Netflix works so well streaming video but your local news website can't stream video for shit? Well it turns out scaling video is super not easy and you probably need to outsource it to a firm like mux or cloudinary. We then discuss the ever important meta tags and the even importanter og tags. Then we cap the whole thing off with a hilarious thread I stumbled upon that made me question my own sanity. But hey, what's life without a shot of imposter syndrome every once in a while?

If you know your stuff and want to come on the show and chat [email protected]

If you want to collab or sponsor: [email protected]

I poo-poo on web3 a bit and describe the process of putting ttpspodcast.com on the blockchain. Visit chadsyntax.eth in your browser, today! (Spoiler: it was not cheap, but I guess it would be cheaper now since... you know... 📉📉📉📉📉) We chat about kubernetes (aka k8s) for just a bit, then discuss what and why is monorepo. We cap it off with answering a css question.

If you know your stuff and want to come on the show and chat [email protected]

If you want to collab or sponsor: [email protected]

I just love the lowercase greek L. λλλλλλλλλλλλλ. We discuss serverless, a cloud computing model or also known as the hip new way to run servers and (might) save you money? It's also a framework. We then go on a long description about the interview process I've seen as an engineer the last time I was out 'n about for a new gig. It sucks but hey, what can you do? We cap it off with a question on micro service ideas.

If you know your stuff and want to come on the show and chat [email protected]

If you want to collab or sponsor: [email protected]

In this episode we just take a big fat dump on the trash software known Internet Explorer, otherwise known as IE, the worst browser, the slow one, and "el navegador del diablo". In hindsight it used to be the king. The U.S. government wouldn't have sued michaelsoft otherwise. Remember when the government broke up monopolies? Anyway, we pour one out for the homie: Atom aka the og RAM eater and father of all the RAM eating desktop apps we all know and love today. We do a quick review of harvard cs50 on youtube, make sure to check that out.

If you know your stuff and want to come on the show and chat [email protected]

In this episode we go over SCRUM, or AGILE, or whatever you want to call it. In my 10 years of working this has been the general gist of getting shit done on paper. If you have more in-depth knowledge about these kind of workflows or have a different experience, feel free to email me about it, I would love to learn what others are doing differently.

If you know your stuff and want to come on the show and chat [email protected]