Tag Info

Hot answers tagged

7

We write code for other humans to read. New technologies are intended to make code easier to read, not harder. There are good and bad ways to use new technologies. If you're trying to write "impressive" code, you're doing it wrong. I suspect it's not just the use of the technologies that is concerning people. If the way you're using LINQ made a huge ...


6

Use a linter or some program or tool that automatically enforces style. That should alleviate the objections about it taking too much time. Most of the objections have to do with "I'm uncomfortable with that style." It doesn't matter. Coding conventions are all about uniformity. Enforcing that uniformity will make code reviews easier by eliminating ...


6

Three things come into my mind. First: 'simple' is not 'stupid'. Simplicity is the predecessor of elegance. Second: in your job, the most important thing to do is to be is a team player. Your boss is a team player. Is job is to keep the team together, and that means making your code understandable to your team mates and by that making you a part of the ...


5

I like to use present tense when the error/exception-generating code is the "root cause" of the problem, and past tense when I'm merely repackaging an error/exception from a lower layer of code. For example, when our frontend makes a request to our backend, the backend may return an error message "Cannot connect to database", and the frontend will throw ...


4

This is a difficult situation. First, do not get into a negative relationship with your boss, or with your co-workers. Above all, be positive, recognizing their valuable traits, and being helpful. Then, see what you can do to expose your co-workers to newer techniques. If necessary, include explanations in your code, so people can follow you. Appeal to ...


3

The question can be divided into "Why does Java C support brackets behind variables and even behind method signatures?" and "Why would Java inherit so much from C?"; Java also inherited other weird syntax, especially that for switch (why not use curly braces as for everything else and use : and break ?). To answer the first question - I believe back in the ...


2

There are two options that one has for dealing with specific, frequently occurring immutable objects. You can either instantiate them each time, or you can use a constant that is probably stuck in a final static in some class. BigInteger for example has ZERO, ONE, and TEN. However, this is an attempt to avoid instantation of new objects. Say you're ...


1

It seems to me that you were given legitimate feedback from your manager. Not taking anything from it would be a lost opportunity for you. Whether or not your way is right or not your colleagues are struggling. If they're struggling the company will struggle and you will struggle providing tons of support when they're trying to debug, extend or otherwise ...



Only top voted, non community-wiki answers of a minimum length are eligible