Neither of these are bad questions. In fact they're pretty damn good.
Question 1- a title is supposed to inform you on what the story is about. That makes option (a) a bad choice. The sun is in the story, but is not a central actor. Option (d) is also a bad choice, it would make a relatively unimportant part the theme.
Options b and c are harder to pick between, and I think that someone who chooses b isn't completely wrong. So I think having that option was a mistake. But (c) requires you to correctly identify the theme of the story, that the weather forces change in Timmy's actions.
Question 2- requires the child to think about why he needed to change socks. This requires him to go beyond the word and analyze the story, interpreting facts not explicitly mentioned and using common sense. This is an INCREDIBLY important skill that needs to be taught early.
This is EXACTLY what they should be teaching. Critical thinking and the ability to reason about the text.
Never worked in a webshop. Nor do I have any interest in doing so- rather boring work, and I'm not artistic at all. I've switched from firmware to backend web services (back before there were frameworks and a billion scripting languages, these were written in C++), to cross platform mobile software (pre-iOS, where that meant working on Symbian, Windows Mobile, and a half dozen proprietary OSes writing in very resource sparse environments), to doing Android work for the last few years. I've never failed to start fixing bugs in week one. I've been a team lead and I've made sure even new college hires were in the same place- we were getting at least significant bug fixes from them in the first two weeks.
For that matter I have done a little web work on the side- a local non-profit needed an ERP system altered at a charity hackathon last weekend. I'd never done PHP before. I had the necessary changes finished in 24 hours anyway.
If you really take 2 months, you are really fucking bad. The only question is whether you're bad at all programming, whether you just don't know how to read code and come up to speed, or whether you're just bad at making yourself useful while not knowing anything. The last 2 actually can be trained, and I've had to help experienced devs do that. But 2 months is not acceptable- if you weren't useful by the end of 2 months I'd be assuming you never would be and working to get you fired.
If its running on your phone and you have an email app that downloads messages to your phone, it could be reading those files and sending them back to Linkedin. It wouldn't really be redirecting it, but it would be copying it and sending it back there.
Which is why I'm very careful with what apps I download. If the website provides the same services, why would I download an app?
Re: It was already a dangerous site to visit ...
on
PHP.net Compromised
·
· Score: 4, Insightful
That is quite possibly the worst idea I've ever heard. So I either have a hash lookup on each parameter on every function call (which will CRUSH performance in any language), or a very complicated system for the compiler to implement. Then as a user I not only need to remember what the parameters are for every function, but what they were named? Which basically means it would need to be looked up every time, because I am not remembering all that. You're looking at an order of magnitude slowdown in writing code. Just a stupid idea.
If you're really taking 3-6 months to be useful, you're incompetent. There hasn't been a job I started in the last decade where I wasn't fixing bugs by the end of week one. (I had a joke at my last job that my first day I fixed 2 bugs with 0 lines of code- one was fixed by adding a line, one was fixed by deleting a line). Now if there's a large existing codebase it may take months to know all the ins and outs, but you should be contributing within a week.
Fresh college grads are an exception here- they need more handholding. But even with them if you give them the correct jobs you can start getting something useful out of them by the end of week 2. They'll just take longer to hit their real peak performance.
DevOps rarely means a build only guy- those are called build engineers. Generally they mean a developer with sysadmin experience (possibly a sysadmin who wants to transition) or a developer with experience dealing with configuration of servers/services- the guy who'd be configuring Apache, keeping your DB running, etc. He might be asked to set up the build system, but that wouldn't be his primary job.
Oh, I do. But while they may use a few other types of diagrams, nobody uses UML to draw them. Especially not state diagrams- they got those completely wrong, and completely different from how existing disciplines like EE do them.
(For that matter most class diagrams don't use UML either- if you aren't going to be nitpickingly formal it adds nothing. The only time you'll see it is when its automatically generated).
Where did I say i wouldn't develop for Android? I've been doing so professionally since 1.6. I was saying that (almost) nobody should be targeting 4.0, Its still a 2.3 world for another year or two, unless you absolutely need functionality added since then.
Welcome to the late 90s. Out here 15 years later, nobody uses UML. The idea of UML as code is completely dead, the corpse was staked, burned, and scattered to the four winds. It never worked. The only thing that's left of it is class diagrams, which people were doing 20 years before UML existed (if not longer).
Most companies would want to make 2.3 the minimum still. It's still about 25% of the install base, last I checked (as measured by downloads in the last month off of Play). 2.2 is in the low single digit percents, its not worth the trouble. But you can't drop 25% of your potential customers.
On something like this it's an easy fight, if you'd be forced to relocate. The reason more aren't won is that in cases like this they simply offer severance and avoid the lawsuits.
Most compilers do make this at least a warning. It isn't an error because it's a moderately common C-ism to do this in order to assign and check the return value or a function in 1 statement. Particularly if the value is a standard 0 on error or NULL on error return.
Sure. I worked at a startup once where one junior scripter just stopped coming in. It was right after a bit of a reorg, so nobody was really sure who his boss was. He hadn't been there long and came in with a huge hiring spurt, so nobody missed him. What he was doing was so unimportant, nobody noticed the lack of output. We figured it out 3 months later- he hadn't signed up for direct deposit, so the paper checks piled up on his desk and was eventually noticed by our receptionist. If he had just been smart enough to have set up deposit he likely could have gotten checks until the buyout.
In the end I don't think he ever got paid for more than a month or so of that time- he claimed he put in a 2 week notice via email, he was already working somewhere with a better offer.
Actually in large parts of the US they're open to lawsuits for constructive dismissal, if the office isn't nearby. Being forced to drive 10 miles to the office wouldn't likely work, but if it would force you to relocate it would definitely qualify. Most likely anyone who is forced to change by this policy will be offered some severance if they don't want to change, just to avoid the lawsuits.
They make the printers themselves (and the pens, which have just as much tech in them), massive development centers in San Diego, Boise, and Vancouver WA. So not really reselling stuff on that part.
Source: worked for the all in one team in San Diego a decade or so ago.
In the US, a comma is used to separate millions, thousands, hundreds, etc. A period is used to separate whole numbers from decimals. So 2,300 is 200 more than 2100.
They still sell smaller phones in HVGA sizes. There's not a lot of demand for them though- they're difficult to use (fonts are so small most people can't click on links well), the keyboards are almost impossible to manipulate, and there's so little screen real estate that most apps won't fit on them. Basically there so annoying to use most people who want that size prefer a cheap dumb phone.
For myself, I want something even bigger- I'll be picking up either a note 3 or a galaxy mega in the next few weeks. I want the biggest screen that will still fit in my pocket, it makes actually using the phone for internet, apps, or navigation MUCH easier.
Except that 95% of the market isn't serious about taking photographs. That's why photography studios across the country died- ubiquitous smart phone cameras were good enough. Same for professional photographers- most of them have found new careers, because except for weddings there's no demand anymore.
Digital camera sales have plateaued and are now decreasing (by 18% year over year worldwide, 43% in north america). Nobody carries a camera around anymore, phones take a good enough picture (probably just as good given the skills of the people using them) and are more convenient to carry- heck you're carrying them anyway. At parties where before a couple people might bring their cameras, now nobody does- they pull out their phone.
So yeah, a better smart phone camera would address a large market- everyone who enjoys taking photos, but doesn't do art photos. I know a good number of people who tossed their digital cameras away but take the camera into consideration when buying a phone.
Every Nexus device going back the very first has been an existing phone with a few minor upgrades at most and a different set of software installed. Why would anyone expect different this time? My only surprise is that Google hasn't started having their Motorola arm manufacture them yet. Probably due to not wanting to push OEMs to other options.
Over a wristwatch? Probably, except they tend to be more expensive, being a niche market. Over just using my cell? No- why carry a second thing that does a tiny subset of something else I already carry? Just another thing to lose.
Also an advantage of the cell phone- synching time with the phone network. You never have to worry about it running out of synch, or being on the wrong timezone. Rarely a feature of a watch- even the better ones slowly go out of synch, unless you spend really huge numbers on it.
Slashdot Mirror
No, they can't. The problem is you're an idiot.
Neither of these are bad questions. In fact they're pretty damn good.
Question 1- a title is supposed to inform you on what the story is about. That makes option (a) a bad choice. The sun is in the story, but is not a central actor. Option (d) is also a bad choice, it would make a relatively unimportant part the theme.
Options b and c are harder to pick between, and I think that someone who chooses b isn't completely wrong. So I think having that option was a mistake. But (c) requires you to correctly identify the theme of the story, that the weather forces change in Timmy's actions.
Question 2- requires the child to think about why he needed to change socks. This requires him to go beyond the word and analyze the story, interpreting facts not explicitly mentioned and using common sense. This is an INCREDIBLY important skill that needs to be taught early.
This is EXACTLY what they should be teaching. Critical thinking and the ability to reason about the text.
Apple can't have bugs like this- it just works. Maybe they're sending it wrong?
Never worked in a webshop. Nor do I have any interest in doing so- rather boring work, and I'm not artistic at all. I've switched from firmware to backend web services (back before there were frameworks and a billion scripting languages, these were written in C++), to cross platform mobile software (pre-iOS, where that meant working on Symbian, Windows Mobile, and a half dozen proprietary OSes writing in very resource sparse environments), to doing Android work for the last few years. I've never failed to start fixing bugs in week one. I've been a team lead and I've made sure even new college hires were in the same place- we were getting at least significant bug fixes from them in the first two weeks.
For that matter I have done a little web work on the side- a local non-profit needed an ERP system altered at a charity hackathon last weekend. I'd never done PHP before. I had the necessary changes finished in 24 hours anyway.
If you really take 2 months, you are really fucking bad. The only question is whether you're bad at all programming, whether you just don't know how to read code and come up to speed, or whether you're just bad at making yourself useful while not knowing anything. The last 2 actually can be trained, and I've had to help experienced devs do that. But 2 months is not acceptable- if you weren't useful by the end of 2 months I'd be assuming you never would be and working to get you fired.
If its running on your phone and you have an email app that downloads messages to your phone, it could be reading those files and sending them back to Linkedin. It wouldn't really be redirecting it, but it would be copying it and sending it back there.
Which is why I'm very careful with what apps I download. If the website provides the same services, why would I download an app?
That is quite possibly the worst idea I've ever heard. So I either have a hash lookup on each parameter on every function call (which will CRUSH performance in any language), or a very complicated system for the compiler to implement. Then as a user I not only need to remember what the parameters are for every function, but what they were named? Which basically means it would need to be looked up every time, because I am not remembering all that. You're looking at an order of magnitude slowdown in writing code. Just a stupid idea.
If you're really taking 3-6 months to be useful, you're incompetent. There hasn't been a job I started in the last decade where I wasn't fixing bugs by the end of week one. (I had a joke at my last job that my first day I fixed 2 bugs with 0 lines of code- one was fixed by adding a line, one was fixed by deleting a line). Now if there's a large existing codebase it may take months to know all the ins and outs, but you should be contributing within a week.
Fresh college grads are an exception here- they need more handholding. But even with them if you give them the correct jobs you can start getting something useful out of them by the end of week 2. They'll just take longer to hit their real peak performance.
DevOps rarely means a build only guy- those are called build engineers. Generally they mean a developer with sysadmin experience (possibly a sysadmin who wants to transition) or a developer with experience dealing with configuration of servers/services- the guy who'd be configuring Apache, keeping your DB running, etc. He might be asked to set up the build system, but that wouldn't be his primary job.
Oh, I do. But while they may use a few other types of diagrams, nobody uses UML to draw them. Especially not state diagrams- they got those completely wrong, and completely different from how existing disciplines like EE do them.
(For that matter most class diagrams don't use UML either- if you aren't going to be nitpickingly formal it adds nothing. The only time you'll see it is when its automatically generated).
Where did I say i wouldn't develop for Android? I've been doing so professionally since 1.6. I was saying that (almost) nobody should be targeting 4.0, Its still a 2.3 world for another year or two, unless you absolutely need functionality added since then.
Welcome to the late 90s. Out here 15 years later, nobody uses UML. The idea of UML as code is completely dead, the corpse was staked, burned, and scattered to the four winds. It never worked. The only thing that's left of it is class diagrams, which people were doing 20 years before UML existed (if not longer).
Most companies would want to make 2.3 the minimum still. It's still about 25% of the install base, last I checked (as measured by downloads in the last month off of Play). 2.2 is in the low single digit percents, its not worth the trouble. But you can't drop 25% of your potential customers.
On something like this it's an easy fight, if you'd be forced to relocate. The reason more aren't won is that in cases like this they simply offer severance and avoid the lawsuits.
There are in many states. I can't comment on yours, but even a simple search proves you wrong.
Most compilers do make this at least a warning. It isn't an error because it's a moderately common C-ism to do this in order to assign and check the return value or a function in 1 statement. Particularly if the value is a standard 0 on error or NULL on error return.
Sure. I worked at a startup once where one junior scripter just stopped coming in. It was right after a bit of a reorg, so nobody was really sure who his boss was. He hadn't been there long and came in with a huge hiring spurt, so nobody missed him. What he was doing was so unimportant, nobody noticed the lack of output. We figured it out 3 months later- he hadn't signed up for direct deposit, so the paper checks piled up on his desk and was eventually noticed by our receptionist. If he had just been smart enough to have set up deposit he likely could have gotten checks until the buyout.
In the end I don't think he ever got paid for more than a month or so of that time- he claimed he put in a 2 week notice via email, he was already working somewhere with a better offer.
Actually in large parts of the US they're open to lawsuits for constructive dismissal, if the office isn't nearby. Being forced to drive 10 miles to the office wouldn't likely work, but if it would force you to relocate it would definitely qualify. Most likely anyone who is forced to change by this policy will be offered some severance if they don't want to change, just to avoid the lawsuits.
They make the printers themselves (and the pens, which have just as much tech in them), massive development centers in San Diego, Boise, and Vancouver WA. So not really reselling stuff on that part.
Source: worked for the all in one team in San Diego a decade or so ago.
Please. Carly killed it over a decade ago.
Trust me, we all know when you glance at your watch. It isn't nearly as subtle as you think.
In the US, a comma is used to separate millions, thousands, hundreds, etc. A period is used to separate whole numbers from decimals. So 2,300 is 200 more than 2100.
They still sell smaller phones in HVGA sizes. There's not a lot of demand for them though- they're difficult to use (fonts are so small most people can't click on links well), the keyboards are almost impossible to manipulate, and there's so little screen real estate that most apps won't fit on them. Basically there so annoying to use most people who want that size prefer a cheap dumb phone.
For myself, I want something even bigger- I'll be picking up either a note 3 or a galaxy mega in the next few weeks. I want the biggest screen that will still fit in my pocket, it makes actually using the phone for internet, apps, or navigation MUCH easier.
Except that 95% of the market isn't serious about taking photographs. That's why photography studios across the country died- ubiquitous smart phone cameras were good enough. Same for professional photographers- most of them have found new careers, because except for weddings there's no demand anymore.
Digital camera sales have plateaued and are now decreasing (by 18% year over year worldwide, 43% in north america). Nobody carries a camera around anymore, phones take a good enough picture (probably just as good given the skills of the people using them) and are more convenient to carry- heck you're carrying them anyway. At parties where before a couple people might bring their cameras, now nobody does- they pull out their phone.
So yeah, a better smart phone camera would address a large market- everyone who enjoys taking photos, but doesn't do art photos. I know a good number of people who tossed their digital cameras away but take the camera into consideration when buying a phone.
Every Nexus device going back the very first has been an existing phone with a few minor upgrades at most and a different set of software installed. Why would anyone expect different this time? My only surprise is that Google hasn't started having their Motorola arm manufacture them yet. Probably due to not wanting to push OEMs to other options.
Hate? No. They're something that used to fill an important purpose but are no longer needed. The 21st century equivalent of buggy whips.
Over a wristwatch? Probably, except they tend to be more expensive, being a niche market. Over just using my cell? No- why carry a second thing that does a tiny subset of something else I already carry? Just another thing to lose.
Also an advantage of the cell phone- synching time with the phone network. You never have to worry about it running out of synch, or being on the wrong timezone. Rarely a feature of a watch- even the better ones slowly go out of synch, unless you spend really huge numbers on it.