21 ms·

That'd be actually lovely. Not a bad idea. Start from scratch. Rethink everything. Like in the 70s. Create stuff like UNIX, etc. There's a lot that needs fresh

by shd4 7y ago

That'd be actually lovely. Not a bad idea. Start from scratch. Rethink everything. Like in the 70s. Create stuff like UNIX, etc. There's a lot that needs fresh thinkin'. But ... there's nothing like that happening at all. Seriously. Gen Z are not picking-up at all, have no idea, depend on us. And that's real bad (for the future).

verdverm 7y ago
Are you being age-ist here? Do you remember how you were at their age? What did the older generation say about ours... and now we say the same?
- tmcb 7y ago
  My impression is that he meant Gen Z did not have the chance to witness the alleged deterioration of the software industry, hence, can't tell how bad is it.
ToolsDevler 7y ago
I agree but I also disagree, since we have some 1970/80s developers here who teach the attitude "Don't care about details" to younger ones which leads to excessive library usage for even the simplest "problems" (e.g. a team of ours had a JVM crash after they loaded >65K libraries during startup... no one can possibly need so many libraries!) and also to totally stupid design mistakes (e.g a rest service being queried thousand of times per second (open socket, 1 query, close socket) for the same data instead of caching and reusing it in a reasonable context --> massive performance problems). Thats the maximum "I don't care about details" you can archive and it happens a lot since around 3 years. The older deveopers even talk about "enlighment" and "superior knowledge" to get more young people to their side (it is kinda religious, seriously...) And there is not re-thinking happening in their heads (fortunately in the heads of the people in charge). All people (including me) who are not a member of this new religion are often excluded from meetings where they discuss the development (or should we say library management?) of new software projects (their current project is failing completely at the moment because those evil details were ignored, popcorn is ready). Critizism is answered with "you're not modern, go away!". The most "extreme" are not the youngest but the older ones (mostly the 1970s) in their "modern" team. I'm kinda Gen Z (mid 1993) and I'm seriously concered about this develpoment. I need to understand things in detail and I want to know when and why I need a library especially when you work with critical software as we do. New, modern and fancy often means imature and not battle-tested. New Programming languages don't necessarily solve problems. And writing something on your own is not always wrong, at least when you have good reasons and (most important) the qualification to do it. (remember, in the context of shipping critical software).

by shd4 7y ago

verdverm 7y ago

Are you being age-ist here? Do you remember how you were at their age? What did the older generation say about ours... and now we say the same?

tmcb 7y ago
My impression is that he meant Gen Z did not have the chance to witness the alleged deterioration of the software industry, hence, can't tell how bad is it.

ToolsDevler 7y ago

I agree but I also disagree, since we have some 1970/80s developers here who teach the attitude "Don't care about details" to younger ones which leads to excessive library usage for even the simplest "problems" (e.g. a team of ours had a JVM crash after they loaded >65K libraries during startup... no one can possibly need so many libraries!) and also to totally stupid design mistakes (e.g a rest service being queried thousand of times per second (open socket, 1 query, close socket) for the same data instead of caching and reusing it in a reasonable context --> massive performance problems). Thats the maximum "I don't care about details" you can archive and it happens a lot since around 3 years. The older deveopers even talk about "enlighment" and "superior knowledge" to get more young people to their side (it is kinda religious, seriously...) And there is not re-thinking happening in their heads (fortunately in the heads of the people in charge). All people (including me) who are not a member of this new religion are often excluded from meetings where they discuss the development (or should we say library management?) of new software projects (their current project is failing completely at the moment because those evil details were ignored, popcorn is ready). Critizism is answered with "you're not modern, go away!". The most "extreme" are not the youngest but the older ones (mostly the 1970s) in their "modern" team. I'm kinda Gen Z (mid 1993) and I'm seriously concered about this develpoment. I need to understand things in detail and I want to know when and why I need a library especially when you work with critical software as we do. New, modern and fancy often means imature and not battle-tested. New Programming languages don't necessarily solve problems. And writing something on your own is not always wrong, at least when you have good reasons and (most important) the qualification to do it. (remember, in the context of shipping critical software).