2,620 karma · joined February 11, 2019
ian at docstring dot dev
How about people decide to take action -- regardless of the consequences to themselves instead of worrying about maintaining the scraps they're fed in the process? Why is today so much different than yesterday that people don't want to risk their standing and their lives for their principals and expect it just to happen, to be given? All the whining is just theatre as far as I'm concerned until people start actually making the hard decisions and doing something at risk to themselves for what they believe.
Why do people seem so hypocritical compared to the people during those decades you mention?
The owners of Coinbase made a stand for what they believe in, I support that. Maybe the otherside of the table needs to take that collective action they talk so much about instead of talking.
Edit: And you know I'm not sorry but I just don't feel bad for office workers bitching about their jobs. I feel bad for the front line workers, in the stores in the warehouses in logistics and shipping. They actually have real gripes to contend with being physically worn down everyday yet we lump the person sitting in their office chair reading reddit for 8 hours with these people actually killing themselves to get you a package a couple hours sooner.
Note: This isn't aimed at you directly but very much what I feel is the superficialness of many movements today.
http://phrack.org/issues/1/7.html
So it has it's counter culture roots.
Edit: Which I actually just noticed is from 2600 so I guess the point stands?
And actually with most index funds I don’t even have to type, I just click a few buttons. They’re not managed by the end user.
Crypto isn't quite the same as an index fund, but many people use crypto as an investment with expected growth and they've been right so far.
Here's to the next wave of kids that pick up programming from platforms like these.
I read the article FWIW, it didn't particularly convince me. I think even writing things in the style of functional programming, if that's what we want to call it, still makes it easier to reason about the code. Confining side effects to hooks also means there's only one place we have to reason about having non pure consequences.
We think the best way to keep documentation is along side code and in code, as a docstring. Both to make it more likely that it's updated and also because writing documentation along side code makes it more likely to capture little details that might be missed downstream.
For long form documentation like design, architecture and business considerations writing markdown files and keeping it alongside the section of code it documents works well and is pretty common.
Keeping the docs deployed and updated is a different story and as a lot of people here are doing they're suggesting building CI pipelines to do it.
We decided that's messy so we link in directly to the development flow both with git hooks and IDE integrations.
We then use Github to link what documentation should be allowed to be managed by us and we're working on integrating SSO to manage user onboarding and permissions.
I also know this empirically because I was a half a pack a day smoker for a few years and I have never been more anxious, it was what drove me to quit.
You feel relief shortly because you're satisfying the addiction but at the general level you have more stress.
The thing is that is an issue of community, because Ruby does have an FFI and there is really nothing stopping people from building libraries similar to how they're done in Python, calling out to C. They just didn't.
Uber's margins have always been super thin, I would imagine this makes them squarely unprofitable in the Dutch market.