Best practices are aspirational goals for everyone to strive for. But that list is boring – what if you want to aspire for greatness in…a different way? Recently I started such a list and the F&O Twitter community turned it into gold.
Worst Development Practices
You’ve taught me a lot of things.
— Joel Leichty (@joelleichty) July 23, 2020
1️⃣ Always compile Packages on a dev box.
2️⃣ Overlayering is rad.
3️⃣ Make class methods Public so everyone can see the code.
4️⃣ Move code via XPOs.
5️⃣ Compile warnings are only suggestions.
He forgot...
— Malcolm Burtt 💙 #IStandWithUkraine #WokeAndProud (@MalcolmBurtt) July 23, 2020
6. always deploy from Visual Studio
7. Testing is for developers who don’t believe in themselves.
— Joel Leichty (@joelleichty) July 23, 2020
8: Use macros when you spot similar code and queries
— Kenny Saelen (@kennysaelen) July 24, 2020
9. Stay on platform update 12 and laugh at error messages stating lack of support.
— Lane Swenka (@LaneSwenka) July 24, 2020
10. Wait until Microsoft fix all their Best Practice errors before you fix yours (sorry, couldn't resist)
— Malcolm Burtt 💙 #IStandWithUkraine #WokeAndProud (@MalcolmBurtt) July 24, 2020
11. No need for performance testing, as Microsoft have automatic scaling according to load😀
— Kurt Hatlevik (@kurthatlevik) July 24, 2020
12. Use your build VM for development, testing and golden dB. Then run a monthly update and escalate support requests because your code got removed and data was dropped. 😡 pic.twitter.com/GFprZjM4gh
— Joris de Gruyter (@jorisdg) July 24, 2020
13: Copy sample scripts and ignore every disclaimer telling you it's to get you started and not an official supported script and then file support cases. pic.twitter.com/b12WeZd8Px
— Kenny Saelen (@kennysaelen) July 24, 2020
14. Access and use private class members and methods via reflection.
— Paul Heisterkamp (@braul) July 24, 2020
15. Use the Connection class to do tsql updates in prod
— Michael Stashwick (@D365Stuff) July 24, 2020
16. Replicate internal GER classes to build your own paralel framework 😅
— Manel Querol (@manelquerol) July 24, 2020
17. Copy and paste ReqCalc class so you never have to move to the planning optimization service
— Michael Stashwick (@D365Stuff) July 24, 2020
18. Put static methods for event handlers to random classes, don't spend time on the naming convention
— Denis Trunin (@TruninDenis) July 26, 2020
19. Always provide your developers storage based on HDD, they are more reliable than SSD
20. Do not create indexes, indexes slow down the system and consume space
If you didn’t find your work on this list, the message for you from the wise #xppgroupies sage is:
Clearly I have or you wouldn’t be able to make these jokes!! pic.twitter.com/4IFJNsk8lc
— Joris de Gruyter (@jorisdg) July 23, 2020
Joel Leichty 