Yeah 100% this. Comparing a graph data model and a relational data model while obviously possible isn't really all that fruitful so long as each is being use to solve the problem that they're the best fit for.
206 karma · joined January 15, 2013
Yeah 100% this. Comparing a graph data model and a relational data model while obviously possible isn't really all that fruitful so long as each is being use to solve the problem that they're the best fit for.
A lot of devs even at a mid or higher level have little curiosity for the theory side of things, and eventually you'll run into problems that require knowledge of it, so being enthusiastic (and a bit self-starting) in that area pays dividends in my experience even if you're not the most experienced dev going for a job.
The only caveat is that both were/are small companies, so no HR apparatus to go through.
I think there's a desirable degree of pragmatism to be favoured in lieu of unbounded technological utopianism on this point.
Thanks guys!
Taught myself JS, then PHP/HTML/CSS, then graphic design, then back-end stuff (Ruby/Python), some regexes, algos and how to use Linux at a basic level. I'd actually built some stuff as a teenager (websites and mods/tweaks for Homeworld2 in Lua), but I don't count that.
> Did you do unpaid work to establish yourself?
Yeah, quite a lot. Several small sites and a couple of slightly larger ones for my day job at the time - I was working three days a week for a learned society and studying my off days so I did bits for them. A lot of that looks pretty cruddy now, but y'know, that's learning for you.
> Roughly how long did it take you from day 1 of learning to day 1 of being paid?
Started learning in July 2012, got two job offers in June 2013.
> What was your first gig?
Working for a startup making scheduling software. Started as a UX/UI dev doing a bit of the back-end stuff but after re-doing the front end spent a lot of time putting in tests and re-architecting things. It was frantic but good for learning fast. I work for a mature (but still small) company now, which is a nice change.
When I started, it was PHP/JS, but after a while quickly changed that to Ruby/Rails, Python, JS/CSS/HTML and design (can't do a solo project without knowing some colour theory, typography basics etc). With only six things to tick off, it was less of a daunting task and I felt like I was making progress.
I've added to that list both at work and around work since, but as somebody above noted, you can get burned out from coding all the time - sometimes you need to recharge and wait for the fire to come back.
The one thing I do know, is that if you have a passion for the craft and nurture it, you will be able to find a balance :)
Absolutely. So many people seem to aggressively argue for 'test all the things!' or 'test nothing!', where I imagine most jobbing programmers are practical enough to test the key things first and then expand from there. If I'm greenfielding something, I'll do TDD-first, but on new features on an old code-base or legacy apps it's initially way more just a catch in case I come off the mountain unexpectedly. I don't want to spend a day writing a feature and then find out I've broken something fundamental, I want to find that out after a couple of hours.
Especially at large UK festivals like Glastonbury with a broad appeal, it's the acts that are playlisted on BBC that will be playing the festivals. It's not just that that's where the audience is, but it's the echo chamber effect caused by the fact that that's where the industry's ears are, from the pluggers, to the PR men to the festival organisers.
The funny thing is that in my experience this pattern even holds true for niche scenes like math/post rock or metal, just with a different centralized power broker (be it a label, radio station, magazine or booker).
Like tech startups that are beholden to the VCs because they're capital starved at an early stage, the speculative nature of music (I think) is why power tends to accumulate in the places where influence and capital lie.
[0]http://www.theguardian.com/media/2014/may/25/radio-1-playlis...
Combat like this was described in Joe Haldeman's 'Forever War'[0], IIRC.
Do you have any evidence to back that up? I know it was orthodoxy like twenty to twenty-five years ago, but I remember there were plenty of other theories in my university days.
Pushing young people out of the job pool isn't such a bad thing if there's an educational alternative. Besides, people on lower incomes spend a larger proportion of their income, rather than saving.
Directly increase their disposable income with a minimum wage and I find it hard to believe there won't be an increase in spending in the economy - and that has its own multiplier effects.
Besides, even if what you say is true, then you could pragmatically combine policies for effect; an increase in minimum wage with say, government spending on education initiatives, or raising the mandated school leaving age.
Well aware that they are proposing stupid stuff, but surely that's unenforceable? In any case, it's one of those where I'd argue the problem is therefore up to them to reconcile the stupid surveillance laws with their more fundamental principles.