[Qt-interest] VS 2010?

[Yves Bailly]

Eric Clark a écrit :
>> That kind of non-sense has shown a few time already on this list, and I really
>> can't get it... if you need a whole day compiling, then don't compile during
>> the day: start the compile in late evening, just before leaving office. The
>> compile will go over night, keeping your safe salary.
> 
> First of all, calling what we do non-sense is rude and very inconsiderate.

First of all, I didn't say this personnaly, I mentionned it showed several
*on the list*, not from *you* personnaly. Now allow me to find rude to see such
a long thread about something I consider a non-event.

> Our company has been around for over 30 years and is a multi-million dollar
> company for a reason. Obviously, they know what they are doing. 

So what?
Obviously, a multi-millions dollar company knows how to make money. But it
doesn't mean it's a good one in an industrial meaning. There's no direct link
between the amount of cash a company makes, and its intrinsic work quality.
Please note, I'm not saying your company is bad: I'm just saying its $ weight
is irrelevent about the fact it "knows what it does" or not.

> So, what you are suggesting is that I do this work on my own time.

I never suggested such a thing. That is very rude and inconsiderate: you put
words in my mouth, words I never wrote.

> No. I am paid to work during the day and that is exactly when I will work.
 > The company is fully aware of this and that is exactly why we do everything
 > we can to make things faster and less expensive. Again... exactly why the
 > company is a multi-million dollar company.

Because it was a better shark among other sharks? indeed, *why*. Maybe they're
good, maybe they're not, I don't know - and don't really care either. Again,
1- the $ weight is not linked to industrial/technical quality;
2- my words were not about the *company*, just about the fact that "building
   during the day is too expensive", to which I answered "then don't build
   during the day..."

Sorry, english is not my native language, so maybe I wasn't clear enough. Or
maybe you didn't read carefully enough. Whatever.

> Lastly, let's just say I take your advice and work on my own time... When

Please don't, as that's not what I said. Never.

> the build fails, I will find out in the morning. Then I will make a minor

When do builds fail? Last time I saw a Qt build fails was because *I* messed
things, forgot OpenSSL headers...

> change, and wait again until the night time to run the build. Then, I find
>  out again the next morning. So, now, what took me one day to do has taken 3
 > days to do.

Two answers:
1- let me be rude and suggest you try another job if it takes so long to compile
   something as simple as Qt;
2- then, 3 days... so what? a new release is out, for which you waited for 6 months,
   (i.e. 180 days) and it's usable 3 days later... big deal... 3 days during which
   you can still work using previous release, just as you did for 180 days, righ?

> So, as for "business sense" or what I would call now "common sense", one day
> is always better than three, especially if we have a deadline to meet.

Yup. And 0 ("zero") day is always better than 1, which is what I suggested in
"build overnight".

And I see I've already spend way too much of *my* time answering this... while
multi-billions $ companies go on speculating on basic materials, creating and
spreading starvation around the world... ah well. Thread closed for me.

-- 
      /- Yves Bailly - Software developper  -\
      \- Sescoi R&D  - http://www.sescoi.fr -/
"The possible is done. The impossible is being done. For miracles,
thanks to allow a little delay."