CMS Conf

Patchstack

Maciek Palmowski

Company Culture

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

The article discusses the problems caused by a particular type of programmers in the industry and proposes solutions to tackle the issue.

The Worst Kind of Programmer

I agree with that agile methods (like scrum, if used correctly) and DevOps (furthermore: some kind of dogfooding) can help avoid problems, where single developers single-handedly ruin a project. Actually the whole point is: where teamwork is required, don’t let ego-fu**ers do the job.
I have to disagree with the statement, that languages like Lua or Go are a better choice than Rust. Sometimes they are, but often they are not. I like Go and Rust. Both of them. But Go is my go-to-language, if I write a program that could also be quickly written in Python, but has to be compiled and/or containerized. Most microservices fall under that category.
Rust on the other hand is the best choice for critical applications, where errors may not occur. Of course you can still make mistakes, but the most common errors that C/C++ programmers make can only happen in unsafe code. So you have been warned.
Ans it’s also the best choice, if you target Wasm. So it’s more of a “best tool for the job” decision - in many cases Rust and Go are both good options.

Perhaps coding alone can make people a little narcissistic, if there’s little room for collaboration or interaction. Just getting things perfect becomes the holy grail.