When there are a lot of stakeholders or process to be moved through, a project manager to keep track of all of that is really key. This is a skillset most people don't really have and a good project manager is a life saver.
At the same time, lots of development shouldn't be treated as "project" work. Tight collaboration between design, development and product leaders are the core. You want project managers to get out of the way there. That's more creative work and no gannt chart is going to help.
Failure to recognize whether what you are working on needs PM is a pretty common failure pattern. A PM doing a lot of work where they shouldn't results in negative contribution, and missing them where they are needed tends to result in failure to deliver.
In the enterprise software business all sales people are commissioned. Except for the ones we had at my last employer. We recognized that sales is hard, competitive and requires special work. At the same time, the key element that wins a deal might be a developer working all night to sneak a feature into a demo or build a new demo environment.
So why do you pay the sales guy a huge commission check for doing his part and the developer her normal salary if the developer was the one with the heroic effort?
You're best off paying everyone a fair salary and chipping in some bonuses and team celebrations to capture heroics.
The rote IT jobs that are best suited for labor arbitrage outsourcing are also the ones that should just be automated out of existence anyway or handled auto-magically by your cloud provider. The remaining jobs are the ones where close collaboration with the business makes them far more effective and those are going to be ones that you're going to regret offshoring.
The number of jobs that don't fall into either of those buckets is getting smaller by the day. It's hard to see how this kind of outsourcing has a long term future.
They point out that anyone bwi wants an image they find in the Getty catalog will find it via image search and steal it. The goal is to offer the embed as a slightly easier way to get the image for free and so have some home of monetizing use from people who will not pay.
People telling me about cool shit I might want to buy? That's a service. And if they've figured out enough about my behavior to advertise things I'd actually be interested in rather than random shit, that's even better. Please, please, please profile me. It was creepy the first time (ok first hundred times), but I'm over that.
If you lie in an advertisement, that's evil. If you horrendously and needlessly distract from content, that's pretty lame. But if you have a cool pitch to make in the corner of a website I frequent, that's a win-win-win. I get free content. I'm not too distracted. You get my business if you've profiled me well enough and I'm in a buying mood. The website gets paid. Who loses here?
Adblock sites that allow annoying BS that gets in your way. Or better yet, stop visiting them. Let ads in where they behave civilly.
I believe Cord stem cells are rather "pure" stem cells that are very undifferentiated. Making them ideal for a handful of medical procedures and unspecified future medical procedures that may be created. Generally, this nifty resource is lost right after birth (it's thrown away). So some companies have been created to store them, and provide them to you (or others if donated) in the case one of those rare procedures is required.
If I recall correctly, you're looking at $500-$1000 to get things going, and a 50-100 annual fee to maintain. This falls under the broader cateogory of stuff sold under the banner of, "You love your baby right? You'd do anything to protect it? Right? You're not a callous evil person."
They're never pretty and are frequently ugly, but really don't have to be all that bad.
I'm divorced (and now happily re-married!) and while painful, the divorce wasn't ugly. We hired a lawyer together to help us through the paperwork. If you're cheap, there are also forms at Staples. The lawyer was well worth it. I kept most of the furniture and cut my ex a check in return. I had stuff, she had some cash, we were both ok and clear of any alimony claims. I probably could have fought and paid a little less to my ex and a whole lot more to lawyers.
Remember that at the very least you once loved that other person. Treat eachother with some respect, and part civilly. It's strange when you're called, "a model divorcing couple" but a million times better than going to war.
Downstream is a key component. We get rain / melt-off that is used by farmers and cities in other states as well. Water in the west is a precious thing and "ownership" of it is order dependent. Someone owns the first drop of water flowing in the river, and someone else own X gallons / time period only if there's enough left over them after the senior stakeholders are accounted for. Those rights don't care if you are upstream or downstream, but on seniority.
With the possibility of water intensive shale oil extraction, oil companies have been buying senior water rights in Colorado for some time and then leasing them back to farmers / etc. If shale oil happens seriously, and needs the water that's predicted, things could get ugly in a hurry.
I think the "distributed across the map" part is key. In beginner / intermediate play, a really key ability is to actually remember to keep building stuff while scouting or fighting. Can you throw down that building on time while also looking at your opponent's base and gleaning useful information there in an early scout? In an early skirmish, can you micro well enough to gain a minor advantage while also still building workers for the long term economy that actually matters? In the midgame, it's worse, you have building workers, troops, scouting, managing supply, map positioning, upgrades, watching the mini-map for counters/drops, etc, etc, etc all going on at the same time in different places of the map and screen.
90% of the players in the world can't really do these things consistently well because the require you to take care of a lot of background work while actively focused on the exciting stuff. That's genuinely hard and you get better at it incrementally at best.
The line really is starting to crumble with DevOps entering the field. While it's still usually two different people with different skill sets. They're increasingly being put on the same delivery team.
As a software company that makes products for IT departments, someone who can write code and "gets" IT is an extremely interesting candidate in a range of positions (from development to solutions engineer).
Your risk is that we (or anyone else) stops believing that you can actually write code. So you'll want to stay sharp there with a pet project, contributions to open source or something along those lines.
At most airports you have the option of mailing that little credit card tool with a knife in it back to yourself. But you probably got it for free at a trade show and would rather bitch about government abuses than pay 6 bucks to mail it to yourself.
Well, at least that's how I felt when the bastards took mine away.
More specifically, they'd be insane to ever have the file. It would mean sending it to them. Much smarter and more efficient to hash the file on your computer (ignore meta-tags) and match against the tag on their server. Done. They never have the file and never look at the incriminating bits.
This is why Apple thinks they can have all your music to you quickly instead of the weeks of upload time to get it to google. Because you don't upload it. They might still be uploading meta information that would be incriminating, but they would have to go out of their way to do so.
Correct, this is not a theory, like the theory of gravity.
It is an attempt to understand the steady increase in global temperatures over the years. There's plenty of refutable science at work. Researches uncover trending data of global temperatures. Other researchers could show problems in approach, or show data that disagrees.
Modelers make predictions of change over the course of years. The accuracy of their predictions speaks to the quality of the models.
Fundamentally, though we have a problem. It would be great if we had two planets. One where we toss as many greenhouse gases into the atmosphere, and another where we do everything the super enviro-crazy vegan wants us to do. Then a hundred years later, we compare temperatures. The problem is that we don't have spare planets to play with. So we have a relatively high stakes game where we work with models, and do a lot of falsify-able detailed science to help inform those models. Only in the models can we run the data for 100 or 1000 years quickly and without much consequence.
Oh, and anyone who would blame Bush for climate change is a nut job. Most of the damage done so far was done before his birth, while he was a child, or while he was a drunk and playboy. It's hard to blame him for any of that. But to argue only against the nut jobs is strawman bullshit. You're right though, czars aren't going to help. A carbon tax might (and might help balance budget or free money for other tax cuts). Helping China build cleaner coal plants might (and would be cheaper than retrofitting ours). But yeah, czars won't help much.
Just because it's been cooler at your house for the last two years, does not mean the earth, as a whole, is not getting warmer in general.
It's perfectly plausible that the average temperature on the planet could rise significantly while a region, like Europe, gets colder. For instance, general warming could result in polar warming diminishing the northern ice caps (as we're seeing). Should those ice caps melt enough, the iceberg melting in the north atlantic would dramatically lesson since no glaciers would spawn them. The atlantic currents would be disrupted, lessening the gulf stream. Winds flowing over those warm waters would no longer carry that extra heat to Europe and slowly the weather in Paris starts to resemble Winnepeg (about the same latitude). The good news for Winnepeg is that it's likely to warm up a little.
That's climate change in a nutshell. General warming. Local cooling. Some areas get dryer. Others wetter. Very, very complicated interplay between systems makes predicting winners and losers extremely difficult.
And I swear, the next time there's a snowstorm and people use that as evidence that there isn't global warming, I'm going to punch someone in the face.
Or... our jobs are such that we visit our clients across the country. So I could spend every weekend driving and only be able to cover 20% of the country, or I can take a 10 minute pass through a security line twice a week. I'll take a ten minute inconveinance and let someone fly me somewhere in 4 hours rather than do a four day drive across the country - which would cost more money anyway.
Now, if you live on the East Coast, you might be able to travel to lots of people in a few hours. You might also be enough of a pretentious ass to think the whole country is on the east coast. For the rest of us, flying can be needed. For some of us, it's a regular thing that lets pay for things like food.
At the same time, the states compete with eachother by lowering their tax rates - so they're (almost all) broke. IF moving towards more renewable energy is a national goal, then this is perfectly appropriate. Energy can be moved (at cost) so parts of California may benifit as well and nationally we would benifit from this being a success that other plants could be modelled on. Likewise, if the east coast wants less air pollution, it may be equally effective for it to fund renewable energy upwind in the West where things like solar are viable than to try to build something like this in a much more cloudy area.
While built regionally, the benefits of this being a solar plant (rather than a coal one) could be national.
I firmly disagree. Passion is key. People who don't give a damn and people who don't enjoy coding tend to write crap. We try to hire for passion and smarts (knowing both are hard to interview for).
Passionate people given good processes and tools are ideal.
This is really the key insight of most Agile methodologies. Development should own the process and change it to suit their needs during regular retrospectives. The team (not the whining individual) should be able to say, "You know what, I think we're not getting bang for our buck out of this many unit tests, let's shift to 50% coverage." As long as that same team is taking ownership of the regression failures and making an informed trade-off their comfortable with, all is well.
If you get a good team together, you're going to get good code. You'll get better code if you empower them. Experienced and good teams will usually have a lot of these processes and tools in place because noticing things like high code complexity automagically alerts them to "bad smells" that can be examined and either accepted as necessary or invested in to address or test more thouroughly.
Generally, I think development is most fun when you're on a new project and don't give a damn about breaking things. Then it's pure creation. But once an app is older and there's some weird code you're staring at you have to decide, "is this probably a bug, or is this a bug fix for some weird situation or platform?" That's when you wish that the guy having fun three years ago had written some damn tests.
70% Unit Coverage:
-- You've written code level tests that flex 70% of your code checking for regression failures.
CCN:
-- Technical term you can look up, but basically it's a measure of how many decision points are in a block of code. Less decision points is simpler. Too many and you may have something difficult to test and difficult for a programmer to understand. Higher complexity generally means more risk and a higher need for testing of various types.
Presprint grooming:
-- A "sprint" is a time block set aside for development. Usually 2-8 weeks. The goal is declare what you're going to get done in that time and not change the requirements during that time. Between sprints, you can change your processes, "groom" stories (tasks that describe things in a user experience way generally).
Test driven dev:
-- When writing a new feature, right a test for that feature first and you're close to done when the test passes and you haven't broken other tests.
I love competing in the job market against people who can't write well.
Now... where's the grammar / spelling error in that sentence? You're going to get me for that slash, aren't you? Contractions in aren't? Sentence fragment? again?
Slashdot Mirror
When there are a lot of stakeholders or process to be moved through, a project manager to keep track of all of that is really key. This is a skillset most people don't really have and a good project manager is a life saver.
At the same time, lots of development shouldn't be treated as "project" work. Tight collaboration between design, development and product leaders are the core. You want project managers to get out of the way there. That's more creative work and no gannt chart is going to help.
Failure to recognize whether what you are working on needs PM is a pretty common failure pattern. A PM doing a lot of work where they shouldn't results in negative contribution, and missing them where they are needed tends to result in failure to deliver.
In the enterprise software business all sales people are commissioned. Except for the ones we had at my last employer. We recognized that sales is hard, competitive and requires special work. At the same time, the key element that wins a deal might be a developer working all night to sneak a feature into a demo or build a new demo environment.
So why do you pay the sales guy a huge commission check for doing his part and the developer her normal salary if the developer was the one with the heroic effort?
You're best off paying everyone a fair salary and chipping in some bonuses and team celebrations to capture heroics.
The rote IT jobs that are best suited for labor arbitrage outsourcing are also the ones that should just be automated out of existence anyway or handled auto-magically by your cloud provider. The remaining jobs are the ones where close collaboration with the business makes them far more effective and those are going to be ones that you're going to regret offshoring.
The number of jobs that don't fall into either of those buckets is getting smaller by the day. It's hard to see how this kind of outsourcing has a long term future.
They point out that anyone bwi wants an image they find in the Getty catalog will find it via image search and steal it. The goal is to offer the embed as a slightly easier way to get the image for free and so have some home of monetizing use from people who will not pay.
That's reasonable.
Advertising isn't evil.
People telling me about cool shit I might want to buy? That's a service. And if they've figured out enough about my behavior to advertise things I'd actually be interested in rather than random shit, that's even better. Please, please, please profile me. It was creepy the first time (ok first hundred times), but I'm over that.
If you lie in an advertisement, that's evil. If you horrendously and needlessly distract from content, that's pretty lame. But if you have a cool pitch to make in the corner of a website I frequent, that's a win-win-win. I get free content. I'm not too distracted. You get my business if you've profiled me well enough and I'm in a buying mood. The website gets paid. Who loses here?
Adblock sites that allow annoying BS that gets in your way. Or better yet, stop visiting them. Let ads in where they behave civilly.
I believe Cord stem cells are rather "pure" stem cells that are very undifferentiated. Making them ideal for a handful of medical procedures and unspecified future medical procedures that may be created. Generally, this nifty resource is lost right after birth (it's thrown away). So some companies have been created to store them, and provide them to you (or others if donated) in the case one of those rare procedures is required.
If I recall correctly, you're looking at $500-$1000 to get things going, and a 50-100 annual fee to maintain. This falls under the broader cateogory of stuff sold under the banner of, "You love your baby right? You'd do anything to protect it? Right? You're not a callous evil person."
They're never pretty and are frequently ugly, but really don't have to be all that bad.
I'm divorced (and now happily re-married!) and while painful, the divorce wasn't ugly. We hired a lawyer together to help us through the paperwork. If you're cheap, there are also forms at Staples. The lawyer was well worth it. I kept most of the furniture and cut my ex a check in return. I had stuff, she had some cash, we were both ok and clear of any alimony claims. I probably could have fought and paid a little less to my ex and a whole lot more to lawyers.
Remember that at the very least you once loved that other person. Treat eachother with some respect, and part civilly. It's strange when you're called, "a model divorcing couple" but a million times better than going to war.
Sounds like there is a market for a mobile testing lab (and the equipment that could fit in a large truck with a generator).
Downstream is a key component. We get rain / melt-off that is used by farmers and cities in other states as well. Water in the west is a precious thing and "ownership" of it is order dependent. Someone owns the first drop of water flowing in the river, and someone else own X gallons / time period only if there's enough left over them after the senior stakeholders are accounted for. Those rights don't care if you are upstream or downstream, but on seniority.
With the possibility of water intensive shale oil extraction, oil companies have been buying senior water rights in Colorado for some time and then leasing them back to farmers / etc. If shale oil happens seriously, and needs the water that's predicted, things could get ugly in a hurry.
I think the "distributed across the map" part is key. In beginner / intermediate play, a really key ability is to actually remember to keep building stuff while scouting or fighting. Can you throw down that building on time while also looking at your opponent's base and gleaning useful information there in an early scout? In an early skirmish, can you micro well enough to gain a minor advantage while also still building workers for the long term economy that actually matters? In the midgame, it's worse, you have building workers, troops, scouting, managing supply, map positioning, upgrades, watching the mini-map for counters/drops, etc, etc, etc all going on at the same time in different places of the map and screen.
90% of the players in the world can't really do these things consistently well because the require you to take care of a lot of background work while actively focused on the exciting stuff. That's genuinely hard and you get better at it incrementally at best.
How did that work out for him in Russia?
BS. My wife scheduled her LA to Sydney flight in sync with Quantas' use of the 380 over 747.
Writing "All X do Y" when talking about people is almost always wrong.
The line really is starting to crumble with DevOps entering the field. While it's still usually two different people with different skill sets. They're increasingly being put on the same delivery team.
As a software company that makes products for IT departments, someone who can write code and "gets" IT is an extremely interesting candidate in a range of positions (from development to solutions engineer).
Your risk is that we (or anyone else) stops believing that you can actually write code. So you'll want to stay sharp there with a pet project, contributions to open source or something along those lines.
At most airports you have the option of mailing that little credit card tool with a knife in it back to yourself. But you probably got it for free at a trade show and would rather bitch about government abuses than pay 6 bucks to mail it to yourself.
Well, at least that's how I felt when the bastards took mine away.
More specifically, they'd be insane to ever have the file. It would mean sending it to them. Much smarter and more efficient to hash the file on your computer (ignore meta-tags) and match against the tag on their server. Done. They never have the file and never look at the incriminating bits.
This is why Apple thinks they can have all your music to you quickly instead of the weeks of upload time to get it to google. Because you don't upload it. They might still be uploading meta information that would be incriminating, but they would have to go out of their way to do so.
Correct, this is not a theory, like the theory of gravity.
It is an attempt to understand the steady increase in global temperatures over the years. There's plenty of refutable science at work. Researches uncover trending data of global temperatures. Other researchers could show problems in approach, or show data that disagrees.
Modelers make predictions of change over the course of years. The accuracy of their predictions speaks to the quality of the models.
Fundamentally, though we have a problem. It would be great if we had two planets. One where we toss as many greenhouse gases into the atmosphere, and another where we do everything the super enviro-crazy vegan wants us to do. Then a hundred years later, we compare temperatures. The problem is that we don't have spare planets to play with. So we have a relatively high stakes game where we work with models, and do a lot of falsify-able detailed science to help inform those models. Only in the models can we run the data for 100 or 1000 years quickly and without much consequence.
Oh, and anyone who would blame Bush for climate change is a nut job. Most of the damage done so far was done before his birth, while he was a child, or while he was a drunk and playboy. It's hard to blame him for any of that. But to argue only against the nut jobs is strawman bullshit. You're right though, czars aren't going to help. A carbon tax might (and might help balance budget or free money for other tax cuts). Helping China build cleaner coal plants might (and would be cheaper than retrofitting ours). But yeah, czars won't help much.
Wow...
Just because it's been cooler at your house for the last two years, does not mean the earth, as a whole, is not getting warmer in general.
It's perfectly plausible that the average temperature on the planet could rise significantly while a region, like Europe, gets colder. For instance, general warming could result in polar warming diminishing the northern ice caps (as we're seeing). Should those ice caps melt enough, the iceberg melting in the north atlantic would dramatically lesson since no glaciers would spawn them. The atlantic currents would be disrupted, lessening the gulf stream. Winds flowing over those warm waters would no longer carry that extra heat to Europe and slowly the weather in Paris starts to resemble Winnepeg (about the same latitude). The good news for Winnepeg is that it's likely to warm up a little.
That's climate change in a nutshell. General warming. Local cooling. Some areas get dryer. Others wetter. Very, very complicated interplay between systems makes predicting winners and losers extremely difficult.
And I swear, the next time there's a snowstorm and people use that as evidence that there isn't global warming, I'm going to punch someone in the face.
Or... our jobs are such that we visit our clients across the country. So I could spend every weekend driving and only be able to cover 20% of the country, or I can take a 10 minute pass through a security line twice a week. I'll take a ten minute inconveinance and let someone fly me somewhere in 4 hours rather than do a four day drive across the country - which would cost more money anyway.
Now, if you live on the East Coast, you might be able to travel to lots of people in a few hours. You might also be enough of a pretentious ass to think the whole country is on the east coast. For the rest of us, flying can be needed. For some of us, it's a regular thing that lets pay for things like food.
At the same time, the states compete with eachother by lowering their tax rates - so they're (almost all) broke. IF moving towards more renewable energy is a national goal, then this is perfectly appropriate. Energy can be moved (at cost) so parts of California may benifit as well and nationally we would benifit from this being a success that other plants could be modelled on. Likewise, if the east coast wants less air pollution, it may be equally effective for it to fund renewable energy upwind in the West where things like solar are viable than to try to build something like this in a much more cloudy area.
While built regionally, the benefits of this being a solar plant (rather than a coal one) could be national.
True enough from a developer's perspective. But I was trying to keep it simple for the lay person.
I firmly disagree. Passion is key. People who don't give a damn and people who don't enjoy coding tend to write crap. We try to hire for passion and smarts (knowing both are hard to interview for).
Passionate people given good processes and tools are ideal.
This is really the key insight of most Agile methodologies. Development should own the process and change it to suit their needs during regular retrospectives. The team (not the whining individual) should be able to say, "You know what, I think we're not getting bang for our buck out of this many unit tests, let's shift to 50% coverage." As long as that same team is taking ownership of the regression failures and making an informed trade-off their comfortable with, all is well.
If you get a good team together, you're going to get good code. You'll get better code if you empower them. Experienced and good teams will usually have a lot of these processes and tools in place because noticing things like high code complexity automagically alerts them to "bad smells" that can be examined and either accepted as necessary or invested in to address or test more thouroughly.
Generally, I think development is most fun when you're on a new project and don't give a damn about breaking things. Then it's pure creation. But once an app is older and there's some weird code you're staring at you have to decide, "is this probably a bug, or is this a bug fix for some weird situation or platform?" That's when you wish that the guy having fun three years ago had written some damn tests.
70% Unit Coverage:
-- You've written code level tests that flex 70% of your code checking for regression failures.
CCN:
-- Technical term you can look up, but basically it's a measure of how many decision points are in a block of code. Less decision points is simpler. Too many and you may have something difficult to test and difficult for a programmer to understand. Higher complexity generally means more risk and a higher need for testing of various types.
Presprint grooming:
-- A "sprint" is a time block set aside for development. Usually 2-8 weeks. The goal is declare what you're going to get done in that time and not change the requirements during that time. Between sprints, you can change your processes, "groom" stories (tasks that describe things in a user experience way generally).
Test driven dev:
-- When writing a new feature, right a test for that feature first and you're close to done when the test passes and you haven't broken other tests.
I love competing in the job market against people who can't write well.
Now... where's the grammar / spelling error in that sentence? You're going to get me for that slash, aren't you? Contractions in aren't? Sentence fragment? again?