You may notice that basically all of these things can be caught by IDEs at dev time or linters integrated into a CI environment
-
-
Replying to @EmilyGorcenski
Which is a strong indication that the mfg is not using version control or adequate engineering praxis.
3 replies 51 retweets 136 likes -
Replying to @EmilyGorcenski
Else why would you drop $10000s into certification to find errors you can catch with < 2 hours of work setting up Jenkins?
4 replies 37 retweets 128 likes -
Replying to @EmilyGorcenski
But this is what really worries me. Adequate source control practices make it harder for a rogue employee to sneak in backdoor code.
2 replies 53 retweets 147 likes -
Replying to @EmilyGorcenski
And these failures are not the kinds of failures you'd get with adequate code control in place.
3 replies 41 retweets 106 likes -
Replying to @EmilyGorcenski
Look at this. Are you kidding me? 1st year front end devs easily navigate tools to prevent these issues.pic.twitter.com/JUjgK6apuW
9 replies 47 retweets 129 likes -
Replying to @EmilyGorcenski
Hay frends, wanna run COBOL, VB, C, C++, SQL, and Java in the same environment? Democracy depends on it.pic.twitter.com/tqMNDtFHaR
12 replies 113 retweets 176 likes -
Replying to @EmilyGorcenski
I'm confused: isn't this excerpt in contradiction with the first excerpt that says application entirely written in java?
1 reply 0 retweets 0 likes -
-
I looked at 30ish different reports for different systems/versions
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.