1. Most HR departments use "Senior Software Engineer" as a catch-all title for techies. Irrespective of the title that work gives you; you should name yourself as an Architect or Technical Lead or Consultant, or all of the above for the various roles that you've done (any other role that you can back up with from your experience and skills). So long as you've been doing that work there is no harm in that. Your skills and experience should back you up in the title, whether or not the actual title of the role was such.
If you retain the title of Software Engineer, then that is all that recruiters will view you as.
2. Remember; YOU OWN YOUR CV/RESUME! You can write whatever you like and think will sell you best. Don't say you're a Chess-Grand-Master if you aren't but write that which sells you and your skills and shows them in the best light. You don't need to write everything; focus on your strengths and those areas that show your team leadership and advanced skills. Structure it appropriately and you'll be able to include all your skills (so you appear in search results) and target your strengths.
3. Look for some certifications in an area that interests you that if you tag to your resume/CV will give you the leg up you need. PRINCE 2/PMP/ITIL if you're looking for management leanings; MS/SUN/Oracle architect/DBA certs if you want to keep a foot in dev.
4. Get an MBA or MSc in a specialisation.
5. Find a niche - personally, I'm in Security, but there are plenty of others out there.
6. If your present company won't give you the opportunities, leave and find a place that will. If your skills and experience isn't recognised, then there's no point playing the sucker for them.
7. Double check yourself; the problem may be with you. Work on your soft skills: Make sure people like you (don't become a kiss ass, but just try to get on with people - especially managers); Work on your communication skills (Email, powerpoint, speaking, presenting, mentoring, documenting, making a proposal).
If you don't want to be a slave to a manager/HR hiring you, then you can always go the start-up route. I have little to no experience here, so I'll just leave that hanging as an option. :-)
This is very well put together.
I think the best part is that he doesn't overplay or browbeat the point.
The World changes, but it certainly takes a while for us to catch up with it...
What the article has missed is the fact that these cameras and their operators are less interested in crime and far more interested in fine-able offenses such as motorists parking incorrectly; stopping in the wrong place; driving too fast; people putting their rubbish out on the wrong day; people putting the wrong rubbish in the recycle bins; or whatever else they can bill you for to pay off the bank-bailouts.
Local councils are milking these cameras for all that they are worth. Most of the cameras aren't even watching crime spots, but are instead focused on the roads at stop signs etc. Given the added revenue - irrespective of the crime prevention stats - those cameras are here to stay.
Is this an attempt at FUD to stop people from going overseas for inexpensive treatments? Or is my cynical conspiracy theorists hat on a little too tight...
Take some personal responsibility instead of wanting Big Brother (Twitter) to do it for you.
The more inappropriate things a person says, the fewer people will follow them...
... Anyway, WHO defines WHAT is a bad tweet? Just cos you don't like it and find it distasteful, doesn't mean that others will also.
Many forms of satire would be deemed distasteful and yet others are simply deemed distasteful due to the reader having a poor sense of humour or lack of context.
Useless article!
Purely a scaling issue.
It's a similar story to the days when sites would get D-DOSed by Slashdotters!
There isn't an ifinite amount of bandwidth out there, so this will ALWAYS happen occasionally - even in the Holy Cloud!
You can develop an Access Management system (or integrate with a COTS).
You can watermark the files with timestamp and username. Thus allowing you to track who let the documents go into the wild.
Based on Meta data, you can restrict access to different files and restrict the client's ability to display those documents.
None of those tasks are trivial and all of them can be worked around.
You aren't building a military grade secure system, so, perhaps what you are doing is good enough.
I'd start with Access Management and add visibility controls on documents.