My 20 Year Career Is Tech Debt

Recorded live on twitch, GET IN
/ theprimeagen
MY MAIN YT CHANNEL: Has well edited engineering videos
/ theprimeagen
Discord
/ discord
Have something for me to read or react to?: / theprimeagenreact

[@edhyjoxenbyl1409]

Technical debt is for people that doesn't use JDSL

[@ea_naseer]

Tom is beyond TECHNICAL DEBT

[@cypercyte7900]

Tom is a genius

[@dickheadrecs]

Tom + JDSL = Pure TECH CREDIT

[@PawelKOtrebski]

everything is deprecated since JDSL was introduced to the world... not only is Tom the GOAT in SE, He's a marketing PHD... even Prime fell for it

[@Dominik-K]

Tom is a genius

[@allalphazerobeta8643]

During my teenage years, I gifted a friend of mine a PC computer magazine from the UK, because I was a Mac enthusiast myself. The magazine came with a CD that contained a full version of Delphi. My friend took it upon himself to learn programming using this language and, to this day, continues to find employment because of it. He even regularly secures contracts with the company his father used to work for, maintaining Delphi projects, he started in his teenage years.. I feel compelled to apologize to anyone who might have been affected by this. At the time, I didn't understand what Delphi was, and honestly, I still don't. I apologize for any confusion or inconvenience this may have caused.

[@BusinessWolf1]

I almost feel bad for these companies that got screwed over by progress offshoots that never led anywhere. Almost, because they're companies so fuck 'em. They can afford the switch over.

[@casperes0912]

Delphi is more of an environment. The language is a Pascal dialect. I believe it's Turbo Pascal but it might be Object Pascal, I can't quite remember

[@NoX-512]

@@casperes0912I’m pretty sure it predates object pascal, but don’t quote me on that. I was never a fan of pascal.

[@colemanroberts1102]

Delphi is a dialect of object Pascal, per wikipedia.

[@johanloubser8138]

I graduated High School last year, we literally learned programming on the latest version of Delhpi

[@Silencer1337]

Life's not about the code we write, it's about the bugs we fix along the way.

[@CallousCoder]

Then my life is void. I hardly ever have bugs when I release my code, it’s called proper testing 😂

[@Hobbes9]

@@CallousCoder sure bud

[@CallousCoder]

@@Hobbes9 Nobody’s perfect, “hi my name is nobody” 🤪

[@peterheijstek5288]

Good code doesn't create good stories, but weird bugs do

[@oleg4966]

What matters is not the languages you've used, but the shit you've seen.

[@jordanrozum]

My first job (~2011) involved converting some Fortran code to MATLAB & integrating it into a scientific data processing pipeline. The code was written to process atmospheric data gathered from rocket experiments in the 60s. Someone had already moved the code from punch cards to text files, so at least I didn't have to do that part. Eventually I had to convert it to handle the same kind of data but gathered from satellites (which mostly means doing some geometry to account for the different perspective). It was technical debt on two levels. And of course, when they hired me, the only language I knew was C++, so they plopped some Fortran and MATLAB textbooks on my desk and said "figure it out, good luck". That was how I learned the value of writing good documentation for your code... if only the people who wrote that rocket code half a century earlier had learned the same lesson.

[@monad_tcp]

and nowadays developer. mimimi I don't know this programming language, even worse, I can only program in "React". (beating the dead horse)

[@henrikholst7490]

Fortran is still going to be around long after React has been dead and buried with the Action script Ratatouille

[@muhwyndham]

And somehow "your code is your documentation" folks still exist.

[@timgwallis]

Corporate America has twisted the term MVP into something unrecognizable. It has nothing to do with the MVP in the startup world, which is where the term comes from. If you’re working on something that takes 50 engineers and six months to deliver, in no world is that an “MVP”. Edit: Voice to speech typos

[@CallousCoder]

So true! Minimal Viable Product is something different from Quick hacked together crap.

[@Fernando-ry5qt]

For me MVP will always be "It barely fucking breaths", nothing will change my mind haha

[@monad_tcp]

@@CallousCoder a product is usually deliverable to the client , anything else is a prototype

[@CallousCoder]

@@monad_tcp I only work for clients.

[@r_j_p_]

I used to believe this but now I think the mainframe COBOL programmers secretly get together at the clubhouse and laugh at the rest of us trying to keep up on the tech hamster wheel. "Look at those kids run!"

[@garanceadrosehn9691]

It may be a cozy clubhouse, but on the other hand, the number of people in that clubhouse is much *much* smaller than there were COBOL programmers back when I started (1980).

[@monad_tcp]

After LISP was invented, nothing else is of relevance, and nothing new under the sun is worth enough.

[@Rakkoonn]

My dad worked on the same codebase at the same company for his entire career in COBOL. That's almost unthinkable in modern tech.

[@Chemnitz11]

I'm watching this video from the clubhouse, today.

[@DeusGladiorum]

Fun fact: the Brits at my job pronounce “deprecated” as “depreciated” and I’ve had multiple, agonizing conversations with them about how this is not a difference of accent

[@dandogamer]

No one cares

[@DeusGladiorum]

@@dandogamer Don’t say that, man. Someone _does_ care about you. I promise.

[@method341]

My colleague at work does this and I don't want to be the guy that points out he's been using a financial term all this time. And we have the same accent so he's saying the wrong word for sure.

[@AM-jx3zf]

Those are two different words. I'm sure they mean depreciated, as in, not appreciated anymore 😂

[@digibrett]

DID netflix originally use Silverlight... For some reason Im remembering that it used Silverlight.

[@ea_naseer]

Now that I think about it academic books usually treat change in software engineering as change in requirements but none of them to my knowledge treat change in terms of change in design, change in architecture which would be valuable insight into technical debt. Like most of them will say if you want to deal with change go agile.

[@NoX-512]

I worked for a railroad company 25 years ago. Mainframes and Cobol. I’m pretty sure some of my code is still alive. Luckily for me, it’s someone elses technical debt now 😂.

[@codeman99-dev]

What was that like? How quickly did you consider your own code tech debt? At release? At merge? At push? At commit? At stage? First run? When first typed? Before it even left your brain?

[@NoX-512]

@@codeman99-dev 80% of the job was writing simple batch programs. Pretty boring stuff. 'Technical debt' wasn't a thing, at least not in my country, so I didn't consider it at all.

[@joejazdzewski]

My Dad was at Borland and developed Delphi. He still has the box of discs from the 90s

[@kippie80]

@ThePrimeTime, this may blow your mind ... I've been working in a tech space that has been 'grandfathered' by Microsoft and has not changed in 23 years. I'm talking about Axapta's language 'X++' which was leading ERP tech in 2000 (the days of ColdFusion) and it has not changed since (speaking of the core language). MS has updated the compiler to basically be a pre-parser to #CIL byte code but the language itself has not (and I expect never will) be updated as the customer base has all its tech and processes invested in it. This platform is the #1 selling of ERP platforms. (SAP is still the biggest but not in terms of new deployments)

[@thingsiplay]

The Visionary CTO needs to team up with Tom is a genius and create a startup named "Visionary Genius".

[@OBGynKenobi]

I think the problem is this agile way of working. I sometimes go 6 mi this without writing a line of code. I used to be an awesome C# developer, now I've forgotten most of it. We're just always jumping from one tho to the next. You can only hope on keeping your knowledge of the basics, loops, data structures, control flow. If you know those three things you'll get by.

[@wdavid3116]

There are tech stacks that last however. Large established tech stacks last for decades using programming languages that have been around for even longer. There are companies that are still using google's old GWT toolkit to code web apps in pure java and transpile javascript front ends out of it. You just hire developers and train them on the tools you use. A decent developer can pick up the basics of a framework or language very very quickly certainly within a 6 month probationary period. The thing is when you do this your company needs to dedicate the resources to keeping the tools you need alive by contributing to open source projects and picking things that aren't short lived and driven by hype.

[@marcodoe4690]

Interesting article. Management in the company I work for should read that.. i had the most horrible developer experience and i am glad i switched into architecture consulting within that company. It's amazing how much product owners cling to old stacks because they don't want to fund refactoring and you as developer have to build skyscrapers on a swamp without draining it first.

[@ChillAutos]

Ive found this the further I get in my career the less I care about the code and thats not a bad thing. I still care that its readable. I still care if its maintainable. But I don't care about it being perfect. Perfect really is the enemy of good and sometimes you just need to get some shit on the page and call it a day.

[@mattburgess5697]

Same. Solve the problem you have now. Don’t try to solve everything forever.

[@rct999]

I know a company that still uses the same ms-dos inventory system. It was created by the owner, and it's rock solid. Employees that are familiar with it can operate it faster than most UI's today can render and no user has ever found any bugs in it (at least in the last 20 years that I know of).

[@peppybocan]

See, 90% of these technologies are Web based tools, libraries, and Frameworks. If you learn Java, C, C++, Rust and you don't really give a f*ck, then you don't have to deal with this shit.

[@ea_naseer]

I have read Reddit articles where c++ code written by the old team could not be read by the new team so they tried to rewrite it then said eff it and wrote it in Java.

[@peppybocan]

@@ea_naseer sure, but that's just a shitty programmers making mess. It's still the same technology. This article was mostly focused on web-based stuff that changes every 5-7 years or so.

[@adambickford8720]

Yeah... no. Java 8 is *nothing* like java < 8. Nobody mutates in place anymore, even in the core APIs. How's that corba package doing? Have you tried the `Flow` api i.e. reactive programming? You can't write a meaningful app without 100+ annotations. Hell, we aren't even WORA/JIT these days! Java is *nothing* like it was 20 years ago.

[@f0lderfile]

@@adambickford8720 wait, are you saying, java is good now? 😮

[@peppybocan]

@@adambickford8720 sure, but it's still Java. Yes, it may need rewrite, but the syntax and the core of the language is the same.

[@darkarie]

My first job as a software dev was 2 years ago doing crawlers with Perl in a 10 yo company, and I learned a loooot. The last month I even did son CI and deployment stuff too on their custom servers, no AWS, all in housework. Now I am working in a bigger company using Typescript and Ruby for the BE, and a lot of the knowledge that I got from my first job is valuable for my colleagues. Really thankful for that year working with some real software wizards haha

[@nubius]

When you said that IE6 and Netscape dev on a resume still meant something to you, you melted my heart a bit. Thank you for handing me a walker, and bless your heart deary~ Most of the time people DGAF about us, but some folks still do I guess.

[@klaudyw3]

We've got some VB as well. It's one of those things that still does what it's supposed to and we haven't had to really touch it in the recent decade. As soon as more serious change requests come up it's gonna 1. become someone's life for a couple weeks or 2. get replaced.

[@TehPwnerer]

"Given enough time, all your code will get deleted." is another way of saying; on a long enough time scale, your survival rate approaches 0.

[@jeremiedubuis5058]

This is only one part of what technical debt is. Most often, technical debt is what you get when you take shortcuts to meet business deadlines. Technical debt is often when you are writing bad code in the current context, this is a tradeoff for speed to market, for laziness, for lack of manpower and yeah sometimes for lack of updates. Technical debt is also often just shit code you are stuck with.

[@garanceadrosehn9691]

It's true that so many projects which we expect to live forever will actually die within 5-7 years. And yet at the same time there are other projects which will last *much* longer than ever envisioned. In the last month I've had three different projects rear their head, each of which: (1) was first written 18-25 years ago, (2) was meant as a short-term solution, (3) has worked fine multiple times per month without any incident for at least 10 years, (4) had small bugs which suddenly demanded at least four hours of debugging to track down right now, because those bugs were a critical roadblock to some currently-urgent project.

[@garanceadrosehn9691]

I can't seem to get a nice terse way to say point #3. Let me re-word it to say that these programs have worked fine for their entire life (even though they have run multiple times per month), including the fact that the most recent problem for any of these three projects was more than 10 years ago. They have been very reliable for many years -- until they failed in a major way. One of them it took me over an hour just to remember how it was built because it has been so long since the last time any changes were made to it.

[@dylanm1216]

I regularly tell my staff "don't get too attached, eventually your baby will be thrown into the dumpster."

[@32zim32]

Yeah. Sometimes I wish to be a doctor. High salaries. Organs doesn't change over millions of years. No MVPs

[@gracefool]

Unfortunately those salaries are based not on knowledge of the human body, but on knowledge of pharmaceuticals and paperwork, and both have incentive to change often. Healthcare is dominated by government and Big Pharma.

[@32zim32]

@@gracefool Seems like this world is broken and we need another one

[@johanloubser8138]

I'm currently 19. I had IT classes in high school... The government said we had to learn programming with Delphi, so I suppose I'm already in technical debt

[@jazzochannel]

Delphi is not that bad.

[@johanloubser8138]

@jazzochannel I mean, I like it. I'm doing Advent of Code with it and Python

[@Mossad84]

If you move to the fashion industrial, you would be surprised that the clothes you design today, nobody wants to wear it 6 months later. We also call it Design Debt.

[@Jason-eo7xo]

3 decades as web/mobile full-stack developer. NEVER EVER STOP LEARNING AND GROWING! Don't even get me started on IE 6. Netscape was the shit. I LOVED Netscape. My first programming language was ColdFusion 1999. It was really great back then. I was doing full-stack before it had a name.

[@SitchBlapped]

I feel this video in the depths of my soul lol. I spent the last 10 years designing and developing RPGLE apps... the pain is real

[@jespergustafsson7664]

I suspect that the Flash thing you were thinking of is Ruffle. It's a pretty cool project :>

[@asherrfacee]

Your accomplishments become your technical debt. The longer you stay at a company the more debt you accumulate. A good engineer makes decisions that reduce their future maintenance costs and therefore enables them to continue to make progress on new work without being hindered by having to maintain old work. If you’ve made a lot of mistake and your technical debt is too high there is a big incentive to abandoned ship and switch companies. I think an engineer who stays at a company for a long time and stays productive is a champion.

[@Harold046]

Most code becomes obsolete in a matter of years. It's one of the reasons why I'm using C++ as my main langage. Everything decays slower in C++. I've got Qt code that's 10-15 years old and that's still relevant today.

[@kyuss789]

React native still uses objective-C for the native layer and I can with confidence say that it is indeed tech debt. I cry everytime I need to touch it

[@TheNewton]

This is long way to explain the importance of internals being made into technical documentation , codifying specifications , edge cases, the domain knowledge and underlying standards.

[@joestevenson5568]

C devs are laughing at us whilst their code from the 80s remains unchanged.

[@neildutoit5177]

I have one of my dad's old asp textbooks. It's more than 1000 pages long. And it's only of of 9 in the series. Imagine reading a 1000 page book on a Javascript framework. By the time you're done noone would even remember that the framework still exists there will have been so many replacements. Nuts.

[@bkucenski]

Technical debt is what impacts today's work. If it doesn't impact what you're doing today it's not debt.

[@wywarren]

Telling people you make sites compatible with IE6 and Netscape should be the new interview flex.

[@calder-ty]

Pretty much everything the article states is not something I'd consider tech debt. Tech debt is the stuff that ought to be fixed or replaced as soon as it is made. It's a tradeoff for time now vs later. Writing code in the latest version of your language isn't tech debt because eventually the version gets superseded. That's upkeep.

[@moonasha]

man I started really programming with flash, specifically actionscript 3. Before that it was BASIC on a calculator. It was pretty sad to see flash die like it did, I spent a lot of time making games for it

[@Robert-ht5kd]

Silverlight is called WASM now :) Why it failed? Becasue it was made by Microsoft. Why WASM is good? Because it wasn't made by Microsoft :)

[@hardcorecode]

Awesome.... I love how you make dry topics so exciting!

[@jazzochannel]

I don't touch garbage that's likely to disappear. Started with GNU/Linux and bash in 2001, still here. Started with PHP in 2006, still here. Started with HTML and CSS in 2006, still here. Started with go in 2020, still here. Started with JS in 2009, still here.

[@SimGunther]

If your engineering career doesn't increase entropy in the universe, than your contributions in that industry were a moot point and you should think about doing something else like basket weaving.

[@m4rt_]

14:50 At my work we use Salesforce. For some reason Salesforce loves SOAP. I hate SOAP.

[@7th_CAV_Trooper]

The first time I encountered client certificates was with a soap wcf project. This project produced my most up-voted stackoverflow question. Lol

[@japonskibrulionik7729]

Eventually we'll all be dead. Recently I came to a project, which had huge monolithic components, absolutely no reusable components, no tests, to testable functions.... Everything was technical debts, and the project was just 4 months old.

[@nightshade427]

You laugh, but asp web forms and server side controls is same aritecture and approach as react server components and server actions. What is old is new. We even had update panels that interacted with server controls to give us async components, and this was in 2005.

[@oleg4966]

14:45 "I'm just like every good Arch user: I've never used SOAP." Brilliant.

[@bkucenski]

I have code I started in PHP 5.3. It upgraded to PHP 8 just fine. If your PHP code is greatly impacted by major code revisions, it's because you wrote code badly because you did what you were allowed to do rather than use good coding practices because you're supposed to. Bootstrap is an example of when if you do things the correct way, you're screwed when it comes to the new version because they completely changed things.

[@ruukinen]

Agreed. Every time I had to refactor something where I was working to upgrade the PHP version it was always because that code was rotten to begin with.

[@TehKarmalizer]

That’s easy to say in hindsight, but it isn’t always apparent what will be the correct way looking forward. Sometimes changes are just breaking.

[@bkucenski]

@@TehKarmalizer best practices haven't changed in decades

[@TehKarmalizer]

@@bkucenski I can’t speak for PHP, but C# and C++ have both evolved best practices as better language features have developed.

[@bkucenski]

@@TehKarmalizer they still use classes and don't promote spaghetti code

[@arthurbh]

Basically the guy invested all his time and energy in the latest webdev fad and cant accept that things die. Learnt C 20years ago, still using it today, still relevant, looking forward to the next language that can work in baremetal apps

[@AndrewBrownK]

hard to argue against C in this context

[@chri5toph_k]

Why do you think, he can't accept it? I see a critical reflection about his past work, but not regret. I learnt JEE in school and how to build websites with JSF and even stuff like CORBA. Was it unnecessary for today's world? yes. Do I feel bad that I had to deal with this stuff? no. Currently I develop stuff with Java, Spring Boot and Angular and I know for a fact, that these applications will be deprecated at some point and that I will be working with completely different technologies. Every language and framework tackles problems in their own way. It's the concepts you learn on the way, which make this work rewarding in the long term.

[@JorgetePanete]

ah yes, still relevant for accidentally making malware

[@arthurbh]

@@chri5toph_k Agree with you, but I do think this article is just lamentation and being salty. Every code is deprecated one day, doesn't mean it was bad code or wasn't fun to make

[@arthurbh]

@@JorgetePanete K

[@complexity5545]

SOAP was the devil. You had to pay whatever company for their official $1_000 SOAP library because there were edge cases where SOAP with balk and need one-offs to fix. SOAP is a tech that has bugs inherently designed in it. This article is like a timeline for the last 20 years and raises the question of why are we doing so much useless and vain technology changes?

[@michaelslattery3050]

When picking books to read, I prefer learning something that still might be applicable in 15 years. Soft skills, CS topics, Linux/Unix, how parsers work, etc.

[@realtimberstalker]

My father used to write apps in FoxPro for his business but then migrated to c#. I, by complete coincidence, not only learned c#, but it also became my favorite language, so I work for him now.

[@hinzster]

When Delphi came out I had already quit programming in Turbo Pascal. Wait, what? :P No, seriously, I have in my time learned to program in Basic and 6502 assembler, switched to Z80 and Turbo Pascal, PC was actually my third programming platform (bought me an Atari ST for my first wages programming on *ack spit* PC in Turbo Pascal and *ack spit* Clipper - if you remember what that is you are dating yourself just as I am). But like my two aborted IT bachelors I still find use for the stuff I did back then. Pascal tought me to be structured also in organizing my code, assembler (6502, Z80, 68k, even IBM /370, but never x86, because I'm not a masochist) tought me how computers work deep down below, and SQL is relevant even today (because, boys and girls, NoSQL means NOT ONLY SQL :) ). I still program in C and Python (yes, also Django, nevermind what the kids these days use) because what I code somewhat doesn't matter, as I am not a pgrammer by profession. My contribution to some elisp-code for Emacs back in the 90s though... definitely technical debt :)

[@cherubin7th]

I remember using Fortran for nuclear physics research in 2015.

[@mattburgess5697]

I come up on 25 years as a dev this year. I think he’s wrong. The stuff he’s used and learned isn’t wasted. It’s context. He has a breadth of experience and confidence in his skills that comes from it. He’s also IMO wrongly equating the terms “technical debt” and “legacy”. I can see the connection, but I don’t see them as synonyms. A legacy app can stay forever as a legacy app. Maybe it gets a rewrite, maybe it doesn’t.

[@olafbaeyens8955]

I know Delphi but hide it on my resume otherwise I never get a decent job ever in my life. I once made the mistake to go back to Delphi after C#, but took me hell of a time to get a chance to go to C# again.

[@NotAFanMan88]

11:20 this hurts my soul... considering we have apps written in this that we still have to maintain until the business gets a clue we need to trash them and prioritize.

[@robfielding8566]

As Linus will tell you: It's the data structures that you need to worry about; instead of the code. The data structures persisted to disk will last forever. The code changes continually.

[@olafbaeyens8955]

If you talk about Delphi then you must also mention "Kylix" ;-)

[@SuperHeroINTJ]

And Lazarus, which I was a contributor to. The beautiful Lazarus splash screen was my creation. 😛

[@oconuco]

I started programming at IBM with Assembler doing memory paging in mainframes. And after C, Fortran, Pascal, Prolog, C++, Java, C#, now I'm on Go and Rust. Started the year after the school took the punch cards away... 🙂 Some of that Assembler code still running.

[@rashshawn779]

1. Companies/Corporate deprecates platforms and technologies. 2. People want to adopt widely felt standard than niche implementation. 3. Things get out of favour because of popularity and demand from the job market.

[@josevargas686]

I am sure you would agree that quiet quitting is fine as long as you use the extra time to crush it at something else, like looking for the next gig

[@RealRatchet]

I had to use SOAP in uni, the setup alone was a chore and so many things used to go wrong.

[@pepkin88]

19:57 Unless it has some "temporary change" comments in it - then it stays forever.

[@aLpenbog]

Meanwhile I'm working with 20+ year old PL/SQL code and freaking IE 5.5 compatible web applications because some of our clients are still using 300 MHz Windows CE mobile handheld computers. Windows XP, Windows Server 2003, SOAP, XML. Businesses have a lot of old shit running and if that is tied to expensive hardware and that still works they don't see any need to change. Why get 50 new mobile handheld computers for 100k and get a retrofit for the application if the old stuff is still running? Get a new pallet stacker crane for millions of bucks because the IPC is still using Windows XP? Not going to happen unless it breaks.

[@mllenessmarie]

"I though the ColdFusion was a KZbin channel" Jesus, that's too good...

[@carlsmith8593]

I'm using Swift for terminal apps (no Xcode, Playgrounds or SwiftUI involved). I luvit!

[@laughingvampire7555]

I did web apps with VB6, ASP, IE6. I also used SOAP with web services written in java

[@johnychinese]

The name is the Tomagen

[@NoX-512]

Tomagenius

[@GeorgijTovarsen]

Why people keep saying Ocaml has traits? Modules are very different from traits, maybe even more flexible, but less convenient (it shows even when using basic "traits" like Order, Equal, Show and such). I know Haskell has a bad reputation, but if you want traits outside of Rust, you are stuck with things like Haskell and its clones (eg purescript)

[@kobibr9362]

Anything in versions past 2 years might just go from technical debt to security vulnerability.

[@melski9205]

The Harmon browser is still available for those who still want to use Flash. For all those 'enterprise' apps that no one can be bothered to port.

[@adamblade9156]

Can someone explain the joke with JDSL and Tom, i don't quite get it ?

[@mrdrsir3781]

Needed that advice for beginner programmers. Just make more things, don’t make it perfect, make small iterative improvements over time. Got it chief

[@tsukinoko_kun]

I recently worked for a company that built new software that used SOAP in 2022

[@inertia_dagger]

All your code will be lost to time, like tears in rain

[@Nickname863]

VB6 my beloved. I will never miss you. And that poor sod also had to do Foxpro? Yikes. Also active X sucked. I spend days messing around in the registry because of some dumb dependencies that got registered and deleted and not unregistered.

[@gustavoaguilar7999]

So people think their code will run forever?

[@tylerkropp4380]

OK now we should look at the people who write legacy code in real-time.

[@xregularxjohnx]

i believe it was The Buddha who said, "There is no enduring software"

[@firstlast-tf3fq]

My entire job right now is ripping apart and modernising a webforms monstrosity with a team of 8 Devs while the rest of the company keeps adding features to it...

[@gosnooky]

This is literally me right now. PHP from 2003, Perl from 1995. At least I'm paid well.

[@embedded_software]

Screw protobufs. If you have any sort of memory unsafety in an application that uses protobufs, that application can fail in extremely surprising ways

[@LoftwahTheBeatsmiff]

I set up ASP Nuke using ASP and MS Access for the database on my Windows 98 system.

[@BPTtech]

VinBuddy was probably an homage to BonziBuddy? I feel there was another xBuddy in early 2000s

[@JohnNotation]

Prime talking about C++ as I am currently learning it. 😎

[@bradleymorris161]

Delphi. Whooo boy that brought back some bad memories.

[@kellyrankin8844]

C++ is getting harder to hire for ...for many reasons, one of which is elitism and fear of outsiders bringing new perspectives that don't jive exactly with orthodoxy.

[@johnheilman818]

Note to self: consider making blazor the final programming language just to eff with the haters.

[@mohamedyamani8502]

Great video as always :D I'd appreciate it if you could link the articles you read in the description.

[@verraneventide]

I have seen some sh*t. Approaching 30 year full stack career anniversary.

[@dagadbm]

why dont you show the article link in the description?

[@filthyfrankblack4067]

5:27 "I know C++ is getting harder and harder to hire for" Damn you Snek!! (python)

[@StarOnCheek]

The T in CTO stands for Tom

[@cloudenvying]

look upon my works ye mighty and despair

[@sprytnychomik]

How do you call reusable C++ code? A code smell.