Your hard work IS paying off! ๐
Chibird storeย |ย Positive pin clubย | Instagram

Product Placement
sheepfilms

โฃ Chile in a Photography โฃ

Cosimo Galluzzi

titsay
todays bird

oozey mess
Not today Justin
Keni
Sweet Seals For You, Always
Misplaced Lens Cap
Aqua Utopia๏ฝๆตทใฎๅบใง่จๆถใ็ดกใ

โ
noise dept.
art blog(derogatory)
TVSTRANGERTHINGS

ellievsbear

blake kathryn
seen from Australia
seen from United States

seen from United States
seen from United States
seen from Brazil

seen from Germany
seen from United States
seen from Lithuania
seen from United States

seen from Brazil

seen from United Kingdom

seen from Malaysia

seen from United States

seen from Canada
seen from Belgium

seen from United States
seen from United Kingdom

seen from United States
seen from United States

seen from United States
@acbdev
Your hard work IS paying off! ๐
Chibird storeย |ย Positive pin clubย | Instagram

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch โข No registration required โข HD streaming
I don't exactly dislike writing documentation, and I don't at all mind the effort and thinking that it takes, but I just hate how much time it takes to write documentation even remotely well.
And it's frustrating because in a very important way, the person who wrote the code is the worst person to document it. So the time inefficiency is very high.
The best person to document software is someone eager to get an informal explanation from the person who wrote it.
When I have just written a piece of software, I am literally mentally as far possible from someone who needs the documentation. I know exactly what my software does. I don't have any questions. All features, quirks, and caveats of the interface and any side-effects are equally unsurprising.
To assume the perspective of a person who actually needs to be helped by the docs, to see what could be better with the docs, is far more expensive to the fresh author than anyone else.
I often have set my software aside long enough to start forgetting what it does, or go through several rounds of trying to explain it to others, before I can see what the docs need to be - any docs I previously forced out of myself are usually revealed to be bad once that happens.
I do seem to be getting better at that... the first pass of README for my Python macaddress library still holds up after a few years, I think.
But even so, it's exhausting how time-consuming it is. Does everyone have to take this long? Probably not, but it just rarely comes easy for me. I have to write stuff, re-read it a little bit later, a little fresher, while trying to put on a different mental angle, see flaws - the misinterpretation potentials, the omissions of why it matters, spots where detail or focus is unnecessary, engineer a different wording or examples, rinse and repeat.
And it feels frustrating to not spend that time now, to just put it aside and not force it until one day suddenly the explanation flows... Because documentation is the main step between done and Done - between having a thing that works and any actual benefits of a having thing that works which involve other people. Because if I don't force it, something really nice like git-cotree will just sit indefinitely - sharing things doesn't actually accessibly share it with anyone unless you also explain/present/demo/market it.
Exactly what I was talking about earlier ๐๐พโค๏ธ
Reading documentation is cool actually.
YouTube people can be really obnoxious sometimes.
Learning to read documentation is an ESSENTIAL skill, do not underestimate it โจ

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch โข No registration required โข HD streaming
What a place work on my Swift Playgrounds project โฆ hopefully I will have something ready for beta soon ๐ค๐ผ
Git Workflow ๐
credit
It's very quiet in here.
Apple: iMac G3, Ruby Red (2000)
Breakfast at the Spotify NYC office. I love this place and I love working here ๐
I have just come back from a conference, so today I will spend some time writing up my notes and sharing knowledge with the team. I also have some code to review for an open source library that my team maintains!
Feel free to ask me anything about a career as a software engineer, Iโm always here to help ๐ช

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch โข No registration required โข HD streaming
Mohawk Data Sciences System 2400, c. 1973.
FINALLLY! I've been looking for a way to say this for ages, THANK YOU!
Feel the need to point out that this has been said before, and better, in Penelope Scott's "Rรคt."
So fuck your tunnels
Fuck your cars
Fuck your rockets
Fuck your cars again
You promised you'd be Tesla
But you're just another Edison
'Cause Tesla broke a patent
All you ever broke were hearts
I can't believe you tore humanity apart
With the very same machines
That could've been our brand new start
It feels natural for me to come back here, as Twitter absolutely implodes.