Also realize that sometimes a small bug can get fixed if you are in the area of the code where you do some other change like correcting a major bug so just saying that "we don't fix that bug" or killing the small bug issue with a "won't be fixed" statement is essentially stupid.
Tell people that call you to meetings to bugger off. If they insist, have them explain WHY you shall be on that meeting. If they can't give a good explanation just say to them that you have a more important meeting going on at that time. If they still insist that you shall be on their meeting and still can't explain why you shall be there then they are just there to mess up things with their meeting.
The importance of a meeting is inversely proportional to the number of participants. It's usually in the small short meetings that the important decisions are made while in the large meetings there's a lot of talk and little done.
If management were to add bugs into the bug tracker then you would have complete chaos - most managers don't know crap about what the bug reports are about and can't distinguish a bug from an enhancement. Let it be the responsibility of the developer to re-classify bugs that should be enhancements and submit such to a decision board for future enhancements.
If you spend 2-3 days in meetings then that's the primary problem. 90% of all meetings are not productive at all, and that's especially when it comes to information meetings.
If you have more than 4 hours of meetings per week on average then you are wasting valuable time on meetings. In most cases you can actually decline a meeting call without ill effects. Another trick is to schedule work time as meetings so that in your calendar you look busy with other meetings when people try to book you into a meeting.
You forgot the possibility of hibernation ships. If it is possible to slow the metabolism of humans to a very slow rate then it might be possible to reach distant systems.
If we want to settle on a distant planet we are in for a challenge of optimizing the amount of people that can be transferred. Maybe one solution is to freeze semen and embryos and man the space ship with women. Someone calculated that the minimum number of individuals needed to ensure genetic stability is 1600, but I think that 2000 is probably necessary to have a margin for error. But by shipping a large amount of the population as frozen embryos and implant them in women after arrival at a site that can be settled it's possible to do it using a reasonably sized spaceship. It's not going to be easy and it will require planning, sacrifice and some suffering.
But if humankind shall prosper in the long run it's necessary. In 500 million years earth won't be habitable.
Of course - if we can develop warp drive it's going to be easier. Or develop stargates. (Read 'tunnel in the sky' by Heinlein)
That was science as well, it marked the start of a new batch of science data to be processed.
There's always use for old data when doing science, the Viking probe data on Mars is very useful when it comes to analyzing the more modern data from the later probes. Both as a reference and also when new data provides new reference points it can be used to re-evaluate the old Viking data.
From one perspective I can understand that they want to try to keep an unified structure, but from another perspective they also need to accept some variations on how stuff is written and the structure and don't waste time on changing formalities that aren't necessary to change.
I have been a bit annoyed by some changes that are performed by automated bots that Wikipedia has as well, some of those changes are completely redundant and don't enhance the content at all. All those small changes are quite annoying and disruptive for anyone that produces information.
Not that I hope that anyone from Wikipedia ever sees this.
I wouldn't trust that the key won't be sent to a central server by the operating system. There are both intentional and unintentional holes in security everywhere.
I wouldn't say that they make the best development tools around, just that they are decent but still lacks some features that I expect while they have some unnecessary overhead as well.
I just wait until the day some hacker is penetrating a major cloud service and uses the data there for malicious intent. That can result in a disaster for some major companies.
Until you get your computer checked by TSA in the US, then you discover that they have the key to your hard drive. As long as it's just company items and some cached lolcats you are probably safe.
The voter registration process is a much greater limitation to voting that what a nationally recognized ID is. I find it close to amusing that people can get around without any decent ID at all.
It's worse because it's the key to the operating system itself, which would allow random attacker to gain control over your computer and access your data, possible even if it's encrypted with bitlocker.
Slashdot Mirror
No, in-app purchases shouldn't be permitted at all.
The third thing is that in-app purchases is usually a scam.
The penalties for extortion of this kind are way too mild. 25 years to life should be the range.
Add to it that this may be raising the stakes against the bitcoin economy.
Also realize that sometimes a small bug can get fixed if you are in the area of the code where you do some other change like correcting a major bug so just saying that "we don't fix that bug" or killing the small bug issue with a "won't be fixed" statement is essentially stupid.
No, arsonists are productive, management overhead is like pouring cold tar into a machinery.
Tell people that call you to meetings to bugger off. If they insist, have them explain WHY you shall be on that meeting. If they can't give a good explanation just say to them that you have a more important meeting going on at that time. If they still insist that you shall be on their meeting and still can't explain why you shall be there then they are just there to mess up things with their meeting.
The importance of a meeting is inversely proportional to the number of participants. It's usually in the small short meetings that the important decisions are made while in the large meetings there's a lot of talk and little done.
If management were to add bugs into the bug tracker then you would have complete chaos - most managers don't know crap about what the bug reports are about and can't distinguish a bug from an enhancement. Let it be the responsibility of the developer to re-classify bugs that should be enhancements and submit such to a decision board for future enhancements.
If you spend 2-3 days in meetings then that's the primary problem. 90% of all meetings are not productive at all, and that's especially when it comes to information meetings.
If you have more than 4 hours of meetings per week on average then you are wasting valuable time on meetings. In most cases you can actually decline a meeting call without ill effects. Another trick is to schedule work time as meetings so that in your calendar you look busy with other meetings when people try to book you into a meeting.
Deported and he will continue. Solitary confinement or high-security prison in the white power section is what he needs.
You may not agree with his visions, but if you don't agree, then post some constructive criticism instead of posting useless opinions as an AC.
If we don't have people with a vision then we would lack progress.
You forgot the possibility of hibernation ships. If it is possible to slow the metabolism of humans to a very slow rate then it might be possible to reach distant systems.
If we want to settle on a distant planet we are in for a challenge of optimizing the amount of people that can be transferred. Maybe one solution is to freeze semen and embryos and man the space ship with women. Someone calculated that the minimum number of individuals needed to ensure genetic stability is 1600, but I think that 2000 is probably necessary to have a margin for error. But by shipping a large amount of the population as frozen embryos and implant them in women after arrival at a site that can be settled it's possible to do it using a reasonably sized spaceship. It's not going to be easy and it will require planning, sacrifice and some suffering.
But if humankind shall prosper in the long run it's necessary. In 500 million years earth won't be habitable.
Of course - if we can develop warp drive it's going to be easier. Or develop stargates. (Read 'tunnel in the sky' by Heinlein)
Please elaborate, it seems to me that it still exists and I'm not sure what's wrong with it.
That was science as well, it marked the start of a new batch of science data to be processed.
There's always use for old data when doing science, the Viking probe data on Mars is very useful when it comes to analyzing the more modern data from the later probes. Both as a reference and also when new data provides new reference points it can be used to re-evaluate the old Viking data.
Wrong - it's with systemd that Linux will have a very hard time to be enterprise ready.
If just systemd really was easiness, it's definitely just like fishing in muddy water.
No peace until systemd is dead.
From one perspective I can understand that they want to try to keep an unified structure, but from another perspective they also need to accept some variations on how stuff is written and the structure and don't waste time on changing formalities that aren't necessary to change.
I have been a bit annoyed by some changes that are performed by automated bots that Wikipedia has as well, some of those changes are completely redundant and don't enhance the content at all. All those small changes are quite annoying and disruptive for anyone that produces information.
Not that I hope that anyone from Wikipedia ever sees this.
Time to topple the mess the EU is as well.
Warrant canaries can come in many forms, so it's hard for authorities to get proof that something is a warrant canary or not.
App is just a shorthand for Application, so there's no real difference if you look at it closely.
I wouldn't trust that the key won't be sent to a central server by the operating system. There are both intentional and unintentional holes in security everywhere.
I wouldn't say that they make the best development tools around, just that they are decent but still lacks some features that I expect while they have some unnecessary overhead as well.
I just wait until the day some hacker is penetrating a major cloud service and uses the data there for malicious intent. That can result in a disaster for some major companies.
Until you get your computer checked by TSA in the US, then you discover that they have the key to your hard drive. As long as it's just company items and some cached lolcats you are probably safe.
The voter registration process is a much greater limitation to voting that what a nationally recognized ID is. I find it close to amusing that people can get around without any decent ID at all.
It's worse because it's the key to the operating system itself, which would allow random attacker to gain control over your computer and access your data, possible even if it's encrypted with bitlocker.