I'm the total opposite, my documentation is very thorough, my code looks like it was made by a monkey
Like my professor used to say: "Implementation is trivial, a trained ape can do it."
The trained ape is AI and it works really well.
Hold on i gotta glue my pizza and drink my piss every 24hours before i finish this comment.
(Im joking)
He's doing a good job :3
I prefer concise and accurate documentation than clean code tbh. The reason is that if the documentation stated that it should perform something with side effects a,b,c then I at least know what to expect. When contributing, this also makes it easier to implement something because we have the requirement at hand. Understanding shitty code is easier than understanding human requirements. Shitty code is the language we use to talk with a computer, so at least you'll know exactly what will happen.
I think the same, I often find that people overestimate their ability to write self documenting code and with the added mess of automatic formatters it often becomes hard to read and understand. In my department I am one of the few who actually writes comments and readmes that explains the reason behind some decisions. I am very junior, less than a year of experience, so maybe I will be able to better understand code that other people write in the future. But for the time being I write my documentation and my comments in a way that someone who doesn't know anything about the project can understand, because I hate having to call coworkers because I can't figure out how the project handles x and y (bear in mind that is also caused by Java "best practices" with 45 abstraction layers)
My best READMEs are the ones I write well before I've finished the code. The README bears little resemblance to reality, but it's the easiest to read.
Am I the only one who writes the Readme as I add features and do my commits.
Don't leave your homework until the end and cram away just before it's due.
Code every other day.
Code. Then review and document.
I also try to maintain my feature list in my Readme. Essentially my roadmap. Work my way down the list and write Code as features are added/updated.
As long as you provide a list of dependencies, you're cool in my book
Code is more or less deterministic, communicating with other humans using something like the English language - much harder.
Lots of communication is open ended and up to interpretation especially with things like incorrect grammar usage and/or slang
Take your time, get it as close to right as you can the first go around
Them: "Read the docs, this is a mature project!"
The documentation: "Coming soon!"
Me: "It says its coming soon."
Them: "Its open source, how about you contribute instead of demand?"
Me: "What?"
System notification: "Banned, lol"
This is eerie close to home! Completely illogical answers, yet somehow I'm to blame 🤨...
This is like when I was in school and spend half of the time using "word art" to set fancy titles
I'm the opposite. I will write literally a book of poetry for the tiniest feature to justify my pay raise at the end of the year.
I think a lot of people are kind of bad at written communication. It's not an easy skill.
Often at work folks will write twice as many words and clauses as needed. The Hemingway editor ( https://hemingwayapp.com/ ) isn't perfect, but I recommend they take a look at it.
That hit me right in the gut.
This is why my programs don't come with documentation. If you want to use them, the best I can do is a messy script that "works for me".
I pride myself on writing pretty good technical docs. But there's always a motivation hurdle at the beginning, that I have to get over.
Well, I for one am thankful you lot see so bad at explaining yourselves or I'd be out of a job
Love, the technical writer
I do both well but it never ends. 😟
