|
Counting has come a bit out of fashion, hasn't it?
I just tried and it came out about fiveish.
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
I got 4.75 - but one of my fingers is a lot shorter than the others.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
No need for this kind of precision here.
4,75 looks kind of fiveish to me.
If I look at it out of the corner of my eye it definitely looks fiveish!
Cheers!
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
I don't have the time for that
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
In FSOW:
Number of symbols in the clue = number of letters in the answer
So it's not necessary to mention the number of letters in FSOW, they say
|
|
|
|
|
Not always OG had a strange one a while back that didn't - just saying
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
If it ain't sheep OG does have some difficulty counting.
He even messes up whole numbers, which are inherently the easiest to use in counting. :P
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
That's totally Vader's TIE fighter from the original Star Wars... You know, that great trilogy for which they thankfully never made any more sequels...
|
|
|
|
|
... if I'm the project manager to be - why you force me to use a specific technology even before we started?! I'm quit...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
It's not the PM's roll to decide on the technology. The sole responsibility of the PM is to ensure that the project is delivered on time and to budget. It's not even their responsibility to ensure it works. The hardest part about a techie moving to being a PM is letting go of the technical side.
|
|
|
|
|
Granted - not PM decides on the technology (however in this case there is no development team jet, and it was expected of me to create one)...I had no objection to such statement from the development team, but it came from the owner...
I do not care if he has a thousand nephews just finished learning AngularJS on a five day course...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
There may be other considerations coming into play here that you aren't aware of. For instance, he may have license issues over a particular IDE/language combination or he might have a set of platforms planned later that you aren't aware of. Never assume that you know what factors the owner is weighing in.
|
|
|
|
|
IMHO, there is no way an owner should interfere with technology...
He has the request, the time-frame, the budget - the PM will look into it to make it done!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Of course - but there again you probably have an understanding of information technology while the owner does not, try explaining that to the owner.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
modified 27-Oct-15 4:54am.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: the PM will look into it to make it done! No. Which bit of that's not the PM's job caused problems? The PM should not be concerned about the technology stack - it's a common thing to have PM's who aren't technologists, but who have very good at organising, planning, budgeting, identifying risks, reporting, etc - all the things that are meant to remove the roadblocks and that are meant to keep the project on track. Frankly, when you're developing a system, there's nothing worse than a PM who continually butts in because they used to be a coder.
Yes, the PM may have an opinion and they may offer it, but they aren't there to enforce it or even to choose it. If you're going to do a PM role, you need to stop thinking like a developer and learn to take a much more strategic view. And yes, I speak from experience here - the hardest thing I ever had to learn to do was to hand over the coding reins to others.
|
|
|
|
|
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
As I told. I do not want to hold the technology. All I want is to receive it from the right direction...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
And what do you consider the right direction to be?
|
|
|
|
|
Developers...I can trust those kind of guys around technology...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Worst possible people to choose a tech stack. Far too many developers fall into the "ooh shiny" stack and will push for tech that they want to learn. As I said, there are things like licensing issues that can come into play so, you might have a group who want to do Universal Windows development because they think it will look good on their CV, but the reality is that developing commercially with it requires Windows 10, server infrastructure for enterprise side loading and commercial VS licenses.
|
|
|
|
|
In a setup where there is no architect for that, this IS the group to make the decision...For sure not the owner, who has no idea (and should not have)...
It is PM's job to not let the developer team to dream outside of reality of budget and so...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Okay, get back to me in a year when your developers still can't decide which stack they are finally going to develop this on because new and shinier stacks have appeared regularly in this period.
|
|
|
|
|
d'accord!
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
Very good points - the best PMs I have worked with are those who have no experience of IT but are able to trust my advice and are great organisers and negotiators.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Pete O'Hanlon wrote: the hardest thing I ever had to learn to do was to hand over the coding reins to others. I never actually managed to do that, so I'm stuck as a developer/architect. And yeah the architect part means I get to choose, right up until some stupid twat in Microsoft canned Silverlight.
Never underestimate the power of human stupidity
RAH
|
|
|
|