5 ms·
So who the hell are Assembla and why should anybody care what they have to say? All I'm seeing here is a lot of misinformed ranting. Sure, there's a kernel or
by mindcrime 14y ago
So who the hell are Assembla and why should anybody care what they have to say? All I'm seeing here is a lot of misinformed ranting. Sure, there's a kernel or two of truth hidden away in there, but most good rants have that. I don't see that TFA makes any sort of interesting point or arrives at any real conclusion that's helping anybody make a decision though.
Oh wait, I'm almost 40, so I guess I'm too busy decaying into compost to know anything about this stuff. Never mind me..
- jschuur 14y agoNote the last line: 'If you are interested in new solutions to some of the issues listed above, please follow this blog over the next few weeks.'
- ryanmolden 14y agoYeah, I stopped reading at "Old People", and I am not even in that demographic. Wholesale discounting all wisdom in an entire segment of people with lots of experience in the very field you work in is rarely a good idea. I mean what's up with Knuth being so old? Some young guy should finish out TAoCP and show him how its done.
- mikegirouard 14y agoAgreed. It looks like the author was getting some heat for that point. http://blog.assembla.com/assemblablog/tabid/12618/bid/87899/Seven-Things-I-Hate-About-Agile.aspx#comment179715 http://blog.assembla.com/assemblablog/tabid/12618/bid/87899/... If you take him for his word, I'm sure he didn't mean anything by it (he says he's in that demographic). But I can't say that I'd let him off the hook that easily. Off-hand comments like this almost always come back and bite hard.
- protomyth 14y ago"Off-hand comments like this almost always come back and bite hard" If he has influence over hiring / firing, the first age discrimination suit is going to be fun. Stupid blog or e-mail comments give lawyers way too much ammunition in hostile workplace claims.
- ExpiredLink 14y agoAnd it isn't even true. 'Agile' is appropriate especially for young people who need an entertaining and motivating environment to be productive. The 'social' aspects make Agile appealing to most of them.
- PostAgilist 14y agoHere's my take on the "Olde Agile Coaches". Around 2000 the stock market tanked, and a lot of these old agile coaches were seeing their retirement go away. They didn't have any meaningful programming skills to bring to the workplace, but they needed some income. So what did they do? Become agile coaches! That's why most agile festivals look like an AARP convention, and why they drone on about Zen parables and radical 70s leftism. PostAgilist
- einhverfr 14y agoThat part struck me too. On the other hand, agile is the anathema of good data modelling and it causes productivity gains early on which lead to ossification and inflexibility later. This doesn't mean that there is now room for agile development, just that it needs some boundaries. One of the key areas we are trying to move with LedgerSMB is a solid, well-engineered database (not nearly there yet) with a framework for developing agile applications built on top of it. I suspect that as we get older we start valuing conservative, iterative processes more and that may be a part of the age thing. However, regarding data management it seems like we keep chasing the same lessons over and over that we have been chasing since the 80's. In the 80's it was relational databases vs special purpose ones. Then it was relational databases vs object oriented ones. The object-relational databases started to take off followed by a backlash. Now it is relational (dumb relational) vs object-relational (smart relational) vs NoSQL (object oriented databases 2.0). Yeah, this is a great idea. Let's speed up our development time right now by closing all sorts of doors for the future and ensuring that we have to handle legacy object models going back to whenever we started our project!
- jsight 14y agoI'm not really following your argument. Why would Agile shut doors to future change? It seems like one of the core tenets of Agile is to embrace the concept of change and willfully eliminate legacy models as you are able. I also think it's very naive to think of NoSQL as purely OODB 2.0. It is getting used for a lot of different things, that IMO are inappropriate for it. On the other hand, the movement is intended to solve a very different set of problems (DBs with various ACID levels depending upon scalability and durability requirements), from those solved by OODBs (API improvements that weren't), and traditional RDBMS systems.
- einhverfr 14y agoBut NoSQL is pretty much based on the idea that you store data from your application in a way which is close to the internal data structures, is it not? Since you aren't dealing with the ability to do on-the-fly, ad hoc transformation (the RDBMS and ORDBMS model) then you are limited more or less to a transactional state persistence layer, which is what the OODBMs's were intended to be. It doesn't really solve any of the problems that beset the OODBMS and other app-specific storage layer. It does solve all the problems that OODBMSs solved and a few more. I can't see why one wouldn't see NoSQL as essentially a continued outgrowth of the OODBMS movement to be honest. In essence for complex data it seems to me you have two choices: 1) Insist on rigidly mathematically defined input, allow ad-hoc transformation on output. Input is rigid, output is flexible, or 2) Be flexible with input, and allow some transformation both in input and calling on output. Input is flexible but output is pretty rigid. the first is an RDBMS, and possibly the array-native databases in the NoSQL world, while the second is the OODBMS, and the vast majority of NoSQL products. I think this fundamentally gets us to Stonebraker's 4-fold division, where on the left hand side you have simple data: With query = RDBMS Without Query = Filesystem On the right hand side you have complex data (nested structures and the like): With query: ORDBMS Without Query: OODBMS I don't think there is any question that the key problems of operating without declarative queries that can transform data reliably on data output (and this requires fixed schemas for data input) are the same whether you are dealing with OODBMS's or NoSQL db's.
- rada 14y agoYou think you have problems? I am 40 and one of those silly "girl" people: Pair programming is like those girls that go to the restaurant bathroom together. In Andy Singleton's universe, I should just go die already. P.S. Used Assembla on a client. Very subpar tool, IMHO.
- natrius 14y agoThis sounds like an allegation of sexism, but I don't really see it.
- rada 14y agoGeek Squad CEO, 7 Things I Hate About Tech Support: Irate callers are just like those black people who don't tip at restaurants. Now do you see it? (Obviously, I made that up. Apologies to Geek Squad and their CEO who I am sure would never say such a vile thing).
- thebigshane 14y agoAre you offended that the author is making fun of certain girls (the particular girls who go to the bathroom together) or that the author is making fun of girls (a group in which a subset go to the bathroom together, and you don't want to be associated with that subset)?
- natrius 14y agoNope, still don't see it. Women tend to go to the bathroom together far more frequently than men do in my neck of the woods. It's a stereotype, but I don't see how it's a harmful one to perpetuate, unlike your example. Would it bother you if people assumed you wanted to go to the bathroom in a group? If so, is this a common concern?
- lurkinggrue 14y agoOh you.