anomie
Joined 16 years ago
Joined 16 years ago
(Sounds like they’re not well done in practice although don’t have much personal experience- maybe haven’t hit the UK as much yet)
It's this which upsets me as someone in favour of remaining. I know a large number of people who are personally concerned for the immediate safety of their jobs following an exit vote (working in the finance sector in London, working for research institutions currently funded by the EU, or Brits working outside the UK) and also have friends (and a sister-in-law) who have come to the UK thanks to the freedoms afforded by the EU, and who are worried about their futures now.
I have great sympathy with the desire to send politicians a message, and with a desire to make the EU a more transparent, more efficient organisation, but you can surely understand the frustration of people who are facing very real fears for their own livelihoods, when someone in favour of exiting tells us they are doing so not because they believe that leaving is the best thing for the UK, but rather because they want to "send a message". This message comes at a great potential cost, and the people sending the message are in many cases not the ones paying the price
I find that most new developers instinct is to do exactly the opposite - i.e. write the first line of their main function, then realise it needs, say, an argument-parsing class, so start writing that, then realise that needs a logging class, so start writing that, etc. which means you have to keep much more stuff in your head at once, you end up writing much more code in each commit than you should, and the distinction between bits of code at different levels of abstraction often ends up much blurrier which leads to messier design.
This seems to be quite easily countered though - just pointing out to people the difference between breadth-first and depth-first styles can have quite an immediate effect
Of course after seeing 10 days of government without the lib dems to moderate I'm starting to re-evaluate how positive an influence they likely were...
(The wiring was originally done by my grandad'a brother - use a professional people...)
Well worth the effort to take the time to set up such a tool, particularly if you have a large UI test matrix - we couldn't possibly verify all the different page layouts and sizes before we introduced wraith
We have a very strong culture of constructive code review though - I guess you might have some work to do to get those more experience coders to get into the mindset that would accept this sort of feedback in a positive way