Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@champion01 I don't know what it was like. But I tried my best to shut the fuck up until they asked me a question.
So every time they asked I was basically forced to shoot down the ideas because they simply don't understand what it is were working with. -
@kevbost that's the best way you could of handled it. Well done!
-
@champion01 unfortunately, most people either don't understand what you just said or think you are out of you mind. Those people who think you are right are the better once
-
@claudiofilipe21 win10H
-
@rant The thing is, the people setting the requirements have no concept of the technology. There are two tasks this sprint, and they were both complete on Monday.
I know what you're thinking, "Why don't you set the requirements?"
You're right I should probably do that. Now... if i could just get someone to listen to me. -
@kevbost I know how that feels. In a previous job I did the whole setting requirements, deliverables, and closure criteria for the project at the beginning... But because the people on the project were non-technical they never felt like I delivered quite what they had in mind although I had fulfilled every criterion specified.
At some point you just do what you can and make sure you have solid, authoritative answers for when they ask you. That's all you can do. -
@rant Agreed. I'm doing my best to look into the future at the problems were going to face in none of us being familiar with the technology.
It's unity and c#, and while I'm extremely visual and can make my way around unity, I am not up to speed on c#. And the opposite is true of my colleagues, very well versed in c# but have no visual sense of order.
https://github.com/Microsoft/...
I work remotely for a team that works together in an office, and this morning on the conference call a team member said
"one thing i think we need to do with this is stay on task, because while these things that have been added are cool we don't need to be doing anything not outlined in the MVC requirements"
Okay first of all -- this is a completely foreign technology to this team. It's not like I diddled around adding fancy animations and no function. The problem working in a new technology with an old mindset is assuming that it's going to move linearly from step 1 to step 2. And that drives me fucking insane.
- Progress in paid contracted work is done by staying on task.
- Progress in research isn't done linearly. You have to try shit -- and figure out what doesn't work.
I feel bad because I'll chime in and shoot down ideas with a fucking guided missile because I know the answer and I've done the fucking research -- I'm not a dick about it, but replying with a simple "no that's not possible, because of this or that", the call becomes silent for 30 seconds because I've shattered their understanding of the technology because nobody has taken the time to understand anything about how this thing works!!
So until they either listen to me, ask me, or learn the smallest amount to get on my fucking level, I'll keep progressing -- because whether the old world idealists like it or not -- that's my job.
Progress.
</ rant>
undefined
devrant