Last time, bro thought he was done talking about organized irresponsibility. Instead, we had a "scrum" at lunch and iterated quickly upon yet more to talk about regarding this.
Discussion of the "organized irresponsibility" in corporations, and how it kills the ability to take risks. How this destroys the ability to find meaning in corporate work.
I did a deep dive into how pasted links turn into previews in chat and social media applications and was pleasantly surprised to find CPAN had the solution for me. I found a couple of gotchas you might want to know about if you don't want to figure this out the hard way.
It took a bit of creative thinking to cram a site that wasn't my brainchild into muh box. Though thankfully it didn't require too much custom fitting and fixes to get the job done.
That said, it could have gone a lot smoother. Discussing that and more!
tCMS is more or less doing what we wanted it to. What's more, it fit into the time we allocated for getting it done! Today we looked back at what we did and where we want to go next with Troglodyne.
From the "I should know better" files. Having predictable user identifiers which are also superfluous is pretty bad, and something I already knew not to do, but hey, worse is better!
Nah, turns out they probably would have saved money and incurred less risk by just outsourcing that concern in the first place. Atlassian is spot on with the marketing here (and we're not even shilling!)
Sometimes management at a firm will codify certain attitudes or practices that employees must hold or follow. Unfortunately, this guarantees inauthenticity. Don't make this mistake unless you want employees to gain cognitive dissonance about your corporate brand.
Like all headlines with a question mark at the end, the answer is (unsurprisingly) NO. Most of the time patents are an excuse to not actually do the work required to get what you need done, instead validating your identity as "an innovator".
Checklists are used often in many industries, but even to this day we still see a disturbing lack of checklisting in software. Don't make this mistake!
This time we come in with an episode that tries to "bring it all back together" regarding things we've been talking about these past few weeks. We cannot stress enough the importance of judging risks and properly estimating expected rewards as it regards success both in software projects and your own life!
