I got a new iPhone 6s this year. All the Android phones in the store were new models and very expensive with higher monthly fees (that you continue paying even after the phone is paid off). The older iPhones were there, pre-paid with small cost and small monthly bill, and they're still fast and zippy, have headphone jacks, and are big upgrade over my older Samsung.
Ya, this was a pain for me. Drivers license is used, but I never had a social security card (cardboard, hand typed, totally and utterly insecure) so eventually I went and got a new one. I think I've used a birth certificate before, although I may have to get a new one since it's not "long form".
I'm still thinking about the good old days before we had soviet style "homeland" security.
And that was indeed the purpose. They wanted project managers who were not coders to be able to read the code and do code reviews, see if the design matched the specification, and so forth. Before this most programs were in assembler or machine code for an obscure one-off machine, with only a few slightly higher level languages that were scientific or technical in nature (macros). So yes, code reviews existed from the beginning.
At one company I asked the IT guy a networking question since he was supposedly the expert, and he said "well, they really didn't teach that in any of my classes..." So he knew how to do things by following instructions but didn't know how to go beyond that.
The purpose of a college degree is not to teach you a state of the art skill. The purpose is to teach the student how to learn new things, how to research new things, how to adapt to new things, and basically how to learn. If the college does not teach that then the graduates will be obsolete in a few years. If someone just wants to learn the state of the art it can be done more cheaply at a trade school.
In California you're allowed to use a provisional ballot much of the time. Ie, if you move to a new location within the same county but did not re-register you can still vote but with a provisional ballot, and it will get counted as long as it shows you did not vote in any other precinct. If you move to a different county without re-registering, you can still vote with a provisional ballot, it will just take a bit longer to verify. For most hiccups, you can get the provisional ballot.
How do you show proof of citizenship? A driver's license doesn't cut it. No one in the US is issued with a certificate of citizenship when they are born. My birth certificate may not even count for me to get my Real ID as now apparently I may have to apply for a "long form" version. A passport may work, but very few in America have those or carry them around everywhere. To register I prove my identity, but not my citizenship, but check a box that I agree under penalty of perjury that I am a citizen.
In my view, every citizen should vote with as FEW hurdles to jump over as possible. Getting more people to vote is better, even if they're going to vote the opposite of how I vote.
I think this is because Republican states are the most intent to prevent those who might lean Democratic from voting. That's the poor, minorities, college students, etc. In Democratic leaning states it is much more difficult to prevent or discourage rich whites from voting.
You can get jobs without ID. You need a social security number, but you don't need ID for that. The problem is that the people for whom voter IDs are difficult to get tend to be the sorts of people who don't vote the way the powers that be want them to. Ie, the poor, the elderly shut-ins, the homeless, widows who never needed this stuff until after the husbands died, etc.
When elections are tight, disenfranchising a very tiny minority is enough to sway elections.
Getting a driver's license is a royal pain in the ass in many places. A identity card from the DMV is similar. People are reporting 8 hour waits at the DMV in California (because of the increased demand for the ridiculous Real ID cards that you can only get in person), and I had to book an appointment 3 months in advance for the DMV!
There is a problem that many in the US do not believe voting is a right, and they're greatly opposed to the wrong sorts of people voting since they might vote for the wrong things. There are those who don't want college students to vote, since they're not in the country for a full 12 months. There are those who don't want convicted felons to vote even after they are out of prison. There are even those suspicious of members of the military voting when they are stationed overseas.
I suspect it might go over better if the upper area had icons appearing on a black background. It would serve the same purpose only it wouldn't look like a notch and it wouldn't look like a copy of a feature. I think using the notch emphasizes more that the screen is larger (sort of), which is why it's used.
How do you know most people aren't using the headphone jack? Headphones came with my iPhone, headphones came with my previous Android phone, so it's clear that many customers already have the headphones (well, earbuds). Removing the headphone jack means that now uses need to obtain bluetooth headphones or a headphone adapter. Did the later iPhones ship with those?
This really depends upon where you are in your time zone - those in the far east of it have a very different experience than those in the far west of the same time zone. Note that many time zones deviate quite far from longitudinal lines because of politics. Ie, both eastern Main and the Florida panhandle are in the same Eastern Time zone and yet are more than a full hour apart from each other relative to solar time.
Otherwise after a decade or two after moving to Summer Time permanently they'll want to create Winter Time so that it's not so dark in some locations, and the cycle starts over.
The plan by many is to stay with DST permanently, rather than using standard time. That's the equivalent of saying you want to be in the next time zone over. In summer when the days are longest the choice of using DST or not is not very important, but in winter it will matter much more. The real solution here is to either get rid of time zones altogether, or have regions be more flexible about when school start and the like.
Agile is not just for IT, or even primarily for IT, it's just a product development style. DevOps is mostly an IT thing, it only makes sense in the context of having customer facing servers; so you make operations and development the same group, despite no commonality in skill sets, so that you don't have to hire as many people. Lean IT I dunno, I haven't done IT since the 80s, but it was always lean and underfunded back then. But they're most certainly NOT the same thing.
I can see Windows XP being used on my Dentist's computer...
Of course, ignorance IS an issue here. And that ignorance is not just the programmer's, but with system designers, marketing, documentation, etc. I worked on a medical system that used local time. The assumption was that it was not going to cross time zone boundaries very often, but this broke when a hospital system would straddle time zones, or the server was in a different time zone than the machine, and so forth. Never mind that the standard used by medical images will have the time zone specified as offset from UTC; this means that the system has to be able to convert to and from this style and so you'll get bugs. You can't really blame the junior programmer who was tasked with this as his first job.
Many operating systems and the like do NOT use UTC. Ie, Windows 95 did not, it assumed the PC RTC chip was using local time. It may have converted to UTC internally in a few places, but not many. Many embedded systems come with libraries that use UTC but which assume that time zone is just an offset from that. Many embedded systems actually use local time because that is what the customers and the designers assume will be used, and then add-on cards using UTC have to do some complex interactions. It is also common for embedded systems and RTOS's to not have a reliable or well documented system of time (sort of POSIX-like functions with the first letter capitalized); and simultaneously the compiler runtime library will have its own competing functions which will clash. And because most of these systems are built from scratch, since the common libraries are too large, you rely on mere programmers to become subject matter experts, meaning you will get bugs.
The "deletion" happens even when there's not a real database, it can happen because a system internally has a hard requirement of not having duplicates. And if time is not stored as UTC then you end up with two hours that look the same (1AM PST and 1AM PDT only they leave off the suffix). Seriously, there are systems that separate the date from the time of day and the time is represented as seconds since midnight local time.
Quite often the functionality isn't built in to some systems. I've had to write this stuff a few times, and have had to fix bugs with it in other systems. Today you'd think that with the religious mantra to never write your own code and only use existing libraries that this problem would go away, and yet people still don't even know how to use their basic C library correctly to do this.
You'd think it was obvious - and yet remember how Windows 95 had you manually ask you if it should change the time twice a year despite every programmer working on it knowing that DST was a real thing and that they sold the product to nearly all time zones. It seems that this is one of those things that often falls through the cracks by the designers and is left to someone low down on the totem pole to notice and try to patch up.
Even last year we had to write code to convert from a device's concept of time to UTC time, and I had to explain how this all worked multiple times, I drew diagrams multiple times, and so forth. Some of it was my fault, I assumed the device behaved logically when it was absolutely being stupid (log data every hour and assumed that every single day always had 24 hours no matter what, so when time changed it would either duplicate an entry or it would drop an entry.
A: "Why are you in charge of the design?" B: "Because I'm a medical records expert!" A: "Do you understand time zones, DST, and all their implications?" B: "It's just time, how hard can it be? I'm sure all the junior programmers working on it understand that stuff."
The problem here is that medical software is generally old. Programmers naively expect everyone to update software constantly, which is not feasible when the updates are expensive and require additional training. Doesn't help that a lot times the software chosen is the one that had the lowest bid. People bitch about the cost of medical care, but in reality hospitals and clinics are usually on a shoe-string budget when it comes to big budget items.
Slashdot Mirror
I got a new iPhone 6s this year. All the Android phones in the store were new models and very expensive with higher monthly fees (that you continue paying even after the phone is paid off). The older iPhones were there, pre-paid with small cost and small monthly bill, and they're still fast and zippy, have headphone jacks, and are big upgrade over my older Samsung.
Ya, this was a pain for me. Drivers license is used, but I never had a social security card (cardboard, hand typed, totally and utterly insecure) so eventually I went and got a new one. I think I've used a birth certificate before, although I may have to get a new one since it's not "long form".
I'm still thinking about the good old days before we had soviet style "homeland" security.
And that was indeed the purpose. They wanted project managers who were not coders to be able to read the code and do code reviews, see if the design matched the specification, and so forth. Before this most programs were in assembler or machine code for an obscure one-off machine, with only a few slightly higher level languages that were scientific or technical in nature (macros). So yes, code reviews existed from the beginning.
At one company I asked the IT guy a networking question since he was supposedly the expert, and he said "well, they really didn't teach that in any of my classes..." So he knew how to do things by following instructions but didn't know how to go beyond that.
The purpose of a college degree is not to teach you a state of the art skill. The purpose is to teach the student how to learn new things, how to research new things, how to adapt to new things, and basically how to learn. If the college does not teach that then the graduates will be obsolete in a few years. If someone just wants to learn the state of the art it can be done more cheaply at a trade school.
In California you're allowed to use a provisional ballot much of the time. Ie, if you move to a new location within the same county but did not re-register you can still vote but with a provisional ballot, and it will get counted as long as it shows you did not vote in any other precinct. If you move to a different county without re-registering, you can still vote with a provisional ballot, it will just take a bit longer to verify. For most hiccups, you can get the provisional ballot.
How do you show proof of citizenship? A driver's license doesn't cut it. No one in the US is issued with a certificate of citizenship when they are born. My birth certificate may not even count for me to get my Real ID as now apparently I may have to apply for a "long form" version. A passport may work, but very few in America have those or carry them around everywhere. To register I prove my identity, but not my citizenship, but check a box that I agree under penalty of perjury that I am a citizen.
In my view, every citizen should vote with as FEW hurdles to jump over as possible. Getting more people to vote is better, even if they're going to vote the opposite of how I vote.
I think this is because Republican states are the most intent to prevent those who might lean Democratic from voting. That's the poor, minorities, college students, etc. In Democratic leaning states it is much more difficult to prevent or discourage rich whites from voting.
You can get jobs without ID. You need a social security number, but you don't need ID for that. The problem is that the people for whom voter IDs are difficult to get tend to be the sorts of people who don't vote the way the powers that be want them to. Ie, the poor, the elderly shut-ins, the homeless, widows who never needed this stuff until after the husbands died, etc.
When elections are tight, disenfranchising a very tiny minority is enough to sway elections.
Getting a driver's license is a royal pain in the ass in many places. A identity card from the DMV is similar. People are reporting 8 hour waits at the DMV in California (because of the increased demand for the ridiculous Real ID cards that you can only get in person), and I had to book an appointment 3 months in advance for the DMV!
There is a problem that many in the US do not believe voting is a right, and they're greatly opposed to the wrong sorts of people voting since they might vote for the wrong things. There are those who don't want college students to vote, since they're not in the country for a full 12 months. There are those who don't want convicted felons to vote even after they are out of prison. There are even those suspicious of members of the military voting when they are stationed overseas.
It may be high quality engineering where the goals are not to provide customer security but to provide corporate profits.
I suspect it might go over better if the upper area had icons appearing on a black background. It would serve the same purpose only it wouldn't look like a notch and it wouldn't look like a copy of a feature. I think using the notch emphasizes more that the screen is larger (sort of), which is why it's used.
How do you know most people aren't using the headphone jack? Headphones came with my iPhone, headphones came with my previous Android phone, so it's clear that many customers already have the headphones (well, earbuds). Removing the headphone jack means that now uses need to obtain bluetooth headphones or a headphone adapter. Did the later iPhones ship with those?
This really depends upon where you are in your time zone - those in the far east of it have a very different experience than those in the far west of the same time zone. Note that many time zones deviate quite far from longitudinal lines because of politics. Ie, both eastern Main and the Florida panhandle are in the same Eastern Time zone and yet are more than a full hour apart from each other relative to solar time.
Otherwise after a decade or two after moving to Summer Time permanently they'll want to create Winter Time so that it's not so dark in some locations, and the cycle starts over.
The plan by many is to stay with DST permanently, rather than using standard time. That's the equivalent of saying you want to be in the next time zone over. In summer when the days are longest the choice of using DST or not is not very important, but in winter it will matter much more. The real solution here is to either get rid of time zones altogether, or have regions be more flexible about when school start and the like.
What if I don't drink coffee?
Agile is not just for IT, or even primarily for IT, it's just a product development style. DevOps is mostly an IT thing, it only makes sense in the context of having customer facing servers; so you make operations and development the same group, despite no commonality in skill sets, so that you don't have to hire as many people. Lean IT I dunno, I haven't done IT since the 80s, but it was always lean and underfunded back then. But they're most certainly NOT the same thing.
I can see Windows XP being used on my Dentist's computer...
Of course, ignorance IS an issue here. And that ignorance is not just the programmer's, but with system designers, marketing, documentation, etc. I worked on a medical system that used local time. The assumption was that it was not going to cross time zone boundaries very often, but this broke when a hospital system would straddle time zones, or the server was in a different time zone than the machine, and so forth. Never mind that the standard used by medical images will have the time zone specified as offset from UTC; this means that the system has to be able to convert to and from this style and so you'll get bugs. You can't really blame the junior programmer who was tasked with this as his first job.
Many operating systems and the like do NOT use UTC. Ie, Windows 95 did not, it assumed the PC RTC chip was using local time. It may have converted to UTC internally in a few places, but not many. Many embedded systems come with libraries that use UTC but which assume that time zone is just an offset from that. Many embedded systems actually use local time because that is what the customers and the designers assume will be used, and then add-on cards using UTC have to do some complex interactions. It is also common for embedded systems and RTOS's to not have a reliable or well documented system of time (sort of POSIX-like functions with the first letter capitalized); and simultaneously the compiler runtime library will have its own competing functions which will clash. And because most of these systems are built from scratch, since the common libraries are too large, you rely on mere programmers to become subject matter experts, meaning you will get bugs.
The "deletion" happens even when there's not a real database, it can happen because a system internally has a hard requirement of not having duplicates. And if time is not stored as UTC then you end up with two hours that look the same (1AM PST and 1AM PDT only they leave off the suffix). Seriously, there are systems that separate the date from the time of day and the time is represented as seconds since midnight local time.
Quite often the functionality isn't built in to some systems. I've had to write this stuff a few times, and have had to fix bugs with it in other systems. Today you'd think that with the religious mantra to never write your own code and only use existing libraries that this problem would go away, and yet people still don't even know how to use their basic C library correctly to do this.
You'd think it was obvious - and yet remember how Windows 95 had you manually ask you if it should change the time twice a year despite every programmer working on it knowing that DST was a real thing and that they sold the product to nearly all time zones. It seems that this is one of those things that often falls through the cracks by the designers and is left to someone low down on the totem pole to notice and try to patch up.
Even last year we had to write code to convert from a device's concept of time to UTC time, and I had to explain how this all worked multiple times, I drew diagrams multiple times, and so forth. Some of it was my fault, I assumed the device behaved logically when it was absolutely being stupid (log data every hour and assumed that every single day always had 24 hours no matter what, so when time changed it would either duplicate an entry or it would drop an entry.
A: "Why are you in charge of the design?"
B: "Because I'm a medical records expert!"
A: "Do you understand time zones, DST, and all their implications?"
B: "It's just time, how hard can it be? I'm sure all the junior programmers working on it understand that stuff."
The problem here is that medical software is generally old. Programmers naively expect everyone to update software constantly, which is not feasible when the updates are expensive and require additional training. Doesn't help that a lot times the software chosen is the one that had the lowest bid. People bitch about the cost of medical care, but in reality hospitals and clinics are usually on a shoe-string budget when it comes to big budget items.
I mean the dinosaurs!
Merde!