I had to shorten the title, but some of the information you say is missing is actually covered on the question.
Anyway, I just thought of adding this question today because I actually was asked a variant of this in an interview (no mention about code style docs), and the interviewer was not happy with my answer which was something like “Whatever style decision is important should be covered in the style guide. If you don’t have a style guide, then I’d assume that this is not really important for the team, and I rather focus my review on things that really matter. Is the code testable? Is it maintainable? Is the code being introduced completely different from what we have before or are we consistent with our inconsistencies? All in all, I’d rather spend time working on new features and shipping than arguing over style preferences.”
Imagine if OSes in the 90s crashed as rarely as desktop OSes today. Imagine if desktop OSes today crashed as rarely as mobile OSes today. Imagine if mobile OSes crashed rarely enough that the average consumer never experienced it. Wouldn’t that be a better state of things overall?
Depends. What is the cost to get there? Will that sacrifice openness? Will that sacrifice portability? Will that require ossified structures that will make development of new applications more difficult?
Look, the article is talking from the perspective of someone who is developing web apps in Ruby. Performance is not a huge concern. Processes being crash-proof are not a concern. You know what is the concern? To be able to validate ideas and have something that bring customers willing to pay real money to solve their real problems.
For his scenario, forcing to define everything up front is a hindrance, not a benefit. And having GP screaming at it like this for having this opinion is beyond ridiculous.
I don’t really want to be talking past each other. The point I am refuting is that even if type-safety can help reduce the amount of bugs shipped, this is not the only metric that matters to measure the value of the software being developed.
bugs are really annoying
And being late or never delivering out of fear of shipping buggy code is even worse.
Some years ago, I worked on a crypto project that was financed via an ICO. This meant that whatever money the company was going to get was already in their hands, and their only job was to make sure they could prove they’ve done a best effort to deliver what was promised to investors.
Because of these incentives, the engineers were more concerned about covering their asses regarding bugs than to actually get the software out in the hands of users. The implementation was in python, and to the team it was easier to justify spending time on getting 100% mypy coverage than to get things in hands of users to see the value of what we promised to deliver.
In the end, by the time the team managed to deliver, the code was super well-tested, there were 0 mypy warnings and absolutely zero interest from other people in adopting our tool because other competitors have launched a whole year before them.
How many billion dollar companies were built on dynamically typed languages? Do you think that companies/bosses/investors care about the compiler warnings or whether you can deliver/iterate faster than the competition?
nobody likes plumbing, but we all know it’s necessary.
Is it, really? Are we all working on mission critical software? We are living in a world where people are launching usable applications with nothing but the prompt to an LLM, ffs, and you are there trying to convince yourself that pleasing the Hindley-Milner gods is fundamental requirement in order to deliver anything?
Good engineering is about understanding design constraints and knowing where to choose in a myriad of trade-offs. It’s frankly weird to think that such an absolute, reductionist view like yours got so much support here.
FYI: it looks like Trump is going to win the popular vote on this one as well.
No flair. What you need is:
<post title> @community@instance
<line break>
<post body>
Edit: to those downvoting: If you think what I am saying is wrong, how about giving a better answer?
Here is a Mastodon Post and here is how it ended up in Lemmy (The NSFW tag was because I mistakenly tried to add the title as a content warning)
Why? How many kilobytes of disk space are you going to save from that?
Somewhat related: would you be interested in joining https://fediverser.network? The project is meant to help people migrate from Reddit to Lemmy automatically. People need to authenticate once with their Reddit credentials, and the system finds the best instance for them and looks at their list of subscribed subreddits to automatically find and follow the most relevant Fediverse communities.
The project is now at the point where more people can join and help spread out the word to Redditors, so the idea now is to get more people there to sign up (to help fill the crowdsource map of community recommendations) and to get more Reddit moderators who might be interested in helping their communities to move out of there.
**
**
Fair enough. I think I’d rather be more mindful of what “mode” I am browsing around. I stick with only the subscribed communities, and whenever I am in the mood for something new, I take some time to browse around the instances to see what’s out there. Browsing by all and then blocking all the crappy stuff seems to me like a constant effort with very little potential reward.
wouldn’t it be easier to stop browsing by all and only see the things you want to see?
Wait, how many communities do you need to block every day for this to be an issue?
What is your base image? It has no python installed.
You know that you can configure minio to only serve images for authenticated requests, right?
Don’t reinvent the wheel unless you have a very good reason to do so.
It looks like your cloudflared is trying to reach the Lemmy UI directly? What is the URL your tunnel is configured to reach?
I might be wrong, but I believe that lemmy-ui default port is 1234, not 1236.
Can you get the the backend to work? If you make a request to <your domain>/api/v3/site
, do you get a response?
Yes, but if you put it a public library you will be opening yourself for all sorts of copyright trolls trying to sue you for file sharing.
I work with Python. Usage of formatting tools (black, ruff) are widely adopted. Part of its Zen is “there should be one way to do it”, most of its idioms are widely adopted and if you ask anyone about an example of a PEP, they will respond with “8”.
That is to say, “how python code should look” is somewhat of a solved problem. Any occasional differences that might show up in a codebase are likely to be minor that are simply not worth arguing for.
I think that the interviewer was mostly looking for an answer where I could talk about how I deal with conflict. But to be honest if that was the case I would be either more straightforward about the question, or I would try a different scenario with something that might happen more frequently.