DictumMortuum

I recently changed managers and I haven't been doing 1:1 meetings with the previous one. Since the new manager seems to prefer a more systematic approach, I figured I could ask you guys - do you have a plan before going into these kinds of meetings? What kind of talking points do you often have?

So, a new person has joined our team as an intern and I am tasked to be his mentor. Management has explicitly stated that he is here to learn and not to handle tickets. What would you teach to a young software engineer professional?

Hello hacker news,

I am colorblind and I work at a relatively large international corporation. I know that it's not a serious disability like the loss of a limb, except I notice it every day. The higher management always used a color scheme I can't understand for graphs. The new boardgame my friends buy is difficult, as I have to concentrate to understand which color is which; games like junglespeed, where speed matters are unplayable for me.

I also know that I am not the only one, so please, if you are a designer, a manager or someone who has to use a color scheme for their work, take colorblind people into account.

Happy Christmas everybody!

I'm in the process of migrating the common libraries I used during my university years to github. They were the building blocks for larger implementations, like bplus trees, static hashing, etc.

I haven't really coded in C since then, so when I looked at the source code after all those years I found a large number of bad practices and I'm slowly working towards fixing.

My question is - is there any guide towards organizing large C codebases that provides info like:

- How to name header guards? - How to name variables used for the same purpose for consistency? - How to name globals? - How to name the API functions? etc