4 ms·
The Tragedy of the Bloomberg Code Issue
- noir_lord 11y agoPerhaps or perhaps in an introductory guide they decided not to muddy the waters any more than necessary in the interests of brevity (as post mentions, 28,000 is seriously pushing it as a word count for a long form article).
- JustSomeNobody 11y agosigh It is 28000 words. It can't cover everything. Some things will get left on the cutting board. Get over it.
- tptacek 11y agoIn the case of this magazine, it's clear that software security is not on the minds of the professional programmer who wrote the issue. It's also not a concern of the editor or any of the team that contributed to it. From what I have seen, that neglect is not unique to Bloomberg. This was a surprisingly dumb and disingenuous thing to see from Bejtlich, who should know better. In particular: Bloomberg (the company) has for the past decade or so managed one of the better application security teams in the business. He meant to pick on the magazine, not the company, but sauce for the goose, die by the gander. Bejtlich is not a software security person (his background is in network security and IR). I am. I thought the Bloomberg Code article was wonderful, accomplished exactly what it set out to do, and picked a very worthy thing to accomplish. We get to better software security by having more people understand code.
- davidbanham 11y agoI try not to make a habit of reading reviews written by people who have not actually read the thing they're reviewing.