573 karma · joined February 15, 2009
Eventually, some bug comes up, and you need to peek at what queries the ORM is generating, and then peek at what is actually in the database, and etc.
But at this point, you have to not only know what's going on with your particular SQL dialect, you also have to know syntax hoops for whatever particular ORM you're using. Instead of even just language + SQL, you've got language + ORM + SQL , which is even worse for focusing on whatever I was trying to build in the first place!
Whereas, with a NoSQL solution, you're (probably) dealing with JSON, which works nicely and reliably and transparently in pretty much every language ever.
Personally, I'm drawn to Mongo, etc. because I can develop in my language of choice, and not have to write/debug SQL of any dialect to store and retrieve my data.
Developing with mongodb is _lightning fast_ and holds up very very well. If you end up with problems, switch to SQL later!
I don't think a lot of these people hating on the nosql projects have actually tried building something with them.
flame on? maybe you don't understand because your startup doesn't have a lot of traffic?
you even admit that you don't really understand how the nosql dbs even work!
NoSQL is faster to develop/prototype with also, since you only need to understand json dictionaries.
So your shit ships faster, and scales cheaper.
I have never in my life had to deal with an unused gift card. I.. don't know anyone who has this problem, I've never heard anyone reference it.
Yet somehow, there are five funded companies in this space?!
Mahalo is not particularly interesting, not particularly evil, he doesn't really do anything, and yet - we keep talking about him and putting his shit on the front page of hacker news.
It's a mediocre aggregator/linkfarm, with some mechanical turk style incentives for humans to contribute, and a nice chunk of $ in the bank. Just ignore/mock him for another year or two until the funding runs dry.
A real architect can build his design. An architect has to learn to build before she learns to design.
I just think that's a profoundly different thing
and i think there's some website where you can pitch a job idea and they'll give you $ to start a company.
hilarious, insightful and prolific
(Which is a big part of the reason I choose to work as a coder ;)
I am saying that a top notch architecture school is much more demanding than an equivalent engineering school, from my experience. I say that having lived with ME and CS roommates, at U of Michigan, while I was in school.
I think that if you are competent enough to build any part of your project, but can still understand the big picture and have some appreciation for elegance and beauty in a design, you've got the basic idea.
I think architects are also better trained at accurately sizing up time requirements and logistics, for an entire project, and at being aware of time and money and arbitrary client constraints.
And I think architects are trained a lot more in presenting their ideas to hostile audiences, which gives a lot of insight into taking and giving criticism, and finding the flaws in your projects and designs before they ever reach a client.
Sketch out the big picture, take care of the trickiest details, wrangle your underlings into doing the rest.
Architecture school is very hard, mentally and physically. The perk is the weird mystique that society gives us.
No, not telecom high, but it does take a pretty significant amount of hardware to index and deliver that much data. No?
"Without search neutrality rules to constrain Google’s competitive advantage"
make anyone else immediately think, "Atlas Shrugged"?
Sexy wallet though!