3 ms·
> A developer not knowing what happens in an IP packet I don't care if devs understand IP packets, TCP congestion control algorithms, or anything similarly low
by sgarland 5y ago
> A developer not knowing what happens in an IP packet
I don't care if devs understand IP packets, TCP congestion control algorithms, or anything similarly low-level. If they do, that's awesome, but it's not expected. I do expect them to have a basic understanding of expected latencies for intra-DC vs. internet, why running Flask in production isn't a good idea, and if they're really sharp, an inkling of how Kubernetes networking works.
- arwineap 5y agoI think I understand your sentiment, but what's wrong with flask??
- kazen44 5y agoi assume the poster means running flask in production without something like nginx in front to serve as the webserver. the flask build in webserver is not production grade software in my opinion.
- Cyphus 5y agoIt is also the opinion of the people who wrote the built-in webserver. If you try to run it in production mode, it'll emits this warning on startup: > WARNING: This is a development server. Do not use it in a production deployment. > Use a production WSGI server instead. I don't expect junior devs to have a sense for what is production-grade and what is not, but if they try to ship software that explicitly warns against being used in production, you've got a real liability on your hands.
- rswail 5y agoI do. Why should devs not understand the environment in which they are developing? If they don't understand the concepts then they're not developers. Why do we call these people "software engineers" if they're not engineers. There is endless documentation, there is all the resources needed. Allowing devs not to know what they're doing is a complete failure of anything approaching professionalism.