• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: February 9th, 2024

help-circle

  • Taking a short break to do something else for a few minutes is a wonderful way to stay productive and not stuck on some issue.

    I remember specifically one day in university times I was stuck for almost 4 hours in a problem. I started working shortly after 8:00 and I went for lunch with some buddies, came back, and instantly knew the solution. This is how I learned how to have lunch at 9:00



  • The stdlib I actually find quite complete. Especially for http projects. You really don’t need third party libs for that for example.

    The errors were super strange to me at the start, but I’ve come to really like it over exceptions. It is similar to old error codes, but I feel that this makes one always have to be mindful of error handling and the non happy path (thinking of large Python projects where no one cares about exceptions).

    A lot of people tend to compare Go and Rust, but I feel that the languages are just too different. Rust is good for a variety of things which don’t overlap with the things Go is good for.


  • I don’t disagree with this, and honestly I would probably support just using bash like you said if I was in a team where this was suggested.

    I think no matter how simple a task is there are always a few things people will eventually want to do with it:

    • Reproduce it locally
    • Run unit tests, integration tests, smoke tests, whatever tests
    • Expand it to do more complex things or make it more dynamic
    • Monitor it in tools like Datadog

    If you have a whole project already written in Python, Go, Rust, Java, etc, then just writing more code in this project might be simpler, because all the tooling and methodology is already integrated. A script might not be so present for many developers who focus more on the code base, and as such out of sight out of mind sets in, and no one even knows about the script.

    There is also the consideration that many people simply dislike bash since it’s an odd language and many feel it’s difficult to do simple things with it.

    due to these reasons, although I would agree with making the script, I would also be inclined to have the script temporarily while another solution is being implemented.




  • I used to work with a guy who was a tech lead on a project. He was getting constant pressure that he app he lead simply did not work. The problem all came down to a database connection that was being used in multiple threads.

    I told him what the problem was. He said, great let’s make a meeting to talk about it. I wasn’t allowed to solve it just yet. I made the meeting. Everyone understood. The lead told me to then make a prototype, but still not allowed to just fix it. I made the prototype. The lead said we needed a meeting to talk about it. Still not allowed to just fix it.

    Meanwhile we still get pressured to make the damn app work, the lead keeps saying that none ever bothered to read documentation and that we need to sit down and talk about how we are going to to solve.

    This went on for several weeks. When I was finally allowed to solve the issue (not by him), I took only one day.


  • I’ve been promoted into management for over one year now, and I’ve barely programmed on the job. I find it hard to keep up with the details on the application, but I still make an effort to with news, and do some programming for fun on my on.

    I think it’s important for manager to still be able to make small contributions to the application. The manager isn’t going to own a big new feature that takes several sprints to complete, but he can still debug or solve some bugs, or make smaller changes. He should also have an overview of the code’s structure, and know about the technologies used to build the project.


  • Indeed. The name doesn’t follow the conventions of other commands in Windows/Powershell at all. And it is inconsistente too. “sudo” stands for “super user do”, but in Windows the notion of super user is called administrator. This will likely also cause confusion with people googling for “sudo” and getting to *nix related pages instead.