groundCode

I love SQL and I love databases. It's usually where I start any debugging - "what's in the database?" is what my first mentor always used to say when I hit a snag - surprising how often the actual data is simply not being transported to the user correctly.

I notice that devs who love their ORM of choice tend to rally against SQL itself, but I for one, would rather see a SQL statement - abstraction to an ORM is great of course because it keeps you in the paradigm of your chosen language, but it sucks because every time you move to a new framework, you have to re-learn how to create those complex pieces of SQL you've been using.....

I've just started tinkering with nitrous.io - I have to say it's very impressive and it makes the chromebook an actual usable device for development out of the box without any tinkering

I would so try these guys, but they only take money by bank transfer from what I can see which means, from the UK, it becomes very annoying.

great - not seen sailjs before - I'll give it a look see - thanks.

haven't actually used the rails api - I'll take a look cheers.

great reminder - I tinkered with firebase a bit a while ago - I'm not sure about the security implications of it though - it seems like (though I haven't actually tried) that anyone could grab your firebase url and start randomly writing objects to it. I know they have some authentication, but I haven't looked too closely into it yet - thanks for the reminder.

SEEKING WORK - Remote

UK based web dev, looking for small chunks of web development - most interested in Django and Angular work, but I'm quite prepared to dust off my Ruby, C# or even Wordpress development if the project is interesting.

I'm good with relational data and if you need someone to bounce a design off, I'm happy to be a sounding board.

I'm reasonable on the front-end, but not terribly original, happy to hack up html and css for you to predefined designs.

email in profile - say hi :)

I wonder how much of this applies not only to front-end javascript style stuff but also the backend server rich code. You also debug with a navigate to page, find the right code in editor, change, reload cycle. Granted, you miss out the "change values in developer tools in the browser", but it isn't so far removed.

there's the rub - once all the kvetching is done, coders who care enough can just dust off their editors and put something together.

way to go on the link baiting while at the same time dissing link baiting.

Is it me or does that look like something out of Tron?

James while John had had had had had had had had had had had a better effect on the teacher

Wake up Glass of luke warm water with a splash of lemon juice in it. 20 slow pushups Shower. Coffee. Wake up daughter and chat to her about the dreams she had last night :)

neat idea - kind of like asp.net mvc's ability to switch between the razor syntax and html automatically.

I like the tone of Doc's post as well, however, as a consumer, I don't think it's my problem to help a company out if they suck at serving their customer.....and if I don my entrepreneurial hat, the more AirBNB annoy people, the bigger the opportunity for a good competitor to pick up the pieces.

hmm defacto vs dejure if you ask me

what's your tech stack btw?

nice work

I'm a touch sceptical here - while I appreciate a noobs perspective whenever I'm starting something new, I prefer to see something that encourages best practice - a mix of experience through the eyes of a noob would be better in my opinion.

>> Also, it would be awesome if one of you would actually look at my git repositories before the interview and, you know, actually read my code. No, looking at a "repository summary" doesn't count.

actually, this I find is the biggest annoyance of all. Every company I've interviewed with over the last few years has said "show us your github".....so far, not one has actually looked at it. It's kind of like walking into an interview with a company that has a web-presence and saying "so, what line of business are you in?".

"using hair alone to distinguish heads is cheating" xkcd might disagree :)

well done!

well, last opinion from this peanut gallery - you've done a better job selling your startup on this thread than on your job add - the advert you have up there is prosaic and doesn't really express the passion you obviously have. Of course, just my opinion :)

I think this is certainly happending - my own first reaction to your job ad was "meh....equity over salary for a product that yesterday I didn't know existed".....

fwiw and from my perspective perhaps the problem is that you aren't advertising the salary you are offering - you want someone with significant experience - so we aren't talking about a recent graduate here, but someone with significant technical lead experience - experience most often comes with (at least a bit of) age and age comes with other responsibilities like family, kids, mortgage etc. Now they also have to believe in your product - so either they've already thought of it, or they need it sold to them.

maybe you need to go developer courting rather than waiting for them to drop through your door?

the site is giving me a mysql error :(

This is an excellent attitude - and especially in software development where there is often a not insignificant amount of coding done by the candidates. Several interviews I've been to have involved a full day of pair coding with various members of the dev team on current production code - it seems fair to at least offer something for the work.

and all your facebook friends will get up to the minute information on where you are and where you are heading to.

eh....companies say the darndest things.....I was rejected for a job a while ago because I preferred VIM over Sublime Text during my pair coding interview. Apparently, I didn't have the "right experience with their toolset". c'est la vie. Sometimes they just need "a reason" to not hire you because they just don't think you'd fit in.

well, we do need a great Javascript based blogging engine.

Nice post thanks - I'm about to tackle a fairly large Django project so it's always nice to see some best practice guidelines