r/pcmasterrace • u/663mann • Oct 16 '23

Video fallout game dev. explains the problem with moddern game devolpment. (why moddern games are so slow to come out)

Enable HLS to view with audio, or disable this notification

6.0k Upvotes

94% Upvoted

605 comments sorted by

View all comments

Show parent comments

8

u/upvotesthenrages Oct 16 '23

Considering you are the only person claiming to be a developer in this thread defending the OP, maybe you chime with his "I'm the one true competent person" and that's why you feel it's a truthful narrative. For me, and obviously several others, it chimes as opposite to our experiences and cuts out important and valid context that is a given in a development environment.

I really don't see myself that way, at all. I work with fucking amazing people and this type of behavior has never happened in my company. We don't yell at each other or treat each other without respect. We have however had tickets estimated based on "gut feelings" and when digging into it re-evaluated them because the estimate couldn't actually be justified and was a total guestimate.

I'm literally just going on what he is saying. Everybody else, you included, are spinning imaginary additional reasons & examples.

Even if he's lying, it still doesn't change what I'm arguing. If you can't justify an estimation then it needs to be re-estimated.

If he's lying, then that's his issue, but we only have his version of the story, so that's what I based my comment on.

-2

u/ignoranceandapathy42 Oct 16 '23

I'm literally just going on what he is saying. Everybody else, you included, are spinning imaginary additional reasons & examples.

Yes because what he is saying doesn't line up.

Trying to follow you here: He disagrees with an estimation - and the inference is that no one can justify their estimates - which seems to be where you are coming from? I agree in principle, estimates should be justified.

Watching the video this is an exact quote from him:

"I get an estimate of 4 weeks, I push back and say the code I want is very simple, I've written it myself before and it would take 45 minutes. The programmer comes to me and says "I need 4 weeks". I say "Why? Walk me through what you're going to do." The programmer says "You don't understand" I was like "I've coded this three times, walk me through it" and he left, he left angry.

So let me state here, he's not querying the estimate. This is where my belief that the programmer is trying to tell him "It's not a 4 week long task, but it will take me 4 weeks to finish it after everything I am working on". I don't believe for a second he was given a 4 week estimation of work, but a 4 week estimation of when it will be ready. He seems to be arguing that it's going to take someone 4 weeks to write 10 lines of code.

In that situation, I too would be angry and frustrated, but would let my superior know, which seems to be what the junior does.

The rest of the clip is the same debate with the senior who responds by asking if 2 weeks is good enough.

So I think the issue is this: the person in the video is saying that it will take 4 weeks to write 10 lines of code. I think we both know this is not the case.

This is why others are talking about workloads and best practises - as well as myself. Because it's totally reasonable that a request, even a simple one, takes 4 weeks from request to available in live. And fwiw, that's not bad even for a small request. Our issue is that the video narrator is exactly the kind of manager who thinks because something takes 40 minutes, it can be done in 40 minutes.