I love to collaborate - at the whiteboard or during design review. When it's time to code, however, I'd much prefer to be left to my own keyboard.
146 karma · joined July 22, 2009
I love to collaborate - at the whiteboard or during design review. When it's time to code, however, I'd much prefer to be left to my own keyboard.
int32_t result[my_array_size];
relies on C99 support, which is not necessarily ubiquitous (especially in embedded device work). At the very least, many compilers make you explicitly enable C99 support.If it's becoming accepted practice for companies to dismiss interviewees early, then I see no reason that interviewees should not be able to do the same (politely and professionally, of course)
In my recent experience, for example, I devoted at least 15+ hours to the process and got nothing in return (no meaningful feedback or criticism). There is an obvious benefit IF you get a job offer you are happy with, but it's all too easy for companies to cast a wide net when interviewing and waste lots of hours of my time. At a minimum, I'll be more leery of inefficient interviewers in the future.
Perhaps another distinction Uncle Bob could have made is between hidden technical debt (i.e. the mess that PHBs refuse to acknowledge) and acknowledged technical debt. Uncle Bob is talking about the latter, where everyone agrees some trade-offs were made up-front.
The former is much harder to wrangle because, so often, the decision makers are unwilling to accept that it even exists ("well, the system's working fine, isn't it!?")
The lowest-budget solution is simply to store the third party and open source projects in a reliable network file share (NFS, samba, etc). Then you can either sync locally or just build/link directly against the mounted file share.
It's also important to keep each project in a directory structure that includes the version number in the path (e.g. /nih_libs/boost/1.44.1/...) so that you can easily drop in a new version and start using as needed on a project by project basis. I'm always amazed how many places neglect this step and then have nothing but pain when they want to upgrade to a new version of a lib.
Really? It wasn't so odd back in 1996 when the Netscape web server supported it. To be sure, V8 and node have wildly better performance characteristics..but the idea of js on the server isn't exactly new: http://en.wikipedia.org/wiki/Server-side_JavaScript.
Well, here's my quick answer: pick the one you think you can get going most quickly with. It's better to just get something started that does something than to spend 6 weeks configuring the latest/greatest web framework before you can get started actually developing your app.
If, on the other hand, you want to use this project as a way to play with some particular framework - well, then you already have your answer: use that one.
Don't fret too much about your initial decision. Your app is going to grow/morph over time. At some point, you might "outgrow" your initial choice of framework. No worries - by that time, you'll probably have learned a thing or two about what you really want the app to do. A major refactoring phase is an opportunity to change frameworks, and it's not always as painful as it might seem at first.
So, yeah - that's a non-committal answer. But, that's because I think the focus should be on getting something running quickly. If you have the ASP.net stack on your system already set-up and you know how to get started, fire away. If you're starting from a blank slate, then poke around the documentation for some of the major frameworks (rails, django, cake, etc..)...and have a look at the "quick start" guides. Pick one that seems to make the most sense to you and that you think you could get up to speed quickly on.
Once you picked your framework to start with, head on over to StackOverflow and peruse the latest questions for that framework. It will give you an idea what kind of issues people are dealing with and what kind of help that community can provide. For each framework, there are other more specific forums/communities, but SO offers an easy way to have a look at a cross section of users/issues.
good luck!