• 4 Posts
  • 64 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle

  • I host my own gitlab-ce instance in docker which works well. I mainly needed a web UI for git and I track issues with it. I think there are boards or at least free plugins for the community version, but I do not use them. You can version your documentation in .md files too. Not sure if it can substitute Jira for you, but you mentioned Bugzilla and I like gitlab a lot more.

    Just make sure to update the container regularly, you can’t make big version jumps without the intermediate updates.

    I think you can combine it with OpenProject if you need more project planning.











  • The shower head in the picture is a bit unusual because of the two screws on the right where you can adjust the head. If you loosen the one next to the wall the shower head tilts down and faces the wall (which is nice if warm water takes a while and you don’t like a cold shower) and with the other one you could make it spray the opposite wall. So it’s pretty versatile. (Or annoying if the screws can’t be tightened enough)










  • In short: it’s always like this, sometimes more, sometimes less. And guess what: it’s the main part of the job. As a developer you have to understand what the customer (your boss) needs (sometimes not what they say they want) and to figure out how to do that by yourself. It’s nice to have colleagues you can ask, but it’s like on stackoverflow. The accepted answer is not necessarily the right or good one. Often you have to work with bad documented legacy artifacts (code, api) and figure out what they do. Also the tech changes, you have to constantly keep up with changes and what was great years ago may now be outdated. My advice:

    • Do not start coding until you are sure you understood what is to be done.
    • if there is no user story to describe the task write it yourself
    • write good tests for your code. It’s an art. While thinking about corner cases you often find questions you did not think about at first
    • if you don’t know how to do it ask people around you, browse the web, read books. Develop the skills to figure stuff out. Most of the time noone knows the correct answer. It’s your job to find it.
    • do code reviews with others, usually both benefit from it
    • write clean code

    If you don’t like your working environment then change it. Especially when you think you can’t learn anything new there or it is no fun to work there. Go to meetings in your area (meetup or so) or online to meet other developers and ask them about their job. You get a feeling about what is considered a good job in your area. Good developers will always find a good job. Be one of them. As long as you think you’re a god who can code anything, that’s probably not the case. ;-) The best you can achieve is to be an expert in a very narrow field and to be good in some others.