|
|
Blocked by an ad-blocker blocker therefore didn't read. I shall probably never read another "Wired" article again. I'm sure I'm not the only one.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Same here. ABP's anti-blocker subscription can't handle it and the 2x5min I've spent failed to figure it out either. (I suspect I'd need to go the no-script route and turn them on one at a time until finding the one that triggers it; but can't be elephanted to make that sort of effort.)
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
It seems like it's a stark contrast, but, really, what ARE the differences between a junior and senior developer? More importantly, how can both sides gauge the progress of a developer into more senior territory? About $30K a year?
|
|
|
|
|
From personal experience - knowing:
- what Visual Studio is and how to use it
- how to debug code
- how to write code that is testable through a test fixture
- wait, even before #3, the concept that you have to test your code (true story)
- how to tease apart requirements into an architecture that abstracts where things need to be abstracted, etc.
- how to write a specification so someone can write the code for it
- oh wait, before #6, how to write/communicate. (I got hammered as a kid for using "it" and "that", a lesson I took to heart many moons ago)
- etc.etc.etc.
But ultimately, the true difference between a junior and a senior developer is:
The ability to say, and the frequent use of, the word NO
Marc
|
|
|
|
|
Marc Clifton wrote: The ability to say, and the frequent use of, the word NO
If you use the word NO as a junior you'll never get a chance to become Senior. How's that for a Catch 22?
|
|
|
|
|
Jörgen Andersson wrote: If you use the word NO as a junior you'll never get a chance to become Senior. How's that for a Catch 22?
Good point. Still, someone who constantly says yes is definitely junior. 
Marc
|
|
|
|
|
Marc Clifton wrote: The ability to say, and the frequent use of, the word NO
Very true, but I'd go further, to say "The ability to say, and the frequent use of, the word NO whilst being able to justify your reasons in a way a project manager can understand."
|
|
|
|
|
Wastedtalent wrote: he ability to say, and the frequent use of, the word NO whilst being able to justify your reasons in a way a project manager can understand.
Very true, and I'd add, from my experience working with management, say no but have at least one (preferably two or three) alternative options in hand.
Marc
|
|
|
|
|
Marc Clifton wrote: The ability to say, and the frequent use of, the word NO
I prefer to take the approach of giving all the necessary information to the decision-makers (the costs, benefits, estimates, approximate time-scales, impact etc etc) and let them make the decision. Then it's on their heads not mine. If they say yes to something that is really stupid, then that's entirely their decision.
As an example of this, in a previous company (who shall remain nameless to spare the innocent) we were asked to estimate how long it would take to convert a major part of the application from Classic ASP to ASP.NET. The team took a day off site and together we came up with our best estimate of 9 months. The CTO had already told one of our big clients we could do it in 3 - 4 months. We told him it was impossible. He cajoled us with overtime and a bonus payment if we succeeded. We told him again it was nothing to do with the money, there just wasn't enough time and people. Suffice to say we didn't hit the target. Over the course of the next 12 months the entire development team left (including myself) and eventually he was fired.
There are always consequences to be paid for ignoring the advice of those who are best positioned to give that advice.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Dominic Burford wrote: Over the course of the next 12 months the entire development team left (including myself)
Which is the ultimate "no." 
Dominic Burford wrote: and eventually he was fired.
While it's on their heads, its unfortunate, because really everyone ends up paying the cost, even if you did move on to a better (or at least equivalent) job. Hopefully better, by the sound of what was going on where you were!
Marc
|
|
|
|
|
I would like to think the people involved in making their decisions learnt some valuable lessons. Life can be tough and unforgiving, and there is no short-cut towards experience and knowledge. People need to make mistakes so they can learn
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Marc Clifton wrote: The ability to say, and the frequent use of, the word NO
I prefer the "Yes, but..." approach, followed by a list of things that paints the business leader into making the "No" decision, or extending the timeline and budget by 200%.
|
|
|
|
|
Vark111 wrote: followed by a list of things that paints the business leader into making the "No" decision
plus, as I've learned, suggesting a couple alternative paths that try to meet the issues at least half way. 
Marc
|
|
|
|
|
Some are born as a senior, most however as unfortunate as it is will never become one...
|
|
|
|
|
gstolarov wrote: Some are born as a senior, most however as unfortunate as it is will never become one...
I disagree. At least in this field, we're all born junior, and certainly in my experience (self-taught, no degree, no formal schooling) the reason I'm recognized as senior is because of my demonstrable accomplishments -- I've never met anyone that had senior qualifications that was actually in a junior position. Well, maybe because the company has become gentrified, but those people have always found other work that recognizes their talents (me included in that situation once, many many years ago -- really it was the defining moment of when I stopped being junior and, while not quite senior at that time, was definitely on that path from that moment on. And heck, with all the technology changes going on every day, there's a lot of things I can point at and say, yeah, I'm junior in that, but the difference is, I have years of experience that make me senior at how to learn something new.)
Marc
|
|
|
|
|
A senior developer knows what NOT to do.
|
|
|
|
|
Major content providers object to Brave Software's business model; Brave counters it's 'not the enemy' Ad Blocking deemed illegal?
Edit: fixed url
modified 7-Apr-16 20:30pm.
|
|
|
|
|
You just won the Major Link Fail Of The Day Award!
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Eh. That link was a more useful article. 
Fixed
TTFN - Kent
|
|
|
|
|
Although Apple’s Swift language might be open source now, the last place you’d expect to see it is on Android. But according to some sources, Google is considering making Swift a “first class” language for the iPhone’s biggest rival. That way they can be sued by both Oracle AND Apple!
|
|
|
|
|
Be hard to sue someone for using Open Source Software, as long as they keep to the license.
I suspect someone will port it to Windows too at some point.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
It they bypass Dalvik/ART altogether, bring it on. As it stands now, Java is a death by a thousand cuts.
|
|
|
|
|
This new and stable version of Android Studio has fast build speeds and a fast emulator with support for the latest Android version and Google Play Services. Now with added "Not Eclipse" for your coding pleasure
|
|
|
|
|
Microsoft has partnered with HackerRank to bring code snippets right into its Bing search results pages — and as an added twist, you can also edit and execute this code right on those pages, too. But the people who would benefit most don't know how to search
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
