

Good morning to everyone except the developer who thought these two options should go right next to each other.
You have 934 total plans in your cache, with 100.00% plans created in the past 24 hours, 100.00% created in the past 4 hours, and 100.00% created in the past 1 hour.
Shout out to Brent Ozar for his outstanding First Responder Kit.
Hat tip to friend of the Lair Cap’n Quacks for this one. Who would win? A trusted and respected company with thousands of developer training videos, or one loose semi-colon boi.
I’m sure it passed all the unit tests.
//TODO : update the title.
Need to right justify output, safely divide by zero (indoors, even!), or generate random numbers within a specified range? Check out Chad Baldwin’s excellent T-SQL Tuesday #143 – Short code examples.
Thus begins John Mecke’s essay Agile is Dead (So is COBOL, XP, RAD, UML, SAFe, etc). It’s an enjoyable, step by step takedown of the {whatever} Is Dead new paradigm promotion treadmill.
The key takeaway … is that you should experiment to see what works in your environment. Every company is in a unique place at any point in time. Your market position, your level of resources, your ability to execute are all specific to your situation. As Dave Thomas says no rules are universal. What works for Google may not work for you.
You should not abandon things that have worked in the past in favor of some shiny new toy just because they’re old. Edgar Codd’s approach to database normalization works just as well in 2021 as it did in 1972. UML state machine diagrams are still an efficient way of documenting complex designs. Spring planning, daily standups, and retrospectives are still very effective ways to build software. You should synthesize what has worked in your environment with new ideas.
Legacy == Proven
You must be logged in to post a comment.