sandal

10 ms·

31.
by sandal 11y ago
> The missing piece of information here is that while the quantity of items may be increasing, it is likely that the severity of those items is decreasing. The truly urgent major issues get identified and fixed early in an app's lif
32.
by sandal 11y ago
Good insight. I didn't split the categories for the report (nor did I distinguish in the essay) for pretty much exactly this reason.
33.
by sandal 11y ago
That's absolutely right... on its own, the graph tells you nothing at all. However, if you know for sure that there are tough problems going on (related to growth, limited dev capacity, code quality issues, etc), then having well-funct
34.
by sandal 11y ago
This is pretty close to what I ended up doing. I've repeated this process elsewhere too, both for other companies and on my own projects... though the example shown was among the most severe. In the essay, I'll try to be a bit mor
35.
by sandal 11y ago
I wrote this essay. I linked the Reddit thread because there are some good thoughts there, but I'd also love to hear what HN has to say! https://www.reddit.com/r/programming/comments/3z1pfp/the_sad..
36.
The sad graph of software death(tinyletter.com)
106 points by sandal 11y ago|66 comments
37.
The joy of a collaborative writing process(practicingdeveloper.com)
2 points by sandal 11y ago|0 comments
38.
A response to Ron Jeffries(practicingdeveloper.com)
2 points by sandal 11y ago|0 comments
39.
Inspiration vs. Grind(practicingdeveloper.com)
1 points by sandal 11y ago|0 comments
40.
The /now page movement(sivers.org)
2 points by sandal 11y ago|1 comments
41.
by sandal 11y ago
Hi, I'm the author of this post, and have shared it on HN in hopes of getting your feedback! This advice isn't (or at least shouldn't be) anything new to those of your building your own businesses. However, the idea of "
42.
Building a feedback loop (Writing a programming book, episode 5)(practicingdeveloper.com)
2 points by sandal 11y ago|1 comments
43.
Effective Code Reviews (a Programming Beyond Practices Series)(tinyletter.com)
1 points by sandal 11y ago|0 comments
44.
Everything Sucks at First (Writing a Programming Book, Episode 2)(practicingdeveloper.com)
7 points by sandal 11y ago|1 comments
45.
13 software design articles for 13 weeks of study(blog.practicingruby.com)
1 points by sandal 11y ago|0 comments
46.
Safely evaluating user-defined formulas and calculations(practicingruby.com)
2 points by sandal 11y ago|0 comments
47.
by sandal 11y ago
Hi, I run practicingruby.com and am the one who set up this Kickstarter. All the money is going to contributors, and the materials will all be released under CC BY-SA as soon as they're published. In addition to a $500 honorarium, I wi
48.
by sandal 11y ago
If that's the case, I'm curious to hear your thoughts on two things: 1) If you don't think that gender diversity is strongly related to education, why are you participating in a group that's designed specifically to addr
49.
by sandal 11y ago
> People who are good at writing educational materials need to be paid to do this, because it's hard and takes a long time. I don't see any possible objection to this. I have been paid to do this for five years with practicin
50.
by sandal 11y ago
I feel like I addressed this very directly in the article, but I'll repost the main points of "what's wrong" here for further discussion... This economic model is so ingrained in our DNA, that we hardly ever question it
51.
by sandal 11y ago
My own interpretation of this is that since the commercial sponsorship and advertising supported model is a race to the bottom, we need to be looking at alternative models that are focused on social benefit first. We do have Wikipedia. It w
52.
by sandal 11y ago
I actually may plan to do some feedback with cancellations in the future, but "you not publishing for half a year and giving everything away for free" seems like a pretty compelling reason to quit a service. However, the main feed
53.
by sandal 11y ago
Maybe! Although (for better or for worse), it's a word you rarely hear in the software industry.
54.
by sandal 11y ago
I've been focusing only on timeless content (for as realistic of a definition of "timeless" as technology allows) for Practicing Ruby, because I think it's more compelling and sustainable as a work for the benefits of th
55.
by sandal 11y ago
Very thoughtful feedback, thanks! Related to your last point: > How about finding ways to compensate those who already produce valuable content in the commons, so they can have more time to do what they already do well? This is actuall
56.
by sandal 11y ago
Thanks for the feedback! > 1. Community is absolutely a weasel word when you're using it to lump together people from many different backgrounds and speak on behalf of them, or to act as if your particular sense of identity is repre
57.
by sandal 11y ago
I'm the author of this essay. Happy to discuss this topic with anyone, even if they disagree with my points!
58.
Help Practicing Ruby gain new contributors(kickstarter.com)
1 points by sandal 11y ago|0 comments
59.
by sandal 12y ago
If you want to just see an example of building a parser, you could check out "Parsing JSON the hard way", which uses Racc: https://practicingruby.com/articles/parsing-json-the-hard-wa...
60.
Four great articles on designing, developing, and maintaining software systems(elmcitycraftworks.org)
3 points by sandal 12y ago|0 comments

More ›