locopati

61 ms·

811.
The 21st-century textbook(radar.oreilly.com)
3 points by locopati 17y ago|1 comments
812.
by locopati 17y ago
And a well-stated counterpoint http://www.salon.com/news/opinion/glenn_greenwald/2010/04/26...
813.
by locopati 17y ago
The more things change the more they stay the same? MSFT: Always one step behind I am addicted to YC News Why to Not Start a Startup
814.
by locopati 17y ago
It's understandable though. That level of customization requires an increase in dev resources, QA resources, turnaround time, bugs. And the payoff only pleases a small percentage of your users who probably aren't making a purchase decision
815.
by locopati 17y ago
Spring source code - seeing how the internals connect comes up a lot when figuring out how to inject new functionality
816.
by locopati 17y ago
Every religion has some form of meditative practice (though some are less advertised than others - I never did hear about Jewish meditative practices until I was deep into Buddhist practices). And for the non-religious, there are folks like
817.
by locopati 17y ago
Flagging this because the story itself has no link to the free registration and the Palm dev site makes no mention of this. There is no proof and other sites I've found mentioning this are link bait (with irrelevant links in the story).
818.
by locopati 17y ago
1. Get flash working on every mobile OS other than iPhone 2. Transition flash creationg tools to HTML5 creation tools voila - relevance
819.
by locopati 17y ago
So again the question arises - why would you develop for a platform where the rules can change arbitrarily in a way that invalidates your work and possibly cuts into your income stream?
820.
by locopati 17y ago
I say this only partly tongue-in-cheek...an enterprise-grade IDE is one that you're probably not going to use unless the enterprise paid for it (that said, I'd readily shell out $250 on a JetBrains IDEA personal license if I went back to co
821.
by locopati 17y ago
Though it didn't become 'standard', the cross-platform aspect of Java's AWT/Swing APIs definitely gave it an early boost in uptake. I would also agree with the inevitable disagreement, that Java truly found its niche server-side (cross-plat
822.
by locopati 17y ago
Multitasking on the Pre works pretty darn well
823.
by locopati 17y ago
To run with your dog kicking example - that may be true of some cultures, does it hold equally in all? (an honest question that I do not have an answer to) are there other examples we can conjure that seem obvious but are culturally depende
824.
by locopati 17y ago
Step away if you can - take a trip, do something unrelated to anything you usually do - give yourself some space to clear your head and maybe you'll see what it is you really want.
825.
by locopati 17y ago
IDEA, svn, TeamCity (continuous integration), Jira (bug tracking), Confluence (info sharing), Basecamp (file sharing - though I wish we had nothing to do with it - it's generally painful)
826.
What’s wrong with extending the DOM(perfectionkills.com)
5 points by locopati 17y ago|0 comments
827.
Cloud Computing and the Internet(googleresearch.blogspot.com)
2 points by locopati 17y ago|0 comments
828.
by locopati 17y ago
Disagree a bit with "Anti-pattern 3: Overusing a technology". If you decide to use a technology, embrace it (even as you recognize the lock-in potentials). You often stand to gain more by making the most of what you're already more-or-less
829.
by locopati 17y ago
The dead ends of the first design usually inform the design decisions of a major rewrite/refactoring. So, in that way the line of evolution is unbroken. Even moreso, if you expand the metaphor from the evolution of an individual or a specie
830.
Ridley Scott On Harrison Ford As Deckard(youtube.com)
1 points by locopati 17y ago|0 comments
831.
by locopati 17y ago
The thing about efficiency is that efficiency from one person's perspective is not the same as efficiency from another's. It may _run_ more efficiently, but maintenance efficiency decreases and extendability efficiency increases. So, you'v
832.
by locopati 17y ago
The thing I rarely see brought up in discussions of automated testing is longevity. If you have a team of developers and the codebase is going to be around for a while, you need to grow tests over time so that the someone doesn't accidental
833.
by locopati 17y ago
Which is funny - just because you can work without being led doesn't mean you can lead others. One would hope you've gained some insight into how to work without being led and can apply this to others, but that's far easier said than done.
834.
by locopati 17y ago
With modern computer speeds and HD space, I've found 'which browser' to be a non-issue. Pick whichever primary browser works for you, switch to any other as needs arise. Chrome is my favorite (especially now that they've added extensions).
835.
Philip K. Dick on Blade Runner(philipkdick.com)
170 points by locopati 17y ago|88 comments
836.
by locopati 17y ago
One reply to address the others. Yes, Spring does not require iface proliferation - it just makes life easier when you decide you need different implementations of the same idea if you've committed to ifaces up front. YAGNI still holds true
837.
by locopati 17y ago
There are good reasons to use interfaces and to just accept the extra minor bit of work that goes with them. When using injection frameworks (like Spring), it makes life easier to reference an iface and have your concrete class plugged in a
838.
by locopati 17y ago
Nonsense. This might hold true for the individual-oriented website, in which case this could be thought of as the next evolution of blogging. When considering a content-rich corporate website, this article just sounds hyperbolic (in the fut
839.
by locopati 17y ago
Depends on how you look at it. I work on an internal CMS that has <100 users but powers large websites serving millions. The app is internal but the product goes to the external-facing websites.
840.
by locopati 17y ago
Easy for them to laugh - they don't have implement IE6 workarounds.

More ›