Early experience in a couple of start-ups that, alas, did not survive. More experience in mid-sized to large companies. . .non-profit, government, for-profit. . . weapons, communications, HR, healthcare. . .coder, tester, project manager. . .
When Fiorina was the CEO of a significant corporation, HP, she got a lot of ink, too. Of course, HP itself, got a lot of ink before, during and immediately after her tenure there.
And, a good PM also says "no" or "can it wait" or "ok, if you insist, but here's the downside" to folks on the other side of the line - customers, senior management.
Well, note who is explicitly excluded from the buyout:
"People working in the Software Group will not be allowed to join VSP, neither will folk with vice president in their title, nor exec/ distinguished directors in engineering or employees in India or Singapore."
I don't know who's included in the Software Group, but it probably includes a lot of people like those who read HN.
I once worked for a company where buyouts were offered - we had seen the handwriting on the wall for quite a while. Engineers were excluded and I was an engineer. They came nowhere near their target buyout numbers and finally, grudgingly, offered buyouts to engineers. I took the buyout.
In all but small companies, I think devs have little to no contact with the other product/project stakeholders. For those devs who would like to be in a position to influence/interact with the stakeholders, being a PM would eliminate some of the constraints/WTFs devs often feel. Well, not always eliminate necessarily, but minimize them, or at least provide some transparency into the part(s) of decision-making process(es) outside the devs' sphere of influence.
“It’s not as if we are suddenly going to start lending to [small and medium-sized enterprises],” said one. “There really isn’t the level of demand, so the danger is that banks are pushed into riskier assets to find yield.”
I wonder how many small and medium-sized enterprises would agree that there isn't demand for bank loans. There is anecdotal evidence that small and medium-sized companies are looking for bank loans but can't get them. Is it that they truly can't get them at any rate or can't get them at the rates they want. . . Conversely, will banks be "pushed" into riskier assets because they truly have nowhere else to invest/loan their money or because lending to small/medium companies will not pay the yields required to satisfy Wall Street, their stockholders and their senior execs?
In the original article, the owner explains what he originally thought he was agreeing to - and why:
"About three years ago, Saleh said police asked him to participate in what they called a “zero-tolerance” program to reduce crime. He gladly signed up, not realizing at the time how much it would impact his business and customers. Under the program, Miami Gardens police are given broad powers to stop and arrest people who appear to be loitering or trespassing at the participating business.
The idea behind the program is based on the “broken window theory,’’ a concept that has been employed by police around the country. The theory holds that a community that rids itself of petty crime, such as shoplifting, vandalism and trespassing, can eradicate more serious crime because criminals won’t have anywhere to hide."
This is also the justification for NYC's "stop and frisk" program which has been in the news so much lately. For the record, I'm not a fan.
They are also incredibly risk-averse. Even though they they have a no-risk, probationary period during which they can release an employee who's not working out, they are deathly afraid of hiring someone who's not perfect. And a 90% fit simply won't do; they must be guaranteed of a 100% fit. In the meantime, their current employees are stretched beyond their limits, deadlines are missed OR made with a very high price (team morale, long-term productivity, other missed deadlines), the business becomes more tactical than strategic, etc. And if things eventually go to hell in a handbasket, it's blamed on the "lack of qualified applicants".
Holding. With its recent growth, I view Bitcoin as much more of a (highly) speculative investment than a form of currency. Curious to see how Bitcoin's rivals fare and how they impact Bitcoin.
If you live in isolation or aren't a member of a group that is perceived negatively by a significant number of people, it's very easy to NOT care. It's a lot harder when how people feel about you affects you - every day - in your ability to get/maintain a job, get promoted at that job, buy/rent a dwelling, finance a business, enter a restaurant/elevator/bus without causing a ripple. . .
For a start-up or small company, I agree with the previous comment - shorter resume with links is the way to go. But for larger companies, especially those that use scanners for initial screening, it may be better - or at least okay - to go longer. The scanners will probably ignore the links. Or. . .I'm aware of a couple of companies that include certain links in their keyword counting/weighting algorithm, but I'm not aware of the extent.
http://unos.org/ - primary mission is to maintain organ transplant lists.
You won't get rich, but you'll have money left over after paying your bills.
Vision statement
To promote long, healthy and productive lives for persons with organ failure by promoting maximized organ supply, effective and safe care, and equitable organ allocation and access to transplantation.
Mission statement
To advance organ availability and transplantation by uniting and supporting its communities for the benefit of patients through education, technology and policy development.
I used to work in a world with lots of embedded software. My experience was that - regardless of domain or company -the "hardware" was regarded as just that - simply hardware. And it was tested as that - simply hardware - not as hardware that, oh by the way, had a helluva lot of critical embedded software. So issues that could have been caught at some level of testing weren't.
I think it depends on how you define code quality. If you mean it's been re-factored (for example) as much as possible, then I agree. . .you are just polishing the apple. But if you mean acceptably (to the customer) bug-free, then I think your work was worth it.
As the manager/co-founder, helping with tools, coping mechanisms, etc. is often not enough. When an employee has shit falling off of his/her plate, he often needs help prioritization. Managers/co-founders often assume everyone knows the priorities of projects and that's often not the case. If the manager's or company's priorities have shifted, that needs to be communicated to everyone. If you have a meeting scheduled with some big-wig tomorrowand I'm providing data for that meeting, I need to know; otherwise you may not get your S until it's too late. But, by God, I'm GSD!!
There are those who believe that projects don't need any management, just "doing/executing". . .and that when projects fail, it's because project management got in the way. . .which is true sometimes, but not usually.
One of my favorite stories regarding an elementary level Standards of Learning (SOL) test in Virginia. . .Students are taught how to estimate relatively simple sums, difference, products and quotients in their heads. Students are required to select the "correct" estimate. One of the questions accidentally (I guess) included the actual answer among the choices. My son selected the actual answer rather than the "correct" estimate and it was marked wrong.
OK, technically he didn't follow directions. . .the question asked for the estimate. But. . .really. . .you penalize a kid for calculating the correct answer and selecting that over the correct estimate??
Try a medium-sized company; it might be more flexible with hiring "requirements" and be willing to look at the time you spent leading other engineers. Be prepared to talk about how you mentored them, resolving intra-team differences, etc.
Sometimes you have to move away in order to move up, especially if you've been pigeon-holed as just a senior developer. Another company will view you through fresh eyes, with an unbiased perspective.
Try "employee health privacy". Regardless of legality, I don't know why an employer would even want to have a common/shared calendar that includes a history of sick days off. Of course, a manager would maintain that or have access to a system that maintains that, but I don't know why everyone else in the workgroup needs access to a history - even an unofficial one - of someone else's sick days off. I'm sure some will keep unofficial track, especially if the co-worker's absence impacts them - or they perceive that it does - but for the manager to purposely do that. . .I don't see the point.
Some people are fairly content in their jobs, but would like to just test the waters - they may contact a recruiter do their legwork.
And some companies like to go the contract-to-perm route, rather than do a direct hire; they can't/don't want to do the screening themselves or the hiring company is willing to pay a premium to let the recruiter assume the risk during the "probationary period" or. . .
I totally agree with having lively discussion within a framework defined by the leadership. But it seems that the mission and values are usually at a pretty high level - so high that they don't necessarily help in coming up with a single solution. It still seems that someone ??in a non-leadership role?? needs to be empowered to make the final decision - and to know when to make it. Maybe the framework you're thinking of, while influenced by the higher-level mission and values, has the "who" and "when" built in. And it certainly wouldn't have to be the same "who" all the time.
Code review, done properly, should provide more than just a critique of coding style. It should should also catch certain types of bugs before they get to functional testing. Yes, you can catch those same bugs in functional tests, but in the environments where I've worked, there's a lot more overhead (read: time, money) involved with bugs found in functional test than in code review. Ita can be pretty frustrating to be that far along (functional test) and find a bug that could've easily been found in code review.
Not just start-ups; larger companies, too. The process may dictate testing, but if, for example, there's an urgent production bug or some enhancement that "needs" to be pushed quickly, testing often falls by the wayside.
This has impact beyond Texas. Since Texas is such a populous state, its approved books end up in a lot of other states, who, understandably, want to take advantage of the economies of scale. . but end up with books with questionable content by their own state standards.
* It's possible that something happened between Jill and the managers/co-founders that the rest of the group is unaware of, and she felt that it was best that she leave.
* It's possible that her health issue flared up again and she decided to leave. She may have been quite appreciative of what the group in her previous absence but didn't want to/couldn't go through having you all pick the slack - either her choice or management's. And she didn't know how to gracefully exit, so she abruptly left.
* Maybe she got ill again and the goodwill "debt" she incurred had nothing to with it - she just needed to leave again to tend to her health - and was unfortunately, not gracious in her departure.
* Maybe she was forced out and has been prohibited from saying anything - or simply chose not to.