The Cydia Store disagrees.
I'm a software developer and I'd love to develop for ground-breaking new hardware like this.
1,411 karma · joined April 8, 2011
The Cydia Store disagrees.
I'm a software developer and I'd love to develop for ground-breaking new hardware like this.
You're completely behind the curve. People have been using Dropbox to do their work from its' very early days. This is nothing new, they're just making it more "official".
I found your post very insightful until you brought in your standard and (imo) off-topic closed-allocation rant.
Except for the part where you're stuck trying to decipher existing Emacs Lisp. With Python I find I can express what I'm trying to do without too much thought.
example:
>People spent time with each other.
They still do. Just because you're in a relationship where that isn't the case, doesn't mean technological advancements are to blame for it. I still have amazing engrossing conversations with people who are as embedded in technology as I am.
Isn't that awesome? I can use the thing without ever understanding what it does :) I'm so glad my car works without me ever having to know anything about how it works. I know it requires some form of money (gas) to work. That's it. Money in -> Transport out. Perfect.
The linked post never proclaimed no one "will ever understand" compilers. That's just what you're reading into it. You try to get upset at it, so you do. It merely proclaims that compilers are incredibly complex, which is the nice thing about them. If compilers were stupid they'd be a lot less useful.
Be humble -> People react positively -> Act more humble as a consequence.
In the end you get frequent "humbleness" injections like in his writing. Nothing wrong with that, just interesting to see.
However I don't agree with glorifying old codebases or putting them as "equal" to working on new stuff. If you're happy doing that, then fine, no one's going to stop you from doing it, but I do think that in general, given the choice, almost anyone would pick building something anew over working on a legacy codebase.
I could never imagine someone on their own accord, going by themselves into a 30-year-old codebase and refactoring it, just to make it "look nice". On the other hand people constantly build new stuff (too much of it really). I think it would be fine to admit that working on new code is more desirable than working on old code. Sometimes the latter needs to be done, but I think most programmers are happy to avoid maintenance work when they can.
"Hi, CEO of Heroku here.
Sorry. We've been misleading customers and only telling the truth when pressed-hard for years. We've created this financial model for all of our customers who have been overpaying on dynos because of our shitty routing and will be reimbursing them based on that.
We've also rolled out a second dyno-tier, called "dyno with non-shitty routing". It's 10x as expensive, but at least we're being honest about it. All current customers will enjoy our "dyno with non-shitty routing" for the price they're currently paying for the next 2 years. Enough time for them to migrate away, like any reasonable person would expect them to after this."