I'm thinking of infrastructure tooling, I'm thinking of frameworks, I'm thinking of libraries, I'm thinking of languages, I'm thinking of architectures,

None of the necessary knowlede is in any curriculum, nor in any of the SEO-stuffed articles you find when trying to search for answers.

It is nigh-impossible for most engineers, on most issues, to make informed decisions.

@cvennevik partially this is because we stopped building these tools in the early 00s/mid 90s.

I am not joking. Research kept going but we lost the industry knowledge of this domain. We are starting to rediscover some of it thanks to both typescript and rust community.

But it will take a long time, and there is nearly no funding. The industry forgot that we can have good tools and it actually impact output and outcomes.

@Di4na I wouldn't have thought of this angle, so thank you for bringing it up.

(Also really cool seeing you in the replies as I've really liked your writing on developer tooling and process engineering)

@yellowbrickc Yeah, my thinking is that each job adds too little, too slow, to our toolbox. Without going out of our way and in-depth on particular topics, I think we're bound to have major blind spots.

Like, I've learned a ton about web dev as a field from engaging with people, doing side projects, and actively reading articles for months, and it has taught me lots that I would never have learned on the job.

And I am now conscious of *even more* things within it that I have blind spots on.

@cvennevik @yellowbrickc
Do you know about the @SoCraTes_Conf ?
It's actually an whole series of #OpenSpace events in Europe and the whole world.

I can highly recommend it

See also the partner conferences at the bottom of https://www.socrates-conference.de/home