No “fixing” with the latest build ;)

Woakes

W
As developers we have bucket lists we check out code. We do what we can for the expected release window. And things may be ready in time, but aren’t as perfect as you want them to be. Many things are abandoned at the good enough stage for testing and deployment.

This is the kind of develop-perfect that can only come from months of toiling in the code-base and no-one else sees any noticeable gains but the developer is happy knowing their end is finally fixed and sorted.

I remember back when I was a dev on larger projectsthe current “merge and deploy” is delayed for a critical fix, then there is a flurry of devs trying to squeeze in their latest build.

This studio recording of David Gahan’s “kingdom” makes me chuckle as we see the process being joked about in the music industry, I guess all creative production have the same issues.

Clas: you came in later!?!
Dave: Yeah I know! I just like following you guys
Clas: You know when I do this[deafening drum crescendo]
Dave vocalises.
Clas: I can fix my end.
Dave : no fixing!
Someone else: if he’s fixing, I’m fixing!

makes me chuckle.
Source: https://youtu.be/s0gETWzWHOU

4m57s

So update 11 then ;)
 

Mogen Teras

M
I dont get what kind of point you are trying to make. That we should praise FDev for working on it despite no significant progress on the users' end because "trust me they're doing stuff." That we should be glad about the improvements they've made on the workflow side that we have no way of even proving exists?
 

Woakes

W
Mogen Teras said:
I dont get what kind of point you are trying to make. That we should praise FDev for working on it despite no significant progress on the users' end because "trust me they're doing stuff." That we should be glad about the improvements they've made on the workflow side that we have no way of even proving exists?
Click to expand...
None of the above.

just some comedic banter in rough times.

The gossip on the forum last week
Was that update 11 was delayed a couple of days for some fixes.
Meaning an opportunity for other Devs to squeeze in their fixes. A well disciplined team shouldn’t squeeze in fixes, because the test cycle for every new piece of code will increase the margin of delay.
Hence the joke “no fixing!”
To avoid the
“If he’s fixing, I’m fixing”

It’s hard “not” To fix. A developer has pride in their work and prefers to have the “better” version for all to see. ironically it can become a Pandora box of good intentions.
 
Last edited:

Woakes

W
Greybeard Seawolf said:
I think the update was delayed because the board had finally made a decision on consoles and they wanted to get that out first
Click to expand...
That’s a very cynical view point that I can agree with to some degree of hindsight ;)

Personally I think in more “fuzzy” logic (node based weighted neural paths) both literally and well, literally and I attribute that to others.

Decisions are strategic plans of action to get out of scenarios which can be described by multiple factors.

So the console announcement, which I am proud of Fdev for making such a dammed hard decision, is a factor since every update is hampered by “but what about the console”.
And a bit of good news (update 11) after bad news (no odyssey for consoles) might help some. But in all fairness, update 11
Will be swamped with compensation claims or migration queries.
But then again maybe they hoped to get the update out prior to the boards-decision but two bug fixes on the board (central to the carrier) delayed and the board members took an executive decision if they are fixing then I’m fixing ;)
 

Greybeard Seawolf

Greybeard Seawolf
Woakes said:
That’s a very cynical view point that I can agree with to some degree of hindsight ;)

Personally I think in more “fuzzy” logic (node based weighted neural paths) both literally and well, literally and I attribute that to others.

Decisions are strategic plans of action to get out of scenarios which can be described by multiple factors.

So the console announcement, which I am proud of Fdev for making such a dammed hard decision, is a factor since every update is hampered by “but what about the console”.
And a bit of good news (update 11) after bad news (no odyssey for consoles) might help some. But in all fairness, update 11
Will be swamped with compensation claims or migration queries.
But then again maybe they hoped to get the update out prior to the boards-decision but two bug fixes on the board (central to the carrier) delayed and the board members took an executive decision if they are fixing then I’m fixing ;)
Click to expand...
I agree but I am frankly surprised that they hadn't already figured out whether migration was possible before the announcement. I understand that it's hardly an ideal solution but having that option at the time would have taken at least some of the sting out of it, I also feel offering a copy of EDO to those transferring should be considered.
 
You must log in or register to reply here.
Back
Top Bottom