3 ms·
I don't claim to "never write security bugs." However, it appears that the norm in the industry, is to write lash-up code, as quickly as possible, in the hopes
by ChrisMarshallNY 4y ago
I don't claim to "never write security bugs."
However, it appears that the norm in the industry, is to write lash-up code, as quickly as possible, in the hopes on an MVP that will get brought up by a FAANG.
And I am doubtful that most OSS actually gets all that "other eyeballs vetting" that everyone talks about. Most folks that I know, that use a lot of these dependencies, would be unable to understand what goes on in them, let alone offer fixes.
In fact, I remember a founder, on this very forum, declare that "If you don't get physically sick, looking at your MVP code, then you are spending too much time on code quality."
That posture doesn't exactly inspire confidence. I'm pretty good at what I do, and I tend to "overengineer" my security-related stuff, because I don't really have huge confidence in that. It's not my forte.
But writing good code, is something that I can do.
Like I said, WFM. YMMV.
- kelnos 4y ago> I don't claim to "never write security bugs." Sorry if I gave that impression; I wasn't trying to put those words in your mouth. > And I am doubtful that most OSS actually gets all that "other eyeballs vetting" that everyone talks about. Agreed, but a reasonably popular OSS project has a much higher chance of getting that vetting (or any vetting at all, really) than a bespoke library that the public never sees. The chances are a little higher for a nice / little-used bespoke library that you end up putting on GitHub or wherever, but it's still pretty low. > In fact, I remember a founder, on this very forum, declare that "If you don't get physically sick, looking at your MVP code, then you are spending too much time on code quality." I would never want to work for such a founder. I get the tension between getting a MVP out before you run out of money, but experience shows that prototype code ends up living in production a lot longer than anyone plans for. And I've personally seen those prototypes cause 6 and 7 figures of damage to a company later, when they haven't been properly replaced or at least improved when they should be. I'm glad what you're doing works for you (you sound like you probably actually are an above-average developer, unlike -- by definition -- most people), but I don't think I could in good conscience recommend your approach as a general practice.
- ChrisMarshallNY 4y ago> I don't think I could in good conscience recommend your approach as a general practice. I can live with that, but ... (There's always a "but"). I am not happy at all, with the general industry practice of writing every project to be something that can be understood by inexperienced, undisciplined coders. Every language and programming methodology has an "advanced" type of thing, requiring people to have experience and/or book-larnin'. I write Swift at a fairly advanced level. I am not at the level of some heavy-duty advanced Swift people, but I am pretty "idiomatic," in my approach. It is not "rewritten TypeScript," like so much code out there. My code is very well-documented, and I hold myself to standards of Quality that most folks in the industry consider to be obsessive to the point of insanity. My testing code usually dwarfs my implementation code, and my documentation is, let's say ... complete. You can see what I mean in my latest module[0]. The fact that so many folks have so much scorn for my posture and approach, tells me pretty much all I need to know. My values are not in sync with the prevailing industry values. I guess that I'm an "anomaly." I can live with that, as well. I won't write junk, so that someone used to junk, can comprehend it. If people aren't willing to learn enough to understand my middle-of-the-road semi-advanced Swift, then I can't help them. Swift is an awesome language. I feel that we are doing ourselves a disservice, if we do not explore it. I write for myself. I write code and documentation that I want to use (and I use it). I really don't care, whether or not someone else "approves" of it. I am not relying on others to review, maintain, or patch my code. When I do use other people's code, I vet it fairly carefully. Including a dependency is a really serious matter. I'm handing full control of my execution context to code that someone else wrote. I'd damn well better take that Responsibility seriously. [0] https://github.com/RiftValleySoftware/RVS_UIKit_Toolbox https://github.com/RiftValleySoftware/RVS_UIKit_Toolbox