Skip to main content

in reply to Hank G ☑️

There's also "Not sharing your code so you aren't responsible for free maintenance and support for the rest of your natural life"
in reply to Hank G ☑️

junior dev: i dont know what im doing
senior dev: nobody knows what theyre doing, including me
in reply to Hank G ☑️

I had been programming for *decades*, and for most of that gleefully pushing bullshit into team/company source-control in order to get "more eyes" on what I was doing, before I first worked on a project that lived on github.

It took **a week** to actually type "git push" on my first commit there, the imposter syndrome was so bad.

Nowadays, it's "push PR, ask for a review, three seconds later go 'oh shit, lookit that crap, hang on!'" and off we go. :)

in reply to Hank G ☑️

Dito.

Another is time. If I only had more time to properly work on something besides my work. But when I only get a few hours of free time every week, I prefer exercising my body to not become a wreck with 40.

And yet another is seeing colleagues of mine shamelessly downloading open-source code of students/researchers from GitHub, write a Flask app around it, and soon get promoted for their "excellent work", while whoever wrote the heart of it doesn't ever get an acknowledgement of it.

in reply to Hank G ☑️

About 3 years ago, I published a greenfield FOSS project I've been working on for about 10 years. Nobody ever used it. Just looking at the directory, I have um, 27 other interesting projects, that were similarly popular. Published several patches over the years to other projects that were more than 1-line long, and of them ...zero were accepted.

Only conclusion I can make is I'm really bad at selling myself. I mean programming.