TODOs top 5

[x] create README.md with TODOs
[ ] add tests
[ ] write documentation
[ ] automate deployment
[ ] improve security

I am happy, my first open source contribution was merged within 2h without any regressions!!
.
.
.
.
.
.
.
.
Well, it was only a typo in Readme.md which I have fixed 😂

tl;dr: spent 12 hours creating an api for a job interview challenge. Got rejected after 4 weeks with no real feedback, and all I can do is rant!

So I was in the interview process with a company that was a great fit for my background.

Got through a couple of phone screens, and was given a coding challenge consisting of writing a web API with a couple of endpoints and a filter function.

I'm like, ok no problem, I happen to have created apis for some mobile apps in the past, and I pick Django rest framework to get the job done.

Implemented it on a Sunday, wrote a medium size Readme.md and some unit tests and submit. Took almost four weeks and a partial resubmission to get a rejection with no specific feedback.

Now I'm shamelessly butthurt and I have nothing else to do but rant! Worse part is I looked back at the code and in my opinion is solid AF, so I put it on my public GitHub cause fuck it!

$ mv README.md please-README.md

The intern again. FUUUUUUUUUUUUUCK!!!!!!!!!!!

She's now done the Laravel course my manager bought her, so now she feels she's ready to tackle a real world project. Hahahaha.

Okay, I have a project set up: Replicate a simple existing website that only has a basic header, some picture thumbnails and a footer element using Laravel. I've already installed Statamic and everything she needs as dev dependencies and made a step-by-step README.md file for her to get the site running locally on her machine. I told her to replicate the home page HTML.

She didn't read the readme file after I've told her multiple times in the past to do so. She tries to run the Laravel application without running composer update and all the other commands I listed in the readme file, and doesn't read the fucking console errors she's getting. She cloned the project into another Laravel project and her files are a fucking mess.

I am sick and fucking tired of telling my manager that she is not suited for this industry, she's just costing the company money and wasting my fucking time. I have been unable to focus for the past month and a half because of her.

She can't even fucking Google the console errors she's getting, just hopping on MS Teams asking me to help without even trying to solve it on her own.

I want to cry. Fuck this company and its stupid CULTure.

README.md file on some random GitHub repository

"A Python program written in Python which does xyz task"

Ok you don't say

I cant live when README.md isnt complete and there are errors...

WTF is up with open-source projects using emojis in their commit messages... FUCKING emojis..

I get it, programming is fun and a hobby to many, but can we also keep at least a minimum level of professionalism here.

WTF is a wheelchair or bento emoji at the beginning of a commit message supposed to mean? Why the hell even bother to use it in the first place? There is no fucking reason for this retarded shit.

Is this what happens when activist developers get out of their way to make programming "inclusive"?

It is your personal project and so if you want to use emojis it is OK, I respect that (not really) but I can't trust your code, your commitment, or the quality of your work if I see those dumb Unicode characters there.

Git commit messages are not a game. Be playful with comments in code or your readme.md file but git messages should be a clear reflection of the changes not what a teenager's phone vomited on the keyboard.

Searched for common typos in Github readme.md files to make trivial PR's to get a free t-shirt, just so I could put off going clothes shopping for a bit longer.

Update README.md

(last commit to readme.md 1 year ago)

- initial commit

Really, I hate this composer / bower / npm shitholes!

Why the hell is my app 300MBs?!? Because that shitty pudding composer decided to download the ENTIRE git including README.md, examples, 5 hours of assembly-giraffe porn, my granny's pajamas and two wraps of kebabs!

How hard is it to define the folder that contains the REQUIRED library so that our project might stay at 5MBs instead of 300?

I started hearing about Git about a few years ago (I think I was in the first or second class of my study, am in the fifth now). I understood the concept but found it really hard to work with, as in, so hard that I just didn't use it. It kept coming back again and again and a few months ago I thought: Fuck it.

What is one thing that a lot of devs are good at? Automation, exactly. So, I had a GitLab account (idc about their recent fuckup, will keep using it) and had to keep asking people to set stuff up for me.

I started to do research and stumbled upon the empty repo page from GitLab which provided clear instructions on how to locally do stuff so I could interact with a remote repository. Then I started to bash script.

After one day, I had a fully working bash script which, with just two parameters, initiates a new repo, clones it locally, creates a README.MD and commits + pushes it.
Then I put it as executable in the /usr/bin.

So now, whenever I start a new project, I just have to create a directory, go into that directory and call a command with two parameters and I'm good to go!

Actually pretty proud of that, although it might be the most usual thing for a lot of peoples, I wrote a workaround/automation thingy for the thing I find the hardest in development :).

You’re a fucking demon if you don’t include a README.md.

Thanks you for reading my GitHub complaint.

Developers too lazy to google search/read the README.md yet too proud to admit their mistakes.

They create disasters that I need to clean up later because they took a vacation.

What makes a good README.md for you ?

40 commits updating the readme.md. I don't feel bad about it

I like js and node in general.
But there's this thing I hate about NodeJs...

The blogs. The goddamn blogs.

Every goddamn blog post. Is code. Dozens of lines of code.

Oh, so you want X feature? Just copy paste this shit.

I swear to god, blog posts are the source versioning system to these people.

What they should instead is
a) Create a package.
b) Add tests to it.
c) Present the package to the reader with some minimal code.

But I'm a getting a huge impression that node blog writers want you to copy the code in their post, paste it in your project, and be happy with it.

Now, I'm not assuming that every person posting in medium.com is a software engineer (and by engineer I mean an engineer, not some fuckwad who begs for github stars on dev communities).

The problem to me is that they fucking SATURATE the goddamn search results.

The same goes for finding an npm package for your need, because there are so many low quality packages it's saturated too, you have too plow this stinking pile of projects that have very low quality,
and there's not a really good npm finder out there. Half of them are dead, some look and load like shit, and npm search has a low barrier for good code.

Me on rails, OTOH "ok, I need this thing", I google that and I swear to [-∞,+∞] I find GOOD packages, well designed, no cookie cutter bullshit, no obscure marketing shit on the README.md, it is very clear what this shit does, and the api is designed for HUMANS.
and it actually takes very little time to know if there's no such package.

I don't have to read dozens of fucking my-fuck-blog.io (jesus christ, the io domain has become such a fucking joke, it got fucking abused to death, there are some cool sites out there using it, but my god, James H. Marketing likes to just absorb everything he can, and the internet was not going to be a fucking exception)

does all of this make sense?

Write a README.md

I didn't manage to win a Hacktoberfest 2020 shirt because I don't use GitHub anymore (and they require that apparently) - but I figured I might as well have a go at it.

echo "- an amazing project" >> README.md
git add devduck.png
git commit -m "update docs"
git push devrant feed

Pls like, comment, share, and subscrieb to CodeWithCondor for moar laif hakz :3

I made a README.md to a bitbucket repo that when a new dev comes in, he/she can refer to the documentation.

After a few hours....

"how do you run this application" 😩

README.md a file with Self written Joke...

$ ouch README.md
-bash: ouch: command not found

Happens way too many times. It hurts.

"README.md edited online with Bitbucket"

Debugging your JavaScript Code for 2 hours and trying out every imaginable solution because it works on the demo page but not your site... and then you find out the fking library had a bug and the Readme.md contained a cdn link to an old version and the demo page was up to date... arrgghh

Share your own useful terminal aliases here:

- grm=git rebase origin master
- gforbm=git fetch origin && git rebase origin master
- vm=vim Makefile
- idea=vim ~/repos/ideas/README.md (where I store all my programming ideas)

So, I've seen a github repo whose owner puts all of his code in an unformatted README.md file, no further files. I'm not sure if I should be concerned for them or scared.

Why are project/tool webpages so useless...?

I mean, whenever I hear of a new tool/project I google its name. Of course, its dedicated webpage pops up as result #1. And EVERY TIME I find them looking nice, but quite confusing, riddled with all the buzzwords, nice phrases, promises of a better tomorrow,... but I'm yet to find a tool's webpage that explains what's that tool for and how to use it at least half as concisely and clearly as that tool's README.md in its GH/GL repo.

I mean, I can read every single word in the webpage, look at every picture/diagram, every fancy gif and still in absolute majority of cases I have no clue what that tool does.
Then I go to its GH/GL repo, read the first 2 sections of its README.md (takes me what, 2-4 minutes?) and I know all I need to now about the tool.

What's the point of those fancy webpages apart from containing docs and an SEO-tuned link to a README.md...?

Useless waste of storage and computing power if you asked me.

The shit happens when the development is over and you have to face the team to ask them to create the README.md files to explain the repository.
Tears roll down when the code works well but they have to justify that.

I had a small .NET PoC project I wanted to upload to our git server. So added the project to version control using Visual Studio, meaning that VS created a local repository for it. Then I wanted to push it to the remote repository which were created by my colleague. This one was initialized with a commit (.gitignore and Readme.md), so I couldn't push directly. Googled a bit, OK then tried to fetch the remote repo, didn't help. Googled again, tried some "git push origin master whatever" stuff and then rebate, because nothing seemed to help.
OOPS where are my local files? WTF? 😣

Long story short: Experience in other version control systems is not enough or even dangerous when switching over to git. 😂

So I live in the south. And it’s been pretty cold here the past few nights. And now there’s a gaping hole in my laundry room and water going everywhere and a plumber who seems to still be reading the README.md file. And my kitchen is flooding. And my gf is losing her shit. And I’m drinking coffee sitting at my bar, checking emails. Somebody wake me up.

So I just spent all morning struggling setting up a project and getting it to run. My colleague sent me a screenshot of the documentation wiki, but didn't give the link.

*4 hours later looks at email for the Nth time*

Wait he did... that's not a wiki, that's Readme.md... this is in the repo link right above it!

I didn't need to checkout the repo so didn't open it...

Readme.md
*Todo: Add description*

>103 commits
>Last commit: a year ago
>Last commit on readme: 5 years ago

Slothful cunt, you don't deserve these 7 stars

You know the point where you should stop coding and think back about what the hell are you doing because the shit is getting crazy?

I just passed it whooshing at the speed of light, leaving behind me moments where removing readme.md changes the error being thrown and using `${someStringVariable}` gives different results from just using the variable - and I do not intend to stop.
I want to see the fiery hell of JavaScript and emerge on the other side victorious or a broken man. No other option.

!rant && load('epilogue');

So I saw my little brother yesterday and... Hell, I don't know. The addiction thing is less a thing that I expected, it's just that he can't find anything else to do than going on minecraft multiplayer servers and play, play, play. Gotta be honest, his life outside high school is pretty boring.

I mean, if I were him with this the few responsibilities, I'd be even worst than him, so how can I blame him?

Still, I had a big discussion with him where I tried to make him see what could go wrong if he fails (in a soft way), and helped him with french and english homeworks (french is our native language but a pain in the ass to learn 😁).

I do believe that saying all this "plz don't ruin your life this early plz" stuff had made him react, I just can't tell how deep and for how long. My main goal was to make sure that he won't feel helpless if he ever struggles for whatever reason.

However, since kids don't get shipped with a README.md, I just hope I did the right thing at the right time, and that he'll actually remember this discussion. But fuuuuck, he's 11 years old 😓😓

Side notes, I asked him about being a developer but it's pretty obvious that it was too early to speak with him about this. Might try again next year or the year after.

Thoughts ? I'll try to answee to you all

I always start a new project like: Copy & paste a similar project and edit its Readme.md file (and perhaps pom.xml) and delete all the other files I don't need right now 😉

Providing a nice Readme.md file with your open source project is never enough. You need to have a beautifully designed website for the documentation to go with it, oh yes sir!

Productivity hack - For me, it’s mostly a single word - planning. I wasn’t always good at it, definitely not yet a “master” of it, but breaking that proverbial elephant up into smaller pieces, and organizing a plan of action for dealing with them is the #1 productivity “hack” for me. Sorry that it’s not an actual shortcut, or anything…I personally don’t believe in those anymore. Complementary habits to this are thoroughly commenting code, having descriptive commit messages, file names, and variable names, maintaining documentation. Use that Readme.md. This is true of any project, even if I’m the only developer - never underestimate your own ability to totally forget shit.

README.md, is there any way in bitbucket/stash to customize the index markdown to be rendered other than README.md?

Anyone notice how fucking difficult it is to install software from GitHub... well for amateurs mostly. I went through pretty much hell to simply install a spotify playlist downloader script from GitHub. Had I not have had Python installed I would have had to download that too. You Install Python, Google a guide to get the pip command up and running. Download the software. PIP it? Then you find out it uses 3 custom libraries that have to be installed separately. Oh that reminds me, u still need an IDE to open the script and figure that, on your own. Then the script is super buggy, expected though it was still in development. I have no idea where I am going with this. Point is ppl need to get better with hosting code at GitHub. And it wouldn't hurt to include a guide to installation in ReadMe.md OR Installation.md. Ok am done now xd

Any tips for onboarding a new joinee to a couple-month old Django back-end project and eventually take it over, as my tenure ends?

The newbie is from a theoretical CS background and only knows very basic Django.

It's gonna be fine, I know; I'm just not sure how to go about handing over the project since even with coding best practices and detailed comments and a README.md, there's still a lot of stuff happening in the background that I know only because I've worked with it daily.