It's All Boxes? Always Has Been.

Content my linkedin profile R, python, javascript, shiny, dplyr, purrr, ditto, ggplot, d3, canvas, spark, sawk, pyspark, sparkly, lodash, lazy, bootstrap, jupyter, vulpix, git, flask, numpy, pandas, feebas, scikit, pm, bayes, h2o.ai, sparkling-water, tensorflow, keras, onyx, ekans, hadoop, scala, unity, metapod, gc, cllc, krebase, neoj, hadoop. I typically ask recruiters to point out which of these are pokemon.

Content DevOps Dan scripticles 000 Doing triage on a web page on my localhost. Every time I try to load the page, it just hangs for five, ten, twenty, thirty minutes. After two hours of this I notice that I have debugging turned on in my IDE, and it's waiting on the first line of the script. devops programming

The React hooks hierarchy of social acceptance visualized. Poor use is literally at the party wearing a dunce cap while everyone ignores them. Meanwhile useState is getting all the attention like the popular kid, and useEffect is down there making out with someone because developers just can't resist reaching for it. The irony? The use hook (introduced in React 19) is actually pretty powerful for handling promises and context, but it's the awkward newcomer that nobody invited. Meanwhile useEffect is getting way more action than it deserves—half the time you're using it, you probably shouldn't be. But here we are, slapping useEffect on everything like it's the solution to all our problems. Classic case of sticking with what you know versus learning the new kid's tricks.

Content Hand-writing a set of both normal test cases and edge test cases Assuming the end-user won't do anything too crazy, and only writing normal test cases Creating a program that generates random test cases Hand-writing test cases for the program that randomly generates test cases Writing a program to generate test cases for the program that generates test cases Assuming your code is perfect to begin with, and not writing anv test cases at all

Someone created a Wikipedia-style article claiming HTML is a "Turing-complete, stack-based programming language" complete with pseudo-code showing HTML tags as programming commands. This is the digital equivalent of putting a "Caution: Hot" label on ice cream. HTML is a markup language for structuring web content, not a programming language—it can't process data or execute logic. Calling HTML a programming language around actual developers is like calling a bicycle a motorcycle because they both have wheels. The creator of this abomination deserves a special place in developer hell, right next to the people who use regex to parse HTML.