PhoneGap sucked badly on anything except the most basic applications. Little marketing apps were ok (or almost) on it. Everything else endup on a terrible user experience.
I don't agree with you. My personal experience screams loud and clear you are simply wrong. Your "work experience" doing little hacks for your uncle's groceries shop simply doesn't counts.
No one has the needed "seniority experience" at the age os 26. Unless you have a very twisted concept about "seniority". Obviously, it appears it's your case (no offense intended, I'm criticizing your definition of "seniority", not your competence or personal experiences).
"Experience" is more than just "do something years repeatedly". It's about living acknowledge, about the consequences of "doing something" over the dude's life.
In order to correctly lead a team, you must understand them. You must know and understand what can happen to them. You must understand what happens when their child is hospitalized, when a brother dies, when the wife is getting problems on the pregnancy.
Simple things like a root channel treatment on two teeth can render your guy useless half of the day. (been there, done that)
Every, every, every "senior" team leader under his 30's that lead me just fucked up horribly. Almost all of them were excellent technicals, but all of them managed to simply destroy the team with foolishness.
As a rule of thumb, it appears that it's highly improbable that someone can lead, successfully, a team with older mates.
(And again, there're exceptions - there're some geniuses around us, they're scarse however. A LOT scarse. Obviously, you are not between them - neither do I, by the way).
You see, your former employer it's not allowed (by law) to talk badly from you if someone calls him for references, but this doesn't apply on the table of a bar neither prevents him to refuse to answer the right question.
"Your former employee is trustworthy?"
"I won't answer this question..."
Don't think managers and H/R people don't have social life nor circles of friendship on different companies.
This is exactly the problem I'm addressing: as you said, "titles may vary from company to company", and in most of the serious companies I worked for, seniority is about *experience*, not *competence*.
Competence it's just the sine qua non condition *to stay employed*, not to get promotions.
Do your best to get a graduation as fast as you can do it, and you'll be more than fine: you already overcome one of the hardest milestones on a career. You must (and it's obvious you already know it) work on how to keep it, in the event you need to exchange jobs.
I am a 26 year old Senior Software Engineer at IBM. If you have the right skills, experience, and mind, age doesnt matter so much as results. Ageism happens on both ends of the spectrum:)
*NO ONE* has the right experience at the age os 26. Unless you have a very, very twisted concept about "seniority".
But since you're at IBM, this doesn't surprises me. IBM is adept of the "head counting" concept, where some management deity defines how much "seniors", how much "juniores", etc, a project needs after (and just *after*) it was sold to the client, and then goes to the head hunt.
Obviously, there're no enough Seniores available (as the real ones, commonly, just quits - when they're not laid off, being exchanged for cheaper workforce overseas) so the management just promotes younger ones to the hole - as they're cheaper to replace if they got burned by the job.
(and believe, the ones that doesn't grasp the thing, *are* replaced without a second thought).
This can work fine on very, very large organizations where the management can fix the mess carefully disguising the resources needed to fix the shit as "development costs". The money flows easily - the client is paying anyway, and IBM's customers have deep pockets and are, commonly, locked up on IBM products.
So I strongly suggest you *never* leave IBM. Your title will make your future employer expect more than you (statistically - *there are* genius between us, it's not impossible you are one of them) are capable of.
Mainly because, here at the Real World, a Senior Software Developer is heavily demanded as 99% of the employers don't have deep pockets customers and, so, *don't have* the needed resources to sustain this kind of "management". Your (future) boss must deliver the task, or he is not paid - simply like that.
And if he is not paid, you are laid off. Simply like that.
You got a "Senior Software Engineer" title at age of 26? O.o
Sorry, pal, but I think your company had spoiled you badly.
On the other hand, KUDOS for your approach to the problem (it is instinctive? How did you realize it?)
Formal education is a need (I know, I did'nt complete my own - besides having a excellent technical formation and experience : I'm entitled to get a PMP title if I apply for it), and you're 150% correct on concerning your future. Don't let the size of your company eludes you, it appears to be not on his best shape.
(off course this is a superficial analysis based on my own experience - as always, your mileage my vary)
You can't fix unprofessionalism by being unprofessional.
Unfortunately, yes, you can. And, more unfortunately yet, this uses to work with some kind of people.
You see, I have a bad experience myself with such a bastard.
He made a mistake, I talked to him nicely explaining what and why that was unacceptable.
He did the mistake again, and I talked to him politely (but not nicely) again, explaining again what and why that was unacceptable.
The third time he did it again, I gone berserk and trashed him out. Good thing he thinks like you and gone away (as I didn't had the power to fire him).
Linus could be a bit (well, a lot!) less harsh, but he could not do it in private.
You *must* be held accountable for what you commit. In a tremendously large project as the Kernel, not doing that *will* render the code useless faster than you can spell W I N D O W S .
What I think it's happened is that Linus burned up with the maintainer's pale excuse for the problem.
If you care reading all the thread, you will see that thing started when Mauro said:
Are you saying that pulseaudio is entering on some weird loop if the returned value is not -EINVAL? That seems a bug at pulseaudio.
...
In other words, only an application that handles video should be using those controls, and as far as I know, pulseaudio is not a such application. Or are it trying to do world domination?
Problem is: the public interface for the ioctl in question stated that -EINVAL should be returned in the situation. It appears to me that the maintainer tried to diverge the discussion, blaming the application.
If it was really what the maintainer had in mind, I don't know. But this is what hit Linus in the balls.
Ok. What if there was just one foundation, and then a second, secretive, foundation foundation whose purpose is to monitor the foundation's activities in Open Source?
A FOSS oriented Church? =P
Come to Brazil, Churches don't pay taxes around here. This can be a highly lucrative enterprise! =D
(Ahh, the blips of the bitcoins being donated by mobile phones on the mass....)
Industrial organizations do seem to work in general, so the supporting role, or meta-role of the OSFF suggested in the summary should not lessen the resiliency of the FOSS. Pooling resources does not always equal pooling power.
I don't agree with you.
I had worked for Siemens Mobile (acquired by BenQ at the time of my leave), Siemens VDO (acquired by Continental, then acquired by Schaefler Group, and then I leave). The recent Sun acquisition by Oracle came to my mind.
The industrial organizations mindset is all about power concentration and promoting scarceness in order to promote revenue. It's about acquisition and/or annihilation of the competition.
I'm serious. We can't afford this mindset on FOSS.
Here at Brazil the tickets always go to the vehicle's owner.
If the owner had lent the car to someone, it's up to him/her to go to the authorities with a declaration, signed by the culprit, asking to transfer the ticket ownership.
It sounds to me like we just need to steer these shootings to the schools where the Free Shit Army send their children. In some places in the US, wiping out a classroom of kids would save society and the government tens of millions of dollars in hand outs, prison expenses, addiction recovery services and damage inflicted on the rest of society.
Also, by your logic, it's better to kill them while they are young as the sunk cost is less.
Strawman. I didn't imply anything of this.
What I said is that is a lot of cheaper to correctly deal with the problem (and I don't even touch on the definition about what would be the correct thing to do) than to let it goes as it is now.
You are the one stating that killing people is a acceptable way of doing things. Not me.
We live in a society that fails to prevent the most basic "accidents" (it's God Damned easy to avoid drinking and driving!).
However, I think the same logic applies. We can't restore a life, but we can issue the people responsable for it a hell of regret for doing that. Not only the perp, but everybody else that enabled him/her.
Slashdot Mirror
PhoneGap sucked badly on anything except the most basic applications. Little marketing apps were ok (or almost) on it. Everything else endup on a terrible user experience.
I don't see how Cordova could overcome this.
I don't agree with you. My personal experience screams loud and clear you are simply wrong. Your "work experience" doing little hacks for your uncle's groceries shop simply doesn't counts.
No one has the needed "seniority experience" at the age os 26. Unless you have a very twisted concept about "seniority". Obviously, it appears it's your case (no offense intended, I'm criticizing your definition of "seniority", not your competence or personal experiences).
"Experience" is more than just "do something years repeatedly". It's about living acknowledge, about the consequences of "doing something" over the dude's life.
In order to correctly lead a team, you must understand them. You must know and understand what can happen to them. You must understand what happens when their child is hospitalized, when a brother dies, when the wife is getting problems on the pregnancy.
Simple things like a root channel treatment on two teeth can render your guy useless half of the day. (been there, done that)
Every, every, every "senior" team leader under his 30's that lead me just fucked up horribly. Almost all of them were excellent technicals, but all of them managed to simply destroy the team with foolishness.
As a rule of thumb, it appears that it's highly improbable that someone can lead, successfully, a team with older mates.
(And again, there're exceptions - there're some geniuses around us, they're scarse however. A LOT scarse. Obviously, you are not between them - neither do I, by the way).
By being fired for lying in the CV. of course!
You see, your former employer it's not allowed (by law) to talk badly from you if someone calls him for references, but this doesn't apply on the table of a bar neither prevents him to refuse to answer the right question.
"Your former employee is trustworthy?"
"I won't answer this question..."
Don't think managers and H/R people don't have social life nor circles of friendship on different companies.
This is exactly the problem I'm addressing: as you said, "titles may vary from company to company", and in most of the serious companies I worked for, seniority is about *experience*, not *competence*.
Competence it's just the sine qua non condition *to stay employed*, not to get promotions.
You appear to have the brains in the right place.
Do your best to get a graduation as fast as you can do it, and you'll be more than fine: you already overcome one of the hardest milestones on a career. You must (and it's obvious you already know it) work on how to keep it, in the event you need to exchange jobs.
"Live longer and prosper". :-)
I am a 26 year old Senior Software Engineer at IBM. If you have the right skills, experience, and mind, age doesnt matter so much as results. Ageism happens on both ends of the spectrum :)
*NO ONE* has the right experience at the age os 26. Unless you have a very, very twisted concept about "seniority".
But since you're at IBM, this doesn't surprises me. IBM is adept of the "head counting" concept, where some management deity defines how much "seniors", how much "juniores", etc, a project needs after (and just *after*) it was sold to the client, and then goes to the head hunt.
Obviously, there're no enough Seniores available (as the real ones, commonly, just quits - when they're not laid off, being exchanged for cheaper workforce overseas) so the management just promotes younger ones to the hole - as they're cheaper to replace if they got burned by the job.
(and believe, the ones that doesn't grasp the thing, *are* replaced without a second thought).
This can work fine on very, very large organizations where the management can fix the mess carefully disguising the resources needed to fix the shit as "development costs". The money flows easily - the client is paying anyway, and IBM's customers have deep pockets and are, commonly, locked up on IBM products.
So I strongly suggest you *never* leave IBM. Your title will make your future employer expect more than you (statistically - *there are* genius between us, it's not impossible you are one of them) are capable of.
Mainly because, here at the Real World, a Senior Software Developer is heavily demanded as 99% of the employers don't have deep pockets customers and, so, *don't have* the needed resources to sustain this kind of "management". Your (future) boss must deliver the task, or he is not paid - simply like that.
And if he is not paid, you are laid off. Simply like that.
Believe me, no one checks up on this stuff. Say you got a 4 year degree from some small university that no one knows too well.
Because if you have the bad luck of hitting one bastard that actually does the check, you're screwed up for the rest of your life.
You got a "Senior Software Engineer" title at age of 26? O.o
Sorry, pal, but I think your company had spoiled you badly.
On the other hand, KUDOS for your approach to the problem (it is instinctive? How did you realize it?)
Formal education is a need (I know, I did'nt complete my own - besides having a excellent technical formation and experience : I'm entitled to get a PMP title if I apply for it), and you're 150% correct on concerning your future. Don't let the size of your company eludes you, it appears to be not on his best shape.
(off course this is a superficial analysis based on my own experience - as always, your mileage my vary)
And, as anyone that lives in Oregon will tell you, if you go in the Oregon section of the Pacific Ocean, you are a fucking moron.
Thanks for the info.
Can you explain why? It's a dangerous place somehow?
Focusing on the tone of Linus' argument is missing the point. Linus is right here.
Unfortunately, focusing on the tone instead of the message is the norm around Brazil.
People here has a huge ego, they insist to be handled with 'caring' - even at their own prejudice (they prefer to go under).
Look, I'm not talking about people that do not take injustice - the weird thing is that THEY TAKE ANY INJUSTICE as long as it is inflicted politely.
It's juts insane...
IMHO, this is the exact attitude that got Linus pissed off.
Of course a mere apology will not do. Only the classical seppuku, flawlessly executed with a tanto, will be somewhat sufficient.
A Yubitsume would be enough! :-)
You can't fix unprofessionalism by being unprofessional.
Unfortunately, yes, you can. And, more unfortunately yet, this uses to work with some kind of people.
You see, I have a bad experience myself with such a bastard.
He made a mistake, I talked to him nicely explaining what and why that was unacceptable.
He did the mistake again, and I talked to him politely (but not nicely) again, explaining again what and why that was unacceptable.
The third time he did it again, I gone berserk and trashed him out. Good thing he thinks like you and gone away (as I didn't had the power to fire him).
Linus could be a bit (well, a lot!) less harsh, but he could not do it in private.
You *must* be held accountable for what you commit. In a tremendously large project as the Kernel, not doing that *will* render the code useless faster than you can spell W I N D O W S .
IMHO, this is the exact attitude that got Linus pissed off.
What I think it's happened is that Linus burned up with the maintainer's pale excuse for the problem.
If you care reading all the thread, you will see that thing started when Mauro said:
Are you saying that pulseaudio is entering on some weird loop if the returned value is not -EINVAL? That seems a bug at pulseaudio.
...
In other words, only an application that handles video should be using those controls, and as far as I know, pulseaudio is not a such application. Or are it trying to do world domination?
Problem is: the public interface for the ioctl in question stated that -EINVAL should be returned in the situation. It appears to me that the maintainer tried to diverge the discussion, blaming the application.
If it was really what the maintainer had in mind, I don't know. But this is what hit Linus in the balls.
This is somewhat related with this Linus' post on G+?
Ok. What if there was just one foundation, and then a second, secretive, foundation foundation whose purpose is to monitor the foundation's activities in Open Source?
A FOSS oriented Church? =P
Come to Brazil, Churches don't pay taxes around here. This can be a highly lucrative enterprise! =D
(Ahh, the blips of the bitcoins being donated by mobile phones on the mass....)
Industrial organizations do seem to work in general, so the supporting role, or meta-role of the OSFF suggested in the summary should not lessen the resiliency of the FOSS. Pooling resources does not always equal pooling power.
I don't agree with you.
I had worked for Siemens Mobile (acquired by BenQ at the time of my leave), Siemens VDO (acquired by Continental, then acquired by Schaefler Group, and then I leave). The recent Sun acquisition by Oracle came to my mind.
The industrial organizations mindset is all about power concentration and promoting scarceness in order to promote revenue. It's about acquisition and/or annihilation of the competition.
I'm serious. We can't afford this mindset on FOSS.
Someone remotely hijacks your driverless automobile. They drive it into a coffeeshop. Are you to blame?
YES.
You are responsible for keeping your car under legal and technical correct operation.
Oh, you car has a manufacturing defect? Sue the manufacturer for damages in order do compensate you for the money you lost due this defect.
*NO*.
Open source can be a "mess". But it's exactly this "mess" that makes the FOSS resilient.
Here at Brazil the tickets always go to the vehicle's owner.
If the owner had lent the car to someone, it's up to him/her to go to the authorities with a declaration, signed by the culprit, asking to transfer the ticket ownership.
It sounds to me like we just need to steer these shootings to the schools where the Free Shit Army send their children. In some places in the US, wiping out a classroom of kids would save society and the government tens of millions of dollars in hand outs, prison expenses, addiction recovery services and damage inflicted on the rest of society.
Also, by your logic, it's better to kill them while they are young as the sunk cost is less.
Strawman. I didn't imply anything of this.
What I said is that is a lot of cheaper to correctly deal with the problem (and I don't even touch on the definition about what would be the correct thing to do) than to let it goes as it is now.
You are the one stating that killing people is a acceptable way of doing things. Not me.
If my poor grammar if the worst thing you can pinpoint in my post, then thank you for implying I'm right. :-)
Yes mass shootings happen,
No. Mass shootings does not simply "happens". They are done. By someone.
Other than this, I agree with you.
Yep. You are right too.
We live in a society that fails to prevent the most basic "accidents" (it's God Damned easy to avoid drinking and driving!).
However, I think the same logic applies. We can't restore a life, but we can issue the people responsable for it a hell of regret for doing that. Not only the perp, but everybody else that enabled him/her.