2,803 karma · joined June 19, 2010
AFK: car fanatic, splitboarder, hiker, wannabe alpinist, metalhead, whisky enthusiast.
chrisrikli at gmail
I'd grown up futzing with code in the 80's (AppleBASIC, a bit of assembler). Turbo Pascal, ANSI C, in the early 90's. I'd started crunching through Ivor Horton's book on Visual C++ in 2000.
My girlfriend's (now my wife's) employer had an ecommerce website that was written in this thing called PHP and it kept throwing errors, something about MySQL. Figure out it was hosted on this "Apache" thing.
Bought a SAM's Teach Yourself in 24 Hours on LAMP, spent a month digesting it, fixing the issues with the site in the meantime. When I was done with the book I wrote my own ecommerce platform to replace the one they had (I did all this for no compensation, I just wanted to learn).
Took programming gigs off of what was then called "rentacoder.com" working for almost nothing to get experience and built a portfolio.
The next year, 2004, a big auto parts company in town was looking for a "webmaster." I leveraged having built an ecommerce platform from scratch into that job. I was all things internet for them (except graphic design). Wrote code for their ecomm website (old school ASP.NET), did SEO/PPC marketing, came up with email campaigns, integrated with their ancient PICK-based inventory system, used NLP to detect tone in customer support emails before that was something you could farm out to Google, etc.
So...the replicable aspects of that path, excepting luck and right place right time:
1) Dive deeply into a challenging language. C++ wasn't for the faint of heart then and although it's been years since I wrote any I'm sure that hasn't changed. I'm a much better coder for having had to deal with the obtuseness of C++. Pointer pointers, anyone?
2) Do work until your skillset and portfolio represents enough value to someone that they're willing to pay for it. So much of my early work was garbage anyway...hell my SAMS book on LAMP hadn't covered SQL JOINs, so I was doing queries and iterating through the results and running more queries!
3) Build something that non-developer can understand and connect to. I was able to talk about the ecommerce site I'd built, how I'd integrated with PayPal, demonstrate the UI, etc, to the people that hired me. Had I been presenting something more esoteric, like the time I had to figure out endianness to decode a data file and get it into a MySQL database, I'd have completely lost them and likely not have gotten the job.
I've since applied this logic fairly universally and I'm going to apply it here: SpriteBox does not exist to teach kids to be great coders, it exists to sell copies of SpriteBox.
The challenge of text undoubtedly is a blocker to the sales of SpriteBox.
I do not believe that it is a blocker to a kid becoming a great coder.
Coding absolutely requires a high level of comfort with abstraction. It requires the ability to mentally model abstractions, maintain relationships between abstractions, and make a (sorta) concrete reality of those abstractions.
Coders must be able to make intuitive mental leaps based on disparate and distributed data. Often the solutions that coders come up with are based on little bits and pieces of the puzzle based on SO answers, documentation, blog posts, example code found on github, etc. The solutions to tough problems are rarely found in a single neat all-explaining resource.
So... if a kid is having trouble with text I would candidly posit that the kid may not have the ability to deal with abstraction that coding requires. Not a problem for the industry as there are already enough coders who have this issue, but it creates a sales problem for SpriteBox.
EDIT: typo, clarity
It's a good question...but I think only Alex could answer that question for himself.
I can say that the feat would not be as impressive because fear management and mental control are a huge part of climbing. As you move from top roping to sport leading (clipping your rope to preplaced hangers) to trad leading (placing your protective gear into cracks or other features in the rocks and trusting it to hold you if you fall) the risk increases and the fear start to become more of a factor.
I've seen climbers that have been perfectly physically capable of making a move but have been so gripped with fear that they couldn't move (and I've been that climber). I've done multipitch climbs (where you climb multiple rope lengths) where at the end of the climb I'm completely exhausted. Not from the physical exertion, but rather from the mental exertion of keeping fear at bay and from the sheer focus that climbing takes.
And honestly, I can see the appeal of free soloing. Protective gear is a giant pain in the ass. It's heavy. It's noisy. On lead the weight of the rope can become a very present annoyance, especially if you're on a long pitch. I would love for there to be the magical robot of your hypothesis that allowed me to climb without all that shit. But such a thing doesn't exist and my personal risk envelope has not expanded to free soloing (nor will it).
What the author was saying was compelling up to the point she admitted she couldn't code.
Non-code contributions have value, however if you don't have the engineering understanding to grasp the full context of a project your perspective likely isn't going to be taken seriously.
With all of the resources available now to learn to code, I just don't have any sympathy for her. At all. She doesn't need to be contributing to every project in order to have an opinion worth considering, she just needs to be able to demonstrate some level of development chops.
Stop talking about it and start doing it. The resources to do so have never been more readily available.
I felt it to be a strong culture of comparison. Comparing job position, comparing employer, comparing income by implication. Ugh. Just not my ethos. I lived my 20s in that mindset and it's a zero sum game.
I also felt like it was so damn expensive to live there that even people making great salaries were constantly under pressure. To me, a pretty relaxed Midwesterner, it just seems like everyone is on edge.
The other thing that grated on me was the "funding equals success" mentality. So you got funded. Big. Effing. Deal. Go turn a profit.
It just isn't my kind of vibe. Like I said I'm a Midwesterner, the culture I grew up in is one of frugal living and understated successes.
I'd rather have seen the money wasted on her spent boosting the publicity of female comics that are actually, you know, talented. Start with Tig Notaro.
I don't know a single person, and I know a good number of Trump voters, who is opposed to legal immigration. What many people, myself included, are opposed to is the illegal part.
Yet I consistently see this stance twisted to mean opposition to all immigration. This conflation is patently ridiculous but it makes for a nice straw man.
(edited for clarity)
But yup, around the first part of 2015 what used to be a one ring call to connect with an expert became 5 minutes, then 15, and a couple weeks back I waited 45 minutes to talk to a Linux tech. Unfuckingacceptable, not as a "managed" customer paying an extra $100/mo and $0.12. We've slowly but surely moved clients to other hosts and I can count the servers still at Rackspace on one hand and still have fingers.
I was with you right up to here. This part...nope. Government should most definitely not be the arbiter of bias.
Edit: I'm dead wrong. :)
I am not an ultra runner or even a marathoner, I'm a wannabe alpinist. But the podcast is incredibly informative for anyone who is going to be under movement for more than 4 hours. I have learned more that has helped me in training and on hikes and climbs from this podcast than any other single resource.
"I feel how weak and fruitless must be any word of mine which should attempt to beguile you from the grief of a loss so overwhelming."
Some pivots will irrigate a quarter of a section, but even this is rare. The standard pivot with a corner system [2] and will cover 152 acres out of a 160 acre field. Roughly a quarter of a one mile section.
[1] At least in Nebraska, I don't know about the rest of the country/world. My source is my brother-in-law a 5th generation farmer.
[2] Basically a swingarm that extends the effective length of the pivot for better corner coverage
Edit: hit enter too soon.
That would be fairly (ok, wildly) impractical.
Most of the roads are gravel, which means that maintenance would be a nightmare. Road graders aren't great at keeping the blade level on turns. So you'd get buildup/digout at every turn.
When it rained you'd get run-off and erasion. Which makes me think of drainage, wow, with the water making 120 degree turns roughly every half mile you'd get some serious washout on those occasions when we get 2" dumped on us in what feels like 10 minutes.
Zig-zagging across the country with a 24-row planter in tow would be a giant pain in the ass (you plan your route minimize the number of turns you're making). Would be a pain driving a combine fitted with a 12 row head. And at harvest the trucks taking grain to the elevator or silos would be doing the same zig-zagging.
It's not like the grain that's outside the obvious circle doesn't yield. It get irrigated via runoff as well as powerful sprinkler guns at the end of the pivot arm.
Credentials: grew up farming in central Nebraska, married into a 5th generation farming family. Thousands of acres, all centrally irrigated via pivot.
Edit: Didn't want opening tone to sound argumentative/condescending.
Edit 2: Just thought about power lines. They'd have to zig-zag too. Which means the pole on the zag would have lateral force vectors acting on it, so it would have to be reinforced/anchored. When the afore-mentioned washouts happened, down goes pole and powerline.