9. You just walked a person thru a very simple sequence of actions ("click here, now click here...") for the 100th time. She has been at that job for about 100 days. Nope, she still doesn't get it.
Do you mean because these royalty payments only affect small companies that it doesn't matter?
Nope, I was just giving the full story before everyone who didn't read TFA went off into paroxysms about 25c/unit over 100,000,000 units...
Anyway, how many small companies are left in the mass market consumer electronics area anyway? Any small companies would be in a niche market and would be in a better position to pass on the costs...
And you do you realise that 2.5c is still huge - all those 16MB thumb drives given away by (cheap) companies in promotions only cost about 10c each in bulk.
and they're 10c each because they're made in bulk, you know, as in shedloads, as in one of those BIG companies so like I pointed out it won't be 25c/unit it will be less because of the cap.
exactly, the original post I was commenting on had posted a link to the M$ licence costs but had failed to mention there was a $250,000 cap on licencing.
I'm the last person to defend M$ but just saying $0.25/unit was misrepresenting the situation (probably accidentally) and it needed to be cleared up. It's not destroying small guys as some other posters have suggested because they pay 25c/unit for the first million units & this will clearly be passed on to the consumer at >25c/unit as these things inevitably are.
Even with the issues database there's too much x-referencing required.
I prefer (in an ideal world) the check in comment to be the issue reference + a broad brush description of what was done.
PVCS/Tracker allegedly offers such integration but we've not got it working (not that I personally administer PVCS here) I'd prefer it if we went FOSS for issue tracking & VCS & wrote our own glue if it doesn't exist - it shouldn't be a big job & it's a nice bit of code to donate back that doesn't jeopardise any trade secrets...
The version of PVCS we're stuck with here sucks nuts & I'm pretty sure that a FOSS alternative (in addition to saving a fortune in ongoing support that we don't use) would be at least as good and easier to fix up to meet requirements.
If you fix a minor bug, and a week later you realize it's created a major bug, but in the meantime eight dozen commits have been made by your team, it's not always easy to just roll back to the version before the one you helpfully noted in the CVS comment as being "the" bug fix; you really do need to tag bug fixes in the code itself.
No you don't, I've had to (far too regularly) go through 5 year old code riddled with tagged bugfixes of various epochs and I can tell you that generally they are more harm than good. Trust me a four year old end of line comment that reads "SRQ 5678" is not helpful to anyone.
What you need to do is have a VCS with a good difference feature built in or read out version 1.23 pre bugfix & version 1.24 post bugfix & do a compare. THAT tells you what was changed to fix the bug better than 25 scattered tags (which may or may not be complete). Then, knowing what was changed you get 1.32 (the latest version) and undo the 1.23 -> 1.24 changes. I have used the VCS to backtrack through 50 revisions to find out who was responsible for certain braindead bugs & what I need to do to unravel them.
Remember, VCS means never having to put bullshit comments like that into your code.
I remember the Master, Had one at work. We had a B+ too if anyone remembers those...
I'm racking my brains for the disc commands is it something like *DISK n?
You might have to switch over to another eprom because the network stuff was non-standard & was implemented by using a different boot eprom IIRC. It's the one on the left of the 4 slots in the basic B as you look from the front (it'll be a plain one not one with a label covering a window). Earth yourself & good luck. Swap out from one to the other to see if I'm right.
I've burned EPROMs for a BEEB before but good luck finding a burner & a 16K eprom these days.
I know someone who had a C64 in England. IIRC they were quite popular until the mid 80s when they were pushed out by the 16 bitters from the top + Amstrads from below. Sinclairs were always big in England - and they had some of the best games - Atic Attack, Ant Attack...
I had a BBC 'B' which put me in a bit of an Elite;) for a while but relatively limited for games. Revs was good with it's great Silverstone implementation (pre emasculation with all of the chicanes) as was Elite of course...
3D came to role playing games with Ultima Underworld in 1992
Somebody's forgotten about (or more likely too young to know about) Dungeon Master which debuted on the Atari ST in 1988 - I remember an Amiga owning friend of mine coming over to play my copy. He later ended up writing a Sci-Fi clone of it called BSS Jane Seymour IIRC for the Amiga.
I keep a local folder on my harddrive that I put important stuff into. If the company routinely deletes e-mail >6 months old it is probably in violation of its' record keeping requirements in most of the world (certainly the UK where I have run a limited company & the record retention period is 6 YEARS).
I doubt very much if you kept a local copy of the e-mail which you just happened to find & re-send that would be grounds for dismissal.
Getting charged with gross negligence is more likely to get you fired. Keeping hard copies of the e-mail trail would help you during an unfair dismissal case.
Re:No one notices a well done security job...
on
Security's Shaky State
·
· Score: 3, Insightful
I've experienced worse. At one company I worked at, I warned of the pitfalls of a particular implementation my boss had been sold on. I was ignored. When the problems I predicted showed up, I was then blamed for creating them.
Document EVERYTHING in cases like this. Offer advice in the form of an e-mail, print out a copy of the e-mail and file it somewhere safe (like at home). Also never delete the e-mail you sent.
Then when the stuff hits the fan you can defend yourself at the time in public and send another follow up e-mail including the original to back it up to whoever needs to know.
This doesn't work if it's the owner being the jerk but it does cover your butt if a supervisor's trying to push the blame down to save him/herself.
Looks like the American government is controlling the internet.
Even though this would make the lives of concerned parents (etc) 3,000,000x easier by putting an e-red-light-district on the web to make either finding or filtering pr0n a non-issue.
I thought First4Internet was owned (or at least had as directors) by some Sony directors.
Looks like their little pocket filling sideline of getting their own company to provide the DRM code to Sony has backfired.
F4I is probably going to get sued into oblivion (by Sony if no-one else) so the shares will be worthless but Sony will probably successfully claim ignorance no matter how incompetent that actually makes them seem. Maybe a director or two should get fired.
Time for a class action by all of the violated GPL/LGPL projects (I'm sure there's more than the two we see at the moment) to help gut F4I. Even if 90%+ of the proceeds end up going to lawyers they're being denied to the scum responsible for this shambles.
Also, we need to find out the names of the F4I programmers to make sure they're blacklisted. We as nerds have the control here - we review the resumes/CVs, we do the interviews. We can ensure our companies only hire ethical coders. If you get an application from an ex F4I coder, bring 'em in, waste their time & tell them why they're not getting the job. None of them had the balls to blow the whistle on this scam so they should suffer.
I was commuting daily to London from Hampshire when that happened so I believe I know about the situation.
I was 5 (five) hours late home one night because one of railtrack's cut price maintenence bozos took out one bolt too many & dropped a signal gantry onto the main SW rail line in Basingstoke.
Please explain how a supposedly independent rail authority which is issuing huge share dividends is so close to receivership? Surely it is criminally negligent to issue dividends if you are close to bankruptcy but it certainly didn't seem to stop the senior management from feathering their own nest.
For our society to grow, we need to accept that monopolies are always bad, and only government can create them. There are no natural monopolies. The 4 or 5 times there might have been in the past I'd argue weren't meant to last, but they're gone anyway.
I agree, but governments should control certain natural monopolies for the good of the country as a whole.
Does a monopoly on telecoms infrastructure run and paid for by the government and leased to providers hurt competition? No. It helps by providing a level playing field to all companies. The government can also provide connections to rural areas that a private company would find it uneconomic to serve otherwise. If it makes a profit then tax cuts all round - which I have to say I'm a lot happier about than share dividends for some...
The same can be argued for all other basic services (Water, gas, electricity). The private sector will run a "wait until it breaks" maintenance scheme without really having to face the consequences of failure (discomfort or even death of customers). Ask some New Zealanders about the consequences of unregulated privatisation. The privatised electricity company cut back on maintenance, reported record profits & dividends for shareholders then one of the two power cables to Auckland failed & New Zealand's biggest city had rolling powercuts for weeks while it was fixed.
I'm not some crazy socialist arguing for nationalization of all property but there are just some things that are far too important to leave to the private sector that has repeatedly proved unable to provide the service.
The madness reached its peak/nadir in England when the privatised railway infrastructure monopoly (which had just come off of several years of issuing large dividends to its shareholders) went to the government begging for money because they didn't have enough to do the essential maintenance program that they were being forced to do after the latest fatal rail crash caused by poor track maintenance. Within two days of receiving the money from the government they announced another big dividend for their shareholders.
Monopolies are BAD if a company holds them (Hello M$)
Monopolies can be good if a government administers them responsibly and the alternative (private ownership) is inevitably worse.
Slashdot Mirror
Can't you see it? She wants you bad
:)
Nope, I was just giving the full story before everyone who didn't read TFA went off into paroxysms about 25c/unit over 100,000,000 units...
Anyway, how many small companies are left in the mass market consumer electronics area anyway? Any small companies would be in a niche market and would be in a better position to pass on the costs...
and they're 10c each because they're made in bulk, you know, as in shedloads, as in one of those BIG companies so like I pointed out it won't be 25c/unit it will be less because of the cap.
I'm the last person to defend M$ but just saying $0.25/unit was misrepresenting the situation (probably accidentally) and it needed to be cleared up. It's not destroying small guys as some other posters have suggested because they pay 25c/unit for the first million units & this will clearly be passed on to the consumer at >25c/unit as these things inevitably are.
Gee thanks M$.
I prefer (in an ideal world) the check in comment to be the issue reference + a broad brush description of what was done.
PVCS/Tracker allegedly offers such integration but we've not got it working (not that I personally administer PVCS here) I'd prefer it if we went FOSS for issue tracking & VCS & wrote our own glue if it doesn't exist - it shouldn't be a big job & it's a nice bit of code to donate back that doesn't jeopardise any trade secrets...
The version of PVCS we're stuck with here sucks nuts & I'm pretty sure that a FOSS alternative (in addition to saving a fortune in ongoing support that we don't use) would be at least as good and easier to fix up to meet requirements.
But as it caps at $250,000 the really high volume guys will be able to spread it out more... $250,000/10,000,000 = 2.5c
No you don't, I've had to (far too regularly) go through 5 year old code riddled with tagged bugfixes of various epochs and I can tell you that generally they are more harm than good. Trust me a four year old end of line comment that reads "SRQ 5678" is not helpful to anyone.
What you need to do is have a VCS with a good difference feature built in or read out version 1.23 pre bugfix & version 1.24 post bugfix & do a compare. THAT tells you what was changed to fix the bug better than 25 scattered tags (which may or may not be complete). Then, knowing what was changed you get 1.32 (the latest version) and undo the 1.23 -> 1.24 changes. I have used the VCS to backtrack through 50 revisions to find out who was responsible for certain braindead bugs & what I need to do to unravel them.
Remember, VCS means never having to put bullshit comments like that into your code.
Think of it as a potential invoice
They're working on it - look up "Trusted Computing" sometime
I'm racking my brains for the disc commands is it something like *DISK n?
You might have to switch over to another eprom because the network stuff was non-standard & was implemented by using a different boot eprom IIRC. It's the one on the left of the 4 slots in the basic B as you look from the front (it'll be a plain one not one with a label covering a window). Earth yourself & good luck. Swap out from one to the other to see if I'm right.
I've burned EPROMs for a BEEB before but good luck finding a burner & a 16K eprom these days.
I had a BBC 'B' which put me in a bit of an Elite ;) for a while but relatively limited for games. Revs was good with it's great Silverstone implementation (pre emasculation with all of the chicanes) as was Elite of course...
Somebody's forgotten about (or more likely too young to know about) Dungeon Master which debuted on the Atari ST in 1988 - I remember an Amiga owning friend of mine coming over to play my copy. He later ended up writing a Sci-Fi clone of it called BSS Jane Seymour IIRC for the Amiga.
Those were the days...
I doubt very much if you kept a local copy of the e-mail which you just happened to find & re-send that would be grounds for dismissal.
Getting charged with gross negligence is more likely to get you fired. Keeping hard copies of the e-mail trail would help you during an unfair dismissal case.
What does it taste like?
or this http://www.mapamobile.com/
or this http://www.verilocation.com/
or this http://www.wayhey.com/
Document EVERYTHING in cases like this. Offer advice in the form of an e-mail, print out a copy of the e-mail and file it somewhere safe (like at home). Also never delete the e-mail you sent.
Then when the stuff hits the fan you can defend yourself at the time in public and send another follow up e-mail including the original to back it up to whoever needs to know.
This doesn't work if it's the owner being the jerk but it does cover your butt if a supervisor's trying to push the blame down to save him/herself.
Ok, so we don't get SNL in Australia so I missed the joke but it still shouldn't be informative. Funny - Yes, Informative - No
If they do that to the San Diego Chargers website because of the cheerleader shots I'm going postal...
And can I have some?
Even though this would make the lives of concerned parents (etc) 3,000,000x easier by putting an e-red-light-district on the web to make either finding or filtering pr0n a non-issue.
What a stupid decision.
You know, Cowboy programers. Geddit?
Otto Stern is a spoof column... DUH!
Looks like their little pocket filling sideline of getting their own company to provide the DRM code to Sony has backfired.
F4I is probably going to get sued into oblivion (by Sony if no-one else) so the shares will be worthless but Sony will probably successfully claim ignorance no matter how incompetent that actually makes them seem. Maybe a director or two should get fired.
Time for a class action by all of the violated GPL/LGPL projects (I'm sure there's more than the two we see at the moment) to help gut F4I. Even if 90%+ of the proceeds end up going to lawyers they're being denied to the scum responsible for this shambles.
Also, we need to find out the names of the F4I programmers to make sure they're blacklisted. We as nerds have the control here - we review the resumes/CVs, we do the interviews. We can ensure our companies only hire ethical coders. If you get an application from an ex F4I coder, bring 'em in, waste their time & tell them why they're not getting the job. None of them had the balls to blow the whistle on this scam so they should suffer.
I was 5 (five) hours late home one night because one of railtrack's cut price maintenence bozos took out one bolt too many & dropped a signal gantry onto the main SW rail line in Basingstoke.
Please explain how a supposedly independent rail authority which is issuing huge share dividends is so close to receivership? Surely it is criminally negligent to issue dividends if you are close to bankruptcy but it certainly didn't seem to stop the senior management from feathering their own nest.
Jeez, I'm over 40 now & I played Morrowind to DEATH. Completed Neverwinter Nights, Baldur's Gate, Icewind Dale 1&2 (including all the addons)
You're just not trying hard enough ;)
I agree, but governments should control certain natural monopolies for the good of the country as a whole.
Does a monopoly on telecoms infrastructure run and paid for by the government and leased to providers hurt competition? No. It helps by providing a level playing field to all companies. The government can also provide connections to rural areas that a private company would find it uneconomic to serve otherwise. If it makes a profit then tax cuts all round - which I have to say I'm a lot happier about than share dividends for some...
The same can be argued for all other basic services (Water, gas, electricity). The private sector will run a "wait until it breaks" maintenance scheme without really having to face the consequences of failure (discomfort or even death of customers). Ask some New Zealanders about the consequences of unregulated privatisation. The privatised electricity company cut back on maintenance, reported record profits & dividends for shareholders then one of the two power cables to Auckland failed & New Zealand's biggest city had rolling powercuts for weeks while it was fixed.
I'm not some crazy socialist arguing for nationalization of all property but there are just some things that are far too important to leave to the private sector that has repeatedly proved unable to provide the service.
The madness reached its peak/nadir in England when the privatised railway infrastructure monopoly (which had just come off of several years of issuing large dividends to its shareholders) went to the government begging for money because they didn't have enough to do the essential maintenance program that they were being forced to do after the latest fatal rail crash caused by poor track maintenance. Within two days of receiving the money from the government they announced another big dividend for their shareholders.
Monopolies are BAD if a company holds them (Hello M$)
Monopolies can be good if a government administers them responsibly and the alternative (private ownership) is inevitably worse.