Do people really print? I haven't owned a printer in 10 years, and I used to write firmware for them.
The real problem will be typing. Whether its inputting in a form or sending an email, eventually you want a physical keyboard and not an onscreen one. My limit before I get annoyed with onscreens is about 200 characters- anything longer I wait until I'm at home.
Pretty much every place I worked. A well run HR department treats talent retention as a key job priority. Replacing and training a mediocre staff member takes months and thousands of dollars in cash and manpower, an above average one may take 10s of thousands and multiple people to do his old job. I've seen far more managers retrained or kicked out of the company than I've seen programmers, middle managers are easy to replace.
As for career opportunities- stop worrying about them. I don't want to be a manager. Except for a possible job as a tech lead/manager at a startup I'd be miserable doing it, I can read politics but I don't like to play games. You work at a job for a few years while it's fun. When it starts getting boring (long term boring, not just boring for a few days of documentation or the like) you look for somewhere else to work (which may be a transfer within the company, but most likely isn't).
I'm not looking to stay at one place for 5-10 years (my longest stay was 4, and I regret that but it was my first job. My lowest non-contract was 2). Besides, you get promotions and raises at a faster rate by moving on then playing the corporate games and trying to "climb the ladder". I've gotten raises of above 10% every time I switched jobs, doing that every 2 years or so is more money than you'd get staying at a place. I've gotten title raises with each, if those matter to you (although they shouldn't, titles are pointless and who does the work has nothing to do with who has the title). If you're looking for a more technical lead type role, that's also more easily obtained by moving- otherwise you're waiting for your lead or a closely related team's lead to leave or another team to be made and pick you. You're focusing totally wrong by thinking of a company career.
And its macho bullshitters like you who want to drag us down and become a hellhole. But I accept your thanks, while it has flaws this is a great country and people like me just make it better.
No, what I am is good, economically frugal (plenty of cash in the bank), and quite happy to go back on the job market to find something better if I need to. Life is to short to work somewhere you're treated like shit. They can spend the 6 months and thousands of dollars it would cost to replace me if they want, I'll have another job in 3 weeks if I'm not being picky, 2 months if I am.
No he's not. First off, in very few companies can the boss actually fire you at whim- they usually have procedures that need to be followed that take a great deal of time.
Secondly, if you're any good they probably can't afford to lose you, at least not quickly. If I was fired, milestones wouldn't be met for the next 6 months- not because I don't document my work for others (I do), but because training any replacement would take that long to know the codebase as well as I do. That's assuming they had someone of my skillset on tap- highly unlikely, finding a replacement would take another 6 months, or require multiple people. It would be easier to replace my manager than me.
Third, even if he does- you're better off not working for that asshole. Always keep at least 6 months reserve in the bank, and don't worry about it. Life's too short to work at a shitty place or for shitty people. I'd rather quit and take it easy for a week or two while I find a new job. And for programmers that's pretty easy these days, there's a lot more openings than good programmers. I get cold called by recruiters on a weekly bases.
Bullshit. If someone is fucking up (especially repeatedly), the boss should talk to him. Not scream at him- talk in a professional manner. Or let him go, if the mistakes are bad enough. You do not disrespect your employees by screaming them- it solves nothing, causes workplace friction, lowers morale of both the one being screamed at, the one screaming, and their coworkers. Its counterproductive.
If my boss came to my office and calmly told me I fucked up, I'd immediately jump on the problem and fix it. If my boss came in screaming at me, I'd tell him to get the fuck out, send an email to HR detailing his unacceptable behavior causing a hostile work environment and go home- telling him I'd return upon getting a sincere apology, and that I would expect full pay for every day in the interim. Oh, and my resumes would be on the net that evening. If he really pissed me off I'd go to his boss and tell him its me or him and I want a decision by the end of the day. There is no excuse for not behaving like an adult in the workplace.
Things like using solid variable/function names, providing sufficient (and quality) comments, and keeping similarity in architectural style matter. How many spaces you use (as long as you use some indentation) or what style of variable names you use makes no difference. And anyone who brings it up in a code review should be shouted down- the purpose of a code review is to find bugs, missed corner cases, unintended consequences of a change, and to find alternate ways to solve a problem. It is not there for cosmetic issues, and anyone who brings them up is wasting time for no gain and makes the code reviews of the entire organization less useful.
Because your examples are false equivalency. Just because each party produces some waste doesn't mean both are equally bad. There's only one party that put two wars on the credit card while cutting taxes. It wasn't the democrats. And there's only one party that continually tries to either lower tax rates or rebate taxes on every surplus. It isn't the Democrats. Just because both make mistakes doesn't mean they're equally bad, one can definitely be far worse.
I had a Galaxy S until I recently lost it. It had the default app layout (which basically meant google apps only, non of the OEM crud). I noticed a significant slowdown in many apps (especially the browser) moving from 2.3 to 4.0. It wasn't horrible, but it was feeling its age.
As much as I hate EULAs and think they shouldn't exist, your reasoning is specious. Lets assume for a minute that a EULA is a valid contract. If so, they're offering you the software in exchange for agreeing to the contract. They have no legal obligation to allow you to negotiate on the contract. So you don't get to red line the contract and still use the software without their approval.
Imagine if you were at my store. I have a price tag on an item for $50. You don't get to yell $10, drop a 10 dollar bill, and run for the exit. Nor do I have to negotiate on price. I set out a deal, you can accept or try to get me to negotiate, but you can't take the goods on your terms and claim I implicitly agreed by not objecting.
And here's the problem- without someone teaching you, its pretty impossible to know that your level of skill is adequate or inadequate until looking at it in hindsight. Thus the biggest problem with the straight out of high school crowd- they think they're a lot better than they are.
You can train yourself on your own, but you will NEVER do so more efficiently than under a teacher and program. Its completely impossible, if for no other reason than the program knows what you need to teach yourself next and you don't. That alone eliminates a great deal of wasted time.
I know an awful lot of "self taught" programmers who are completely incapable of finding any solution that can't be googled for. They came up in the age of web based everything, self taught on php and javascript, and are used to everything being in a library or on stack overflow. Ask them to leave their narrow little box and they can't do it.
The best coders have formal training and the passion to code outside of their classes as well. Whether they're self taught or not doesn't matter, what matters is the additional practice and learning you get form doing more than just your assignments. That may be where the original myth of the self taught programmer comes from- there's a positive correlation between self taught and being passionate about programming. But the majority of the good ones still have formal schooling as well.
I'm self taught myself- I learned on TI calculator basic in high school then taught myself C++. And dear god was my code completely lacking in any real understanding of what I was doing. It was a combination of formal learning in college and practice done while in college that made me good, not being self taught.
It doesn't prohibit things like Swype. If they wanted to kill Swype, they could do it in one blow- delete the InputMethodService class in the next version. Without it, no more 3rd party keyboards (source: I worked at Swype). As much as Google seemed to love making me jump through hoops to work around their code, I don't see them doing that anytime soon.
I dislike how vaguely this is worded, but it doesn't block libraries either. What it blocks is people making phone specific SDKs, or taking the SDK and making it compile Android app to non-Android devices. Its meant as a counter to some Chinese OEMs doing just that. The only thing I really see that it blocks that was good are things like the original x86 sdk/ndk that people used before Google finally moved from ARM only.
Pretty much every place I've seen that elects judges requires them to be members of the local bar.
There's definitely ways we can improve taking people to court. But arbitration isn't one of them- it will always be biased towards companies, and there's no reason to create a parallel court system made out of people with no legal accountability and no appeals process. We have a court system. Hire more judges and make it take less red tape for short trials under a certain dollar limit. Maybe even as simple as any claim under $100 will be dealt with in writing rather than with a formal trial, unless one side requests it.
That's a great idea! Even better- we could have those trained arbitrators be paid for by taxes so that they aren't beholden to anyone but the law. We'll call them "judges".
Exactly. The idea behind a class action is that if a company is wronging a lot of people in a way that's too small to be worth going after by any one person, it can be punished by them as a group. The problem is two-fold. First, they're frequently allowed to pay in goods/services (especially discounts) that will make them money rather than cost them money. Second, they settle for a fraction of the harm they caused, leaving no reason not to do it again. Those two things need to be fixed- the penalty needs to be made cash only, and the minimum penalty applied needs to be the total harm done. Preferably total harm done plus a puntitive fine
I wouldn't expect it to get cheap enough. I also worry about negative side effects. Immunity comes to mind immediately- babies get some immunity from the mother's blood to common illnesses, what would the effect of missing that be long term?
Nope, still wrong. Plenty of parents are willing to adopt, as proof look at foreign adoptions. What almost nobody wants is to adopt a kid more than a few months old. Hence the giant foster care system. But for babies supply of parents far exceeds supply of children.
Not that there isn't some use for this device. I'm thinking for women who can't safely carry to term, they could have the baby moved to an artificial womb. Other than that it's a toy for very rich people who want to have a kid with their DNA but don't want to actually be pregnant- think trophy wives.
Unless they're selling to someone who lives in California. In which case the sale is governed by California law. Now if the developers said CA residents can't buy it (and are not themselves CA residents) then they can ignore this.
Slashdot Mirror
Do people really print? I haven't owned a printer in 10 years, and I used to write firmware for them.
The real problem will be typing. Whether its inputting in a form or sending an email, eventually you want a physical keyboard and not an onscreen one. My limit before I get annoyed with onscreens is about 200 characters- anything longer I wait until I'm at home.
Pretty much every place I worked. A well run HR department treats talent retention as a key job priority. Replacing and training a mediocre staff member takes months and thousands of dollars in cash and manpower, an above average one may take 10s of thousands and multiple people to do his old job. I've seen far more managers retrained or kicked out of the company than I've seen programmers, middle managers are easy to replace.
As for career opportunities- stop worrying about them. I don't want to be a manager. Except for a possible job as a tech lead/manager at a startup I'd be miserable doing it, I can read politics but I don't like to play games. You work at a job for a few years while it's fun. When it starts getting boring (long term boring, not just boring for a few days of documentation or the like) you look for somewhere else to work (which may be a transfer within the company, but most likely isn't).
I'm not looking to stay at one place for 5-10 years (my longest stay was 4, and I regret that but it was my first job. My lowest non-contract was 2). Besides, you get promotions and raises at a faster rate by moving on then playing the corporate games and trying to "climb the ladder". I've gotten raises of above 10% every time I switched jobs, doing that every 2 years or so is more money than you'd get staying at a place. I've gotten title raises with each, if those matter to you (although they shouldn't, titles are pointless and who does the work has nothing to do with who has the title). If you're looking for a more technical lead type role, that's also more easily obtained by moving- otherwise you're waiting for your lead or a closely related team's lead to leave or another team to be made and pick you. You're focusing totally wrong by thinking of a company career.
And its macho bullshitters like you who want to drag us down and become a hellhole. But I accept your thanks, while it has flaws this is a great country and people like me just make it better.
No, what I am is good, economically frugal (plenty of cash in the bank), and quite happy to go back on the job market to find something better if I need to. Life is to short to work somewhere you're treated like shit. They can spend the 6 months and thousands of dollars it would cost to replace me if they want, I'll have another job in 3 weeks if I'm not being picky, 2 months if I am.
No he's not. First off, in very few companies can the boss actually fire you at whim- they usually have procedures that need to be followed that take a great deal of time.
Secondly, if you're any good they probably can't afford to lose you, at least not quickly. If I was fired, milestones wouldn't be met for the next 6 months- not because I don't document my work for others (I do), but because training any replacement would take that long to know the codebase as well as I do. That's assuming they had someone of my skillset on tap- highly unlikely, finding a replacement would take another 6 months, or require multiple people. It would be easier to replace my manager than me.
Third, even if he does- you're better off not working for that asshole. Always keep at least 6 months reserve in the bank, and don't worry about it. Life's too short to work at a shitty place or for shitty people. I'd rather quit and take it easy for a week or two while I find a new job. And for programmers that's pretty easy these days, there's a lot more openings than good programmers. I get cold called by recruiters on a weekly bases.
Bullshit. If someone is fucking up (especially repeatedly), the boss should talk to him. Not scream at him- talk in a professional manner. Or let him go, if the mistakes are bad enough. You do not disrespect your employees by screaming them- it solves nothing, causes workplace friction, lowers morale of both the one being screamed at, the one screaming, and their coworkers. Its counterproductive.
If my boss came to my office and calmly told me I fucked up, I'd immediately jump on the problem and fix it. If my boss came in screaming at me, I'd tell him to get the fuck out, send an email to HR detailing his unacceptable behavior causing a hostile work environment and go home- telling him I'd return upon getting a sincere apology, and that I would expect full pay for every day in the interim. Oh, and my resumes would be on the net that evening. If he really pissed me off I'd go to his boss and tell him its me or him and I want a decision by the end of the day. There is no excuse for not behaving like an adult in the workplace.
Things like using solid variable/function names, providing sufficient (and quality) comments, and keeping similarity in architectural style matter. How many spaces you use (as long as you use some indentation) or what style of variable names you use makes no difference. And anyone who brings it up in a code review should be shouted down- the purpose of a code review is to find bugs, missed corner cases, unintended consequences of a change, and to find alternate ways to solve a problem. It is not there for cosmetic issues, and anyone who brings them up is wasting time for no gain and makes the code reviews of the entire organization less useful.
Because your examples are false equivalency. Just because each party produces some waste doesn't mean both are equally bad. There's only one party that put two wars on the credit card while cutting taxes. It wasn't the democrats. And there's only one party that continually tries to either lower tax rates or rebate taxes on every surplus. It isn't the Democrats. Just because both make mistakes doesn't mean they're equally bad, one can definitely be far worse.
You realize that you can't have a diagonal less than your larger dimension, right?
(70^2+5^2)^.5=70.1 inch diameter.
I can start making Schrodinger's Lolcats. Until you open the link, you don't know if its funny or not.
I had a Galaxy S until I recently lost it. It had the default app layout (which basically meant google apps only, non of the OEM crud). I noticed a significant slowdown in many apps (especially the browser) moving from 2.3 to 4.0. It wasn't horrible, but it was feeling its age.
As much as I hate EULAs and think they shouldn't exist, your reasoning is specious. Lets assume for a minute that a EULA is a valid contract. If so, they're offering you the software in exchange for agreeing to the contract. They have no legal obligation to allow you to negotiate on the contract. So you don't get to red line the contract and still use the software without their approval.
Imagine if you were at my store. I have a price tag on an item for $50. You don't get to yell $10, drop a 10 dollar bill, and run for the exit. Nor do I have to negotiate on price. I set out a deal, you can accept or try to get me to negotiate, but you can't take the goods on your terms and claim I implicitly agreed by not objecting.
And here's the problem- without someone teaching you, its pretty impossible to know that your level of skill is adequate or inadequate until looking at it in hindsight. Thus the biggest problem with the straight out of high school crowd- they think they're a lot better than they are.
You can train yourself on your own, but you will NEVER do so more efficiently than under a teacher and program. Its completely impossible, if for no other reason than the program knows what you need to teach yourself next and you don't. That alone eliminates a great deal of wasted time.
I know an awful lot of "self taught" programmers who are completely incapable of finding any solution that can't be googled for. They came up in the age of web based everything, self taught on php and javascript, and are used to everything being in a library or on stack overflow. Ask them to leave their narrow little box and they can't do it.
The best coders have formal training and the passion to code outside of their classes as well. Whether they're self taught or not doesn't matter, what matters is the additional practice and learning you get form doing more than just your assignments. That may be where the original myth of the self taught programmer comes from- there's a positive correlation between self taught and being passionate about programming. But the majority of the good ones still have formal schooling as well.
I'm self taught myself- I learned on TI calculator basic in high school then taught myself C++. And dear god was my code completely lacking in any real understanding of what I was doing. It was a combination of formal learning in college and practice done while in college that made me good, not being self taught.
The guy working for $1 owns a large chunk of the company. He's paid in either new or pre-existing stock options.
Actually it does. Google (irony there) "vertical monopoly". However being a monopoly is not illegal, only abusing your monopoly is.
It doesn't prohibit things like Swype. If they wanted to kill Swype, they could do it in one blow- delete the InputMethodService class in the next version. Without it, no more 3rd party keyboards (source: I worked at Swype). As much as Google seemed to love making me jump through hoops to work around their code, I don't see them doing that anytime soon.
I dislike how vaguely this is worded, but it doesn't block libraries either. What it blocks is people making phone specific SDKs, or taking the SDK and making it compile Android app to non-Android devices. Its meant as a counter to some Chinese OEMs doing just that. The only thing I really see that it blocks that was good are things like the original x86 sdk/ndk that people used before Google finally moved from ARM only.
Pretty much every place I've seen that elects judges requires them to be members of the local bar.
There's definitely ways we can improve taking people to court. But arbitration isn't one of them- it will always be biased towards companies, and there's no reason to create a parallel court system made out of people with no legal accountability and no appeals process. We have a court system. Hire more judges and make it take less red tape for short trials under a certain dollar limit. Maybe even as simple as any claim under $100 will be dealt with in writing rather than with a formal trial, unless one side requests it.
That's a great idea! Even better- we could have those trained arbitrators be paid for by taxes so that they aren't beholden to anyone but the law. We'll call them "judges".
Exactly. The idea behind a class action is that if a company is wronging a lot of people in a way that's too small to be worth going after by any one person, it can be punished by them as a group. The problem is two-fold. First, they're frequently allowed to pay in goods/services (especially discounts) that will make them money rather than cost them money. Second, they settle for a fraction of the harm they caused, leaving no reason not to do it again. Those two things need to be fixed- the penalty needs to be made cash only, and the minimum penalty applied needs to be the total harm done. Preferably total harm done plus a puntitive fine
I wouldn't expect it to get cheap enough. I also worry about negative side effects. Immunity comes to mind immediately- babies get some immunity from the mother's blood to common illnesses, what would the effect of missing that be long term?
Nope, still wrong. Plenty of parents are willing to adopt, as proof look at foreign adoptions. What almost nobody wants is to adopt a kid more than a few months old. Hence the giant foster care system. But for babies supply of parents far exceeds supply of children.
Not that there isn't some use for this device. I'm thinking for women who can't safely carry to term, they could have the baby moved to an artificial womb. Other than that it's a toy for very rich people who want to have a kid with their DNA but don't want to actually be pregnant- think trophy wives.
No, they could. But Apple had all the design patents on them
It didn't seem like we were having any real problems due to inexperienced pilots before. If this is really a problem, let's just roll this back.
Unless they're selling to someone who lives in California. In which case the sale is governed by California law. Now if the developers said CA residents can't buy it (and are not themselves CA residents) then they can ignore this.