Well at home I got a single wide screen monitor anyway, and at office I will go for that as well the next time I buy a monitor.
Printable View
Well at home I got a single wide screen monitor anyway, and at office I will go for that as well the next time I buy a monitor.
Please regale us with more tales of your time working at Sage!Quote:
Originally Posted by Khendraja'aro
Listen, Steely, if you haven't got a clue of how developing a program works, just say so.
You're trying to excuse a developer's WTF without having the faintest idea of how a program actually works. Again, there simply is NO reason to roll your own DateTime functions. None. All modern languages (and by "modern" I mean: Younger than COBOL and FORTRAN) have such functions and methods in their APIs. C++ has them, C# has them, Java has them, Rust has them, Haskell has them, Ruby/Python/Perl/PHP have them.
New WTF and it could be a coincidence or it might not be.
Spent the day working on a spreadsheet for a business proposal. Quite a basic spreadsheet, three tabs of data with all data fitting on one screen per tab. After finishing I loaded up Gmail webmail (that I use for my email) and attached it as a spreadsheet. As I always do when I send an attachment I clicked to download it (to see that I've not sent an earlier draft) but now its saying that it is corrupt. Checked through File Explorer (or whatever its called nowadays) and this basic Excel spreadsheet was saving as 3.1MB. WTF?
Started a new spreadsheet, copied and pasted everything and it now saved as 15kb. A bit better. Reattached that but again its showing as Corrupt when I try and download it. Gave up, emailed it anyway and now Gmail is showing the spreadsheet perfectly through its preview feature but when I click to download it, it is still corrupt. Hoping the other person I've emailed it too doesn't see it as corrupt.
Never had this happen before so its an almighty coincidence if its not related. Only software used in this is Windows, Excel and Gmail (via Chrome) so no third parties.
That's most likely a problem with Chrome and/or GMail. You're not the first to run across this issue: https://productforums.google.com/for...il/MoV8OuxAvYk
Did you try the same in Edge?
I'm fairly certain the only person around here who doesn't have a clue is you. You have absolutely no frigging idea why Sage even needs Windows date format to be set a certain way, yet your first assumption is that it's because the developers didn't know some pretty elementary stuff about the language they were developing in, which demonstrates nothing but the most breathtaking arrogance on your part.Quote:
Originally Posted by Khendraja'aro
It *could* have been a mistake, it would hardly be the worst WTF ever found in production code, but there may actually be perfectly valid or at least understandable reason for it which neither you nor I being entirely unfamiliar with the code I'm question are in any position to speculate on.
Steely, if they're getting basic stuff like DateTime wrong then I wouldn't really trust them to get more complicated stuff right.
And that they don't know pretty elementary stuff about the language they were developing in, that, my dear, they actually demonstrated by having their program throw a hissy fit about the date format. And frankly, in your case the Dunning-Kruger-Effect comes fully into play. But I'm done arguing with you. Keep on finding excuses just because you're deadset on proving that Windows done goofed. Anyone who actually knows their stuff will only laugh at you.
Just tried with Firefox and Edge and it still shows as corrupt. So Chrome isn't the issue.
Going back to Sage when it detected that Windows was using the wrong date format it gave me prompted me with saying that Windows was using the wrong format and giving me the option of three different date settings. Using Windows default was the default setting, there were two others that I ignored because I'd rather get Windows working properly than fiddle around with other settings. Sage may or may not be using DateTime in the second or third setting, I don't know and honestly don't care.
When I referred a few pages back to a company advising that upgrading is delayed a month so that someone else spots incompatibilities, that was Sage btw. I timed the upgrade by waiting until after I'd finished running payroll and paid everyone and finalised this months accounts before upgrading to 10. No regrets whatsoever over that and my teething problems kind of match my concerns and Sage's advise over timing your updates at a time that suits you properly. Had I been dealing with these incompatibilities while I was on a deadline to pay wages that'd be very frustrating.
This is absolutely ridiculous. You have no idea what weird and wonderful combination of edge cases and quirks may or may not have lead to that particular decision. You have no business simply *assuming* "oh they just rolled their own DateTime library, because they're idiots" based on nothing but a few vague statements from randblade, and no business questioning anyone else's competence based on the level of assumptions you're comfortable making.Quote:
Originally Posted by Khendraja'aro
To be fair the description given by RB doesn't exactly make it sound like it was deliberate. The first part just looks like an oversight which I guess is a little dumb but that's how the world is. Of course Khen is also dumb if he gets this pissed off about what seems to be a mistake. It does not however sound like someone rolled their own datetime function so much as someone neglecting to store some data as dates similar to what happens when you enter a date in the wrong format into an excel cell.
Well, Khen gets pissed off at the drop of a hat, I think we've all witnessed this behavior by now, so what you gonna do. It must be exhausting.
Anyway, if I had to guess I'd say that in there system they have a date which is generated by windows but for some reason in another part of the system it is only accessible as a string so they have to parse it, and they need therefore to know the format it's in do so reliably (I have no idea if they're able to interrogate the system and simply find out what the setting is). Why this should be, who the fuck knows. It could have been an error in the distant past that is too costly to fix, it could be a limitation of some API, library or language they're using, a limitation of the storage format they use, or a consequence of some bizarre inhouse coding standard they're stuck with, or any one of of another a million other things.
Point is; you don't just look at something that appears stupid and then go "obviously the person who wrote this was an idiot, I am so much smarter and so I shall fix it!" Because there's a good chance that five hours later you discover there was a very good reason for that thing that only becomes apparent after looking into the problem for five hours. Or worse, you discover that what seemed stupid was actually a fix for an incredibly obscure bug that you just reintroduced without even knowing about it, but which will quickly become apparent as soon as the software is being used by thousands of people.
This, of course, is also why quirks like this date thing stay in software for version after version, the cost of fixing it and then verifying the fix doesn't have some bizarre unintended consequences may simply outweigh the perceived inconvenience to the user.
Of course here I'm talking about someone who actually has access to the code in question; to make that kind of judgement - "anyone who does this should not be let near code because because apparently I'm physic and can tell exactly what code was written and why" - when all you have to go on is text description of the issue is goes beyond hubris into the realms of the insane.
Still haven't had Windows 7 prompt me to install 10. Icon still sitting in my sys tray telling me windows will tell me when 10 is ready to download and install.
Anyone else still waiting, or has everyone just ignored the wait and installed anyway?
I installed anyway. Run windows update and make sure its working and has everything it needs.
Same issue for me, i had to force it to install.Quote:
Originally Posted by Timbuk2
http://www.pcadvisor.co.uk/how-to/wi...pdate-3575135/
I used this link above to determine how.
I never got the prompt either (I think because my previous install was linked to a domain), but finally upgraded. Went pretty smooth, though it offered to keep my software but kept giving errors so I dropped that in the end. Only annoyance I've noticed so far is that my laptop keeps waking up in the middle of the night.Quote:
Originally Posted by Timbuk2
Oh and neither the product ID as shown by windows 7 nor the one on the sticker were recognised as valid codes. But I upgraded first, then did a clean reinstall with skipping all the prompts for the license, went online with the clean install and now it's good.
Now just to try whether openoffice/libreoffice is any good or whether I should pay (quite a lot tbh) for office.
Internet wisdom: Never upgrade something that works.
I learned it back at the Infogrames forums years ago.