At my last shop the onboarding process was kept in newDev.html, which was accessible in the dev, QA and gold environments, but not prod. included all the installs, checking out from vc, creating a Yourname.java file that extended Developer, and wrote your deets to the DB. Then you had to edit the Rollcall class to make sure you were listed. Then update newDev.html as appropriate so the next hire can complete their setup. Then check it all in, get your check-in approved, and then your code went LIVE that sprint and we all made a BIG deal of welcoming you to the community.
Recent
From the blog
-
Stop Texting Your Friends: SMS Was Never Designed to Be Secure
SMS is great for flight notifications, appointment reminders, and delivery updates. But for conversations with friends and family, it’s time to move…
-
Gheist Can Turn Stolen GitHub Access Into Stolen Production Credentials
If you use GitHub to build and deploy software, take a few minutes to understand Gheist. You do not need to be…
-
Patching your PHP/WordPress on AWS? Don’t Do It Twice
Last week a critical PHP vulnerability dropped. That same week, I realized the WordPress image my blog runs on was never going…
-
Your AI Just Violated First Normal Form. And All Its Tests Passed.
We are the kings of the code. That may sound a little grandiose, but consider what happens when we use AI agents…
-
When AI Is Smart Enough to Get Around the Rules
AI is becoming an extraordinary programming partner. But sometimes its eagerness to help is exactly why we need to pay attention. I…
Leave a Reply