Podcast: Play in new window | Download
Subscribe: Apple Podcasts | Spotify | TuneIn | RSS
Last episode, it might have been said that you can become a senior engineer in just one short year. Our amazing slack community spoke up and had some thoughts on that as well…we revisit that, and what does senior even mean?! Join us for that and much more as Allen plays more with ChatGPT, Michael talks business sense with new customer acquisition costs, and Joe will do just about anything to make troubleshooting an application easier.
See all the show notes at https://www.codingblocks.net/episode213
News
- It’s a little sad, but Stitcher is saying goodbye to the podcasting space
https://apnews.com/article/siriusxm-stitcher-podcast-app-consolidation-4870757590a5386c6c5ae252179cc0df - We revisit the “Can a developer become a senior developer in a year?”
- Huge thank you for the iTunes review from B-Lo7
Topics
- Should you spend valuable developer time writing supplemental applications that can help you understand or diagnose your primary applications quicker?
- Even if you have amazing log viewing capabilities
- Even if you have amazing charting
- Even if you have amazing metrics
- What if all of those things only show you slices of your application but tying everything together is still time-consuming?
- Another visit from the ChatGPT chronicles – this time, using ChatGPT as a way to determine if one technology is better than another – can you fully trust the results, or should you take it upon yourself to do more digging? Allen did a couple of ChatGPT queries – “Which language is better, Java or Go”, and “Which relational database system is better, Microsoft SQL Server or PostgreSQL?” – the results and our thoughts on them may be interesting
- Ever consider “Open Jim” hours at work? Ie – you have an employee that holds all the information and could literally spend 40 hours a week answering other people’s questions, but they need to get work done as well. Is it worth having a set time every day where people can ask “Jim” those questions and the rest of the day they are off-limits so they can handle their own business as well?
- Signing up for online services, or applications on mobile devices, etc. – do you use “Sign in with Google” or “Sign in with Twitter”, etc, or do you sign in with an email rather than using the Oauth2 patterns out there?
- On the flip side, if you were to write your own application and people needed to authenticate, would you enable Oauth2 authentication and why?
With that, as usual we have lots of thoughts on each of these topics so join us for this episode and don’t forget to join the slack community where we inevitably continue the conversation on the #episode-discussion channel!
Tips of the Episode
- Looking for something new to listen to? Check out this Doomgaze playlist. It’s described as “heavy and intense doom drones warpped up in shoegaze layers”. If that sounds like your kinda thing, great! If you’re not familiar with terms like “drone” or “shoegaze” then…even better, you’re in for a treat!
https://open.spotify.com/playlist/3DgEEGi8Vl3SmTdxRhO9Iy - Play an instrument? Create custom backing tracks to learn a particular song.
https://www.karaoke-version.com/ - Test, monitor, and optimize Apache Kafka applications with ease – @Mikerg
https://www.kadeck.com/
