620 karma · joined June 3, 2019
https://twitter.com/Ax_Sharma/status/1509103877978824707
[1] https://spring.io/blog/2022/03/29/cve-report-published-for-s...
[2] https://github.com/spring-projects/spring-framework/pull/280...
Edit: They just translated the chinese post you can find linked here.
[1] https://github.com/spring-projects/spring-framework/pull/280...
Like companies such as Tele Atlas did back in the days for map data (when they didn't have much more than that I guess).
Wait until you have to follow dozens of 5 lines methods for the sake of unrequited abstraction that could have been compacted in an easier to read 30 line method.
And their handbook: https://about.gitlab.com/handbook/
I wonder, is the time spent fixing inane production issues time well spent? Is the time spent by testers/QA to report obvious bugs well spent?
Devs, test your stuff like if you were the only one doing QA, and everyone else along the chain should do the same.
With all the competition on fibre equipments I really doubt.
Other than github providing something similar, why don't they also expose something useful about github users supporter info through their API? Maybe they already do, don't think so.
Pretty sure it will never become the norm outside of some cookie-cutter shops that churn out CRUDs.
If someone would link this to me, I'll interpret it as extremely dismissing. A declaration of war.