[1] http://www.typography.com/ask/faq.php#Ft_10 - choose #20
1,278 karma · joined December 17, 2009
[1] http://www.typography.com/ask/faq.php#Ft_10 - choose #20
1. Debug and refactor. Early on, I'd stumble through creating a script. It was usually write three lines, see if that worked, repeat. I didn't plan ahead enough, and by the end, my code was just layers of ideas tightly held together by a file name. This aggravated me, so after I'd get my scripts working, I'd completely rewrite them from scratch, making improvements where I saw them, simplifying code wherever I could.
I've learned more debugging (generally my own) code than I have from any book or teacher.
This was a lot of time spent, but eventually I could start seeing ahead and could make those changes in real-time as I was writing them. I'm not saying that I don't go back and refactor my code now, but when I do it's usually to fix things for speed or bugs, not for code cleanliness.
2. Plan ahead. I know some people that write out the entire shell of their program -- all of the functions and names and comments of what each function will do -- before ever writing the actual logic. I never had the patience for that, but you can still plan ahead.
Take a look at what you're trying to accomplish, and find the areas where you know you don't know what you're doing. Do a bit of research on those points. See what others have done, there's a really good chance you're not the first person to do those things. If you're still not sure, ask for help. The community is almost always willing to help.
3. Clarity over cleverness, always. I always take the road that will be more easily maintainable in the long run rather than the code that will work the fastest. (But, you know, if you can hit both at once, awesome.) I like breaking things down into simple bits. All of my functions are either only accomplishing one task, or are strings to those one-task functions put together to do something complex (but is still considered one task).
4. Learn, practice, learn, practice, repeat. Don't just stick with one language, branch out and see how other languages tackle similar problems. Take a look at code that you thin is better than yours and figure out why you think that. Take a look at code that's worse than yours and figure out why you think that. Write those things down and keep a list next to your monitor. Review them each time you sit down. Put them into practice. A lot.
5. Perspective. Take a look at your own work from 2-3 years ago and look at how far you've come. You've probably covered more distance than you think. Even if you're not 100% happy with where you're at, the progress will be reassuring.
6. Finally, stop worrying about it. Think of some people that are really good at what they do: professional athletes, professional plumbers, professional anything. When they're in the clutch moments, they're not stressing about how what they're doing looks, they're in "the zone," their mind lets go and instincts take over. Programmers develop those instincts too.
You're probably much better than you think, and you're only going to get better every time you program. :)
HTML5 is just HTML, and unless that fundamentally changes, it should work "forever." JavaScript too, again, unless you're linking to frameworks hosted by companies that later go out of business. JavaScript usually adds, but rarely takes away.
The look of your HTML site 10 years from now may look more outdated than your Flash site does, but as long as we're all still around, I'd wager that they'd both still work, provided Flash player is still a thing.
Not that that's of much help, but it's interesting to know that not everyone responsible for it was behind the name.
For me, I think I prefer reading his writing. While also lengthy, it's been edited and trimmed back. It focuses on just the metaphors that full apply.
(Although for long car/train rides, Back to Work is fantastic.)
These days it seems like leaving GoDaddy is the cool thing to do. If a company's marketing tactics or a CEO's out-of-office actions put you off, then that's one thing, but as for the product itself and how well it performs: GoDaddy performs as well as anything else I've seen for what I consider a fair price.
(Their hosting, however, is a totally different story…)
(I know there's Boxcar, but I've seen friends have trouble unsubscribing from Boxcar effectively, that's a bit worrisome to me however fringe case it may be.)
Either way, good stuff.
For some reason in my mind I had always assumed that open source type things have to be done for free: the building, the support, etc. Seeing someone doing something others helps put that in perspective.
Or, in short: I wish I was smarter about it and more business-savvy.
Netflix may have a ton of streamable content, but if you have to approach it from a non-specific point-of-view, it's questionable how valuable a service it is for people like me.
One person that disagrees with something (for whatever reason) probably won't be enough to abandon research on it. I'm cool with taking a look at what is there.
This doesn't mean that if I bought an equally priced (and benchmark-ed-ly faster) Windows machine that I'd be happier. I would basically just have a machine that is a little bit faster with an interface that I strongly do not prefer. Saving a couple bucks in this way would not make me happy.
These comparisons seem great for people that are truly apathetic to their interface, environment and workflow... the only people I know that fit that description are not playing Call of Duty.
I'm not saying that Mac is better than Windows. I'm saying my preference is a Mac, and with the perceived price-per-power that I normally feel with Macs, I feel like I got a great deal. It's quick, the battery lasts about twice as long as I'd ever need it to, and I'm happy with my purchase.
And at the end of the day, that is what matters.
As others have said, just having a standard upload button would work nicely. Same with click-to-copy, there doesn't seem to be a way to get the URL without Flash. Detect Flash, and then add in the "goodies" like that, otherwise the interface is much less usable.
Other than that, when Flash is installed, the interface is nice and easy to use. It's a great start and I look forward to more!
Some may prefer the N on 1, but for me I see that I can get a lot more out of people just by myself. People are more relaxed, and I can get a feel for who I'll be working with, not just the person that showed up in the interview.
After all of the 1 on 1s, we'll sit in a room and talk about what we learned and how we felt. Everyone gives a gut-reaction rating and go from there. It takes more time and resources, but for us our hire-quality is... well... higher.
Simple to use, pretty good stuff.
However, it was still hard to know when we were and weren't using data. There are options in the iPhone to turn cellular data on/off (which needs to be on to use GPS), and not to allow data roaming, but I still was unsure of when it was being used.
Our bill ended up being $217 for the month. It could have went much worse.