• 1 Post
  • 22 Comments
Joined 7 months ago
cake
Cake day: November 21st, 2023

help-circle




  • I’m pretty sure it’s more like

    Junior dev: Got all the nice addons, RGB lighting, only uses dark theme, got all the stickers, works from either a café or moms basement.

    VS Senior dev: Works on company standard issue hardware, barely customizes visuals (but got a script which makes a cup of coffee on the shared machine in exactly 2 minutes and 30 seconds), works in shared office, has old rolling cabinet with unknown artifacts last touched 10+ years ago.

    Obviously this is an overgeneralization and not a catch-all, you might even say that it’s “programmer humor”.







  • Ekky@sopuli.xyztoProgrammer Humor@programming.devMy Git Knowledge
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    4 months ago

    “Fixed issue with ssl python libs,” or “Minor bugfixes.”

    Red bird going "Hahaha, No!"

    In other news, never work more than one person on a branch (that’s why we have them). Make a new related issue with its own branch and rebase whenever necessary, and don’t even think about touching main or dev with anything but a properly reviewed and approved PR (in case they aren’t already protected), or I’ll find and report you to the same authority that handles all the failed sudo requests!

    Also, companies that disable rebasing are my bane. While you can absolutely do without, i much prefer to have less conflicts, cleaner branches and commits, easier method to pull in new changes from dev, overall better times for the reviewer, and the list goes on. Though, the intern rewriting multiple branches’ history which they have no business pushing to is also rather annoying.






  • For those wondering how to exceed the 70 (80) recommended character limit and still follow best practices:

    1. Write the title on the first line, keep below 70 characters.
    2. Make two (2) newlines
    3. Write one or more descriptive paragraphs.

    The first line will be shown as commit message, and the full text can usually be viewed by checking out the commit. Sentences can span multiple lines, but try to keep the line length below 70 characters for best readability.

    This off the top of my head, so feel free to correct me if I’ve misremembered the best practices.


  • +1

    I personally started by playing around with Ubuntu, but it just didn’t feel intuitive coming from windows.

    Went over to Mint, and was very happy,especially with drivers and gaming. I even fully removed my windows installation during this period. Having gained a better understanding of Linux, I have now moved on again.

    The only real drawback of Mint is not natively supporting KDE Plasma (as they did before). And yes, you can just install it yourself, but I wouldn’t recommend a beginner who barely knows how to install Linux to attempt such an endevour.

    One word of advice to OP: don’t wait till you can’t use Windows anymore. Start by dual booting and getting a hang of Linux, but with windows at the ready for any tasks you cannot yet do/feel comfortable doing on Linux. As you get a better hold of Linux, you should naturally begin to use Windows less.

    The worst thing someone can do, is to jump OS without any backup or safety net. Learning to use Windows took a long time, getting a hang of new concepts and getting used to an alien environment. Now, already having a hang of “computers” (Windows), we have digital needs and expectations (E-Mail, gaming, etc.) which will need fulfilling, but many seem to forget that a different OS means different ways of doing our daily tasks and different challenges to handle.

    And yes, “different”, because Windows definitely also comes with it’s own unique challenges, you just don’t see them as much when having gotten used to them.