The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
From the classics of the 10's week.
Not really a classic I think, although it got high reviews at the time (2013) and it's certainly got a kick to it.
Beyond All Recognition mixed metalcore and dubstep, an electronic musical genre that was popular at the time, and did it well.
Dubstep proved to be a temporary fad and so did Beyond All Recognition, unfortunately.
I didn't actually expect to share this last week, but one of my friends shared an album that reminded me of this one and it still deserves to be heard.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
I liked the sound but as Nelek[^] said I didn't understand the lyrics either. But that's not what bothered me.
A few years ago I was lucky enough to catch Billy Idol in concert just up the road from me. He was great, singing voice was still amazing. Between songs he talked to us, but his voice was so raspy. Still great at singing, but can't talk. So I'm listening to your SOTW and all I can think of is that he isn't going to be able talk in a few years time. As I said, I've gotten old.
I think I know them like that too
I've heard them once or twice, but to be honest, I keep watching for that front lady (or lady front, if you will)
The music is nice too though, just not completely my cup of tea.
Maybe I should check out the complete album.
I'm not sure I can find the articles relating to this difference I am trying to figure out in my head.
When discussing what a Senior Software Developer/Engineer should be and do, the 2 things that that stick out relate to Training Juniors and Doing multiple things (being either projects or multiple languages)
So I am split on that 1, being aware of multiple languages is like having multiple tools in the workshop. Knowing that another tool might be better fit to the job.
This seems to limit a proficient person. Someone that say is expert in C#.net back end.
They can easily say No if a job is proposed and wanting C#.net to be the implementation, but maybe not 100% on offering a different solution
The make code and systems which are solid at launch. highly maintainable by others, and delivered on time that they had a hand in proposing.
But that person is not "senior" because not multiple languages. Will only take 1 job on at a time. Can work in a team but not as classic "mentor", happy to share knowledge but not the Padawan/Master strictness.
Is there another term for this career path, Mastery or Proficiency, which is slightly different, or is the Senior concept a push over from other career structures.
"Proficient" : "I can do this stuff".
"Senior" : "I get paid more".
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
My definition of a Senior Developer is one that does not need help.
But I get your point. I hired a Senior Developer years ago but he wanted a lot of hand holding, not writing code, but in knowing what to work on next. He was still Senior because he did not need help writing code, but he lacked a lot of skills other Senior Developers have.
Seems to me that we had these ratings, graded from senior to junior:
Leaps tall buildings in a single bound
Must take a running start to leap over tall buildings
Can only leap over a short building with no spires
Crashes into building when attempting to jump over them
Cannot recognize buildings at all, not to mention jump.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
I think the only "senior" developers I have seen were called that (and probably earned accordingly) because they were old or with the company for many years.
It never said anything about their skill level.
They always underwhelmed me with their lack of basic knowledge of any tech after approx. 2005.
Doing the same thing for 20 years != 20 years of experience.
A common misconception, it seems