If I understand correctly your comments so far, it looks like you're assuming that sensitivity is at least mostly a function of sensor pixel size, and therefore logically combining adjacent physical pixels would, only the the low end, extend the sensitivity range. I don't know that it works that way, as for all I know the most sensitive sensors require say x photons to hit them during an exposure to register anything, and say the bottom half of a scene is so dark that generally only x - 1 photons hit the pixels on the whole bottom half of the CCD. Then no amount of combining pixels down there will cause any of those pixels to register anything.
If you have to move every few years to keep working in IT, most people would take that to mean that the work is scarce. And wanting to build some equity in a home and hang on to your current friends and not uproot your family and change your kids' schools should not be circumstances of life that make it difficult to find work. When a normal, stable life is incompatible with the field you're in, it's the field, not the life.
How about instead of the feds funding the states, we do the reverse? No more federal taxes of any kind, the states collect all the needed taxes, in whatever forms and ways they each see fit, to meet their share of keeping federal operations afloat.
Hell even candy bar makers warranty their products ("if unsatisfied return the unused portion for a refund"). Why can't record and movie companies follow that example?
Simple: One makes a Baby Ruth and puts it in a plastic wrapper, and the other makes a turd and puts it in a plastic wrapper. Both are bad for you, but that's where the similarity ends.
getting to market has a lot more value than building great tech
The question is, which time? I worked for a dot com that got their first version to market quickly, but it was so shaky technically that it was taking forever trying to build on it for the next version, and the company ultimately failed as a result.
I was thinking, in case a criminal had you at gunpoint and you couldn't click on something without the bad guy noticing, that they could implement a single nod system for reporting crimes.
1) Not a chance. C++ went from being mere "C with classes" a looong time ago. If you program C++ like one does in C, you're doing it wrong. (And wasting the extra power and type-safety -- you may as well just give your source files a.c extension.) C++ has all kinds of gotchas where the compiler is secretly writing code for you and making choices in selecting which classes and functions to use.
As a side note of possible interest, I would be hesitant even to do the converse: Hiring someone to do C++ who has a C++ background without any C background to speak of. For example C++ has references and string objects and container classes, but sometimes it's just simpler or needed to interface with something else to be able and be comfortable/solid with managing your own raw array and pointer arithmetic.
2) This is currently something like the transition I'm trying (trying not as in struggling to learn, but struggling to get hired!) to make. Learning C# was actually fairly painless after mastering C++. Coming from modern C++, C#'s things like generics and lambda functions are not shocking at all, and memory management is much simpler (altho non-memory resource mgmt. is still manual, and a little bit harder due to only limited available determinism).
But the class library is huge, and there's a bunch of co-technologies in.NET that you have to know to be able to produce anything beyond a console app that reads/writes from/to stdin/out. So no, with only a C++ background one would not know WinForms or WPF for desktop GUI apps, or ASPX for web apps, or ASMX or WCF or.NET Remoting for web services and connecting tiers, or ADO.NET or.NET's ORM's for working with databases, etc.
I.e. even in the cases where you're going from a harder to a simpler language, you're not productive in the real world until you can make GUI's, access db's, parse XML, talk to other machines, etc. Which C, C++, and C# (LINQ excepting) don't have built-in to the language such that it's only about learning the language to get hired.
I certainly wouldn't hire, to do C++, a person who's only used Java. As someone else said, it's just not just learning the syntax of a language, but also its idioms. I.e. conventional (e.g. readable and maintainable by those within that language's development community) and proper (e.g. robust) usage. C++ has considerations and complexities a Java-only person has never fathomed.
Oh noes, we're free, so we don't spend every waking moment of our lives working either for the man or society or the state. Individual leisure pursuits -- how terrible.
Hmm, yes, I guess it's only fair that if a driver can aim their car at someone by staring at them, they should be able to thwart the reckless lecher by staring back.
They should also add a blink detection system. To determine who wins.;)
What if later on you need to add logging to the accesses of a member variable for debugging, or protect it with a lock to support a new multi-threaded requirement, as examples. Multiple points of access to a variable is bad, period, not just when it's "external" access, for arbitrary definitions of "external".
I actually liked the 3rd one there. Maybe because I worked on it back in the day. With Simply Village you could just sit and watch the virtual people come and go and the birds flying around and veg.
I might've hit the brakes and then got out and tried to push the car off the highway in whichever was the shortest direction -- at least then you'd have a chance to dive out of the way if a car was coming. I know, easier to judge in hindsight. I've heard of throttle cables sticking, but hadn't heard of one breaking until your story. Guess if I had to choose I'd prefer the former, but with total manual control over the coupling of the engine with the transmission.
Like passing resolutions banning cussing for a week, this is the Calif. legislature trying to do anything but face the problem that has the state in crisis.
If I understand correctly your comments so far, it looks like you're assuming that sensitivity is at least mostly a function of sensor pixel size, and therefore logically combining adjacent physical pixels would, only the the low end, extend the sensitivity range. I don't know that it works that way, as for all I know the most sensitive sensors require say x photons to hit them during an exposure to register anything, and say the bottom half of a scene is so dark that generally only x - 1 photons hit the pixels on the whole bottom half of the CCD. Then no amount of combining pixels down there will cause any of those pixels to register anything.
If you have to move every few years to keep working in IT, most people would take that to mean that the work is scarce. And wanting to build some equity in a home and hang on to your current friends and not uproot your family and change your kids' schools should not be circumstances of life that make it difficult to find work. When a normal, stable life is incompatible with the field you're in, it's the field, not the life.
They know computing skills are a dead-end pursuit in the first world.
How about instead of the feds funding the states, we do the reverse? No more federal taxes of any kind, the states collect all the needed taxes, in whatever forms and ways they each see fit, to meet their share of keeping federal operations afloat.
It might be a start to stop electing so many dang lawyers.
Hell even candy bar makers warranty their products ("if unsatisfied return the unused portion for a refund"). Why can't record and movie companies follow that example?
Simple: One makes a Baby Ruth and puts it in a plastic wrapper, and the other makes a turd and puts it in a plastic wrapper. Both are bad for you, but that's where the similarity ends.
getting to market has a lot more value than building great tech
The question is, which time? I worked for a dot com that got their first version to market quickly, but it was so shaky technically that it was taking forever trying to build on it for the next version, and the company ultimately failed as a result.
Yes, I had to work with code from abroad
Except for the brilliant Paula, I've haven't noticed that they do it any worse. ;)
It's as dead as dead puppies. And dead radio shows aren't much fun.
Same with the American mentality.
It's been 1 minute since you last successfully posted a comment
(Oh gosh, how horrible, someone should alert the police.)
I was thinking, in case a criminal had you at gunpoint and you couldn't click on something without the bad guy noticing, that they could implement a single nod system for reporting crimes.
Anybody who thinks "C++ is C with a few extra things" is very, very wrong.
That and, from TFS:
describes pretty much every developer I've ever worked with at C++ jobs.
In corporate America, democracy capitalizes YOU!
(Had to do it. :)
Exactly. Nothing says "logical" like trusting a company to protect you from a company you don't trust, when it's the same company!
1) Not a chance. C++ went from being mere "C with classes" a looong time ago. If you program C++ like one does in C, you're doing it wrong. (And wasting the extra power and type-safety -- you may as well just give your source files a .c extension.) C++ has all kinds of gotchas where the compiler is secretly writing code for you and making choices in selecting which classes and functions to use.
As a side note of possible interest, I would be hesitant even to do the converse: Hiring someone to do C++ who has a C++ background without any C background to speak of. For example C++ has references and string objects and container classes, but sometimes it's just simpler or needed to interface with something else to be able and be comfortable/solid with managing your own raw array and pointer arithmetic.
2) This is currently something like the transition I'm trying (trying not as in struggling to learn, but struggling to get hired!) to make. Learning C# was actually fairly painless after mastering C++. Coming from modern C++, C#'s things like generics and lambda functions are not shocking at all, and memory management is much simpler (altho non-memory resource mgmt. is still manual, and a little bit harder due to only limited available determinism).
But the class library is huge, and there's a bunch of co-technologies in .NET that you have to know to be able to produce anything beyond a console app that reads/writes from/to stdin/out. So no, with only a C++ background one would not know WinForms or WPF for desktop GUI apps, or ASPX for web apps, or ASMX or WCF or .NET Remoting for web services and connecting tiers, or ADO.NET or .NET's ORM's for working with databases, etc.
I.e. even in the cases where you're going from a harder to a simpler language, you're not productive in the real world until you can make GUI's, access db's, parse XML, talk to other machines, etc. Which C, C++, and C# (LINQ excepting) don't have built-in to the language such that it's only about learning the language to get hired.
I certainly wouldn't hire, to do C++, a person who's only used Java. As someone else said, it's just not just learning the syntax of a language, but also its idioms. I.e. conventional (e.g. readable and maintainable by those within that language's development community) and proper (e.g. robust) usage. C++ has considerations and complexities a Java-only person has never fathomed.
Oh noes, we're free, so we don't spend every waking moment of our lives working either for the man or society or the state. Individual leisure pursuits -- how terrible.
Lobbyists block appointments like unions pass legislation.
Hmm, yes, I guess it's only fair that if a driver can aim their car at someone by staring at them, they should be able to thwart the reckless lecher by staring back.
They should also add a blink detection system. To determine who wins. ;)
What if later on you need to add logging to the accesses of a member variable for debugging, or protect it with a lock to support a new multi-threaded requirement, as examples. Multiple points of access to a variable is bad, period, not just when it's "external" access, for arbitrary definitions of "external".
Single Amanda, 24, from Harpurhey, Manchester,...
She won't be single for long.
Screenshot(s)
I actually liked the 3rd one there. Maybe because I worked on it back in the day. With Simply Village you could just sit and watch the virtual people come and go and the birds flying around and veg.
I might've hit the brakes and then got out and tried to push the car off the highway in whichever was the shortest direction -- at least then you'd have a chance to dive out of the way if a car was coming. I know, easier to judge in hindsight. I've heard of throttle cables sticking, but hadn't heard of one breaking until your story. Guess if I had to choose I'd prefer the former, but with total manual control over the coupling of the engine with the transmission.
Let's make a public registry for people who propose public registries... and the nuisance to society created therein.
Like passing resolutions banning cussing for a week, this is the Calif. legislature trying to do anything but face the problem that has the state in crisis.