I can't even remember how old I am half the time let alone recollect the prefectures of my own country. Hell I can't even remember what countries surround German and I actually lived there for a while.
Anyway, cyber-security of shipping companies is the least of the EU's problems right now. How about you work on finding a way to get the Greeks to do more than 3 hours of work a day?
Or that the don't really need it? So someone finds out I ordered something from Amazon... ok? I mean unless someone was trying to intercept a specific package or something? Maybe? The box has your name, address, and sometimes phone number and e-mail address written right on it!
Zing! Nice one. And by some amazing coincidence the quote that is coming up at the bottom of the page as I type this is: "Q: What do you have when you have a lawyer buried up to his neck in sand? A: Not enough sand."
Why don't we just have Apple, Google & Co., Microsoft and all the mobile manufacturers just exchange a billion dollars with eachother every other week and just skip the lawyers. I didn't even read the article or the summary because I just don't care anymore. Everybody's wrong, software patents and at this point any patent dealing with mobiles or phones is bullshit, and the whole process of suing everyone who even approaches the market will just stifle innovation and kill good ideas.
I think RealPlayer changed their name to Helix at some point so that name is probably cursed or something. Though I do agree, you have an excellent point and I like the name.
Stupid name? Cinnamon vs GNOME? Come to think about it all these years I've been telling people "I use GNOME", I wonder how that sounded to them. Maybe I should have been putting emphasis on the G or something and made it sound like a rapper name. "I use gee-nome dawg".
And even if your phone doesn't there are other dialers out there that probably do, not to mention 3rd party Internet phone apps like Skype which probably do. As long as the manufacturer doesn't distribute the app is it alright?
Come to think of it maybe manufacturers should just distribute a vanilla Android ROM preloaded with whatever crap adware they want and put a sticker along the lines of "Works With Cynogen!" and make the devices openly rootable. Maybe even give the Cynogen guys a hand in the background to make an easy installer to make it as easy as possible.
First off I'm actually a programmer so I entirely understand your points. And I've never fired a programmer because they didn't meet one deadline. But thus far I've had two programmers who ended up just not being able to handle the project, missed multiple deadlines, or just straight out didn't care about finishing the project and made no real effort to finish.
To be honest the only programmer I've straight out fired was one that started writing tons of dummy code and doing things like copying big chunks of code to other files so his commits would look huge and it would look like he was making progress. I wasn't the project lead and wasn't monitoring him directly but he actually pulled this off for a few months and then disappeared a week before an alpha release. Needless to say the lead, who was a designer, hadn't realized his assumption of "he looks like he's writing a lot of code and says he's making progress" wasn't an accurate way of ascertaining things.
Every other time I've given them options to fix things. We work on budgets and the programmers understand that when they come in. It's hard to ask for more money and our deadlines are usually set very late. A week long project for example we'll usually set for 3 weeks. Extensions aren't something we like to do but sometimes we have to, that's just how things go and most customers are understanding. But I've had two programmers that just couldn't get it done and both times they constantly said "just a few more days and it'll be completed", and they always had the option to ask for help but never did. Both times they didn't meet deadlines that were before final release so it wasn't so much of a problem it just meant bringing in another programmer that could do it - I offered them the opportunity to stay on at lower pay and reminded them working with a more capable programmer would help them increase their skills. One accepted and is a much better programmer now, one left.
So that's where I'm coming from on point #2. Would you not have done the same?
Meat packages have QR codes which link to a complete record any nationally raised "meat" when it was still alive, including the farm it was raised in and medical records. Restaurants started displaying the QR codes prominently when the American BSE scare occurred, and the reception was so good many places display information on all the vegetables as well... though granted the information is not nearly as thorough as the meat.
Well you wouldn't give a ruler to a child who was too young to use one. You know, just like you don't give young children screwdrivers and knives.
Of course my son brought Legos out of the office occasionally but that doesn't invalidate having them in a separate room away from the baby. It's a preventative measure and it's far more responsible than just leaving them out in the living room.
Tell you what, go ahead and leave all your Legos and knives and screwdrivers out in reach of your toddler who you never took the time to teach not to stick everything they see in their mouth. You sound like an awesome parent, letting your kid learn from their own mistakes and all. Oh and don't bother securing doors and taping padding to sharp edges, that's mollycoddling them.
I'm doing all the planning myself now, but here it's common to have "planners" who break designs down into tasks, do the scheduling, take into account delays and alter the plans to try and minimize extended development schedules or having to drop features. Planners all have programming and design experience so they're able to estimate pretty well usually. Having worked in teams with planners in the past I have to say I really miss having one.
I set up schedules with the programmers, but we need to fit those schedules into client time frames so sometimes I do have to make assumptions or harder schedules. As for watching commits it's not about micro managing so much as making sure everyone is keeping up and looking out for developers straying from the design. When different modules are developed separately and need to be put together at later points you really need to make sure they are built in a way they will fit together. You could say it's my way of "making sure all your people are productive, clearing roadblocks". I don't deal with recruitment/staffing and there is no management reporting - I deal with a loose knit group of developers/designers/planners/creators mainly on paid OSS projects and I often am the one getting those jobs. I'm not in an office building and none of my developers are forced to come in on any project - they come in because they like to work with me and because I find interesting work for them.
Now if I were in a corporate environment I'd be a lousy manager, but not because I'm too strict but because I'm too lax. I once screwed up by not watching a coder closely enough - he ended up blowing about 2 months when he though he had a better idea of how to do something instead of using a library which I told him to use; which would have implemented the same functionality in a day. When I found out I actually gave him another month to fix things and he still didn't. That killed the project and cost me quite a bit of money - had I been stricter and micro managed more it would not have happened. Other times I've put a lot of time helping developers meet customer deadlines and not collected pay for my time. As you can guess developers really like that kind of management - but it's bad management and these are things you should avoid doing. To say the least I've made a lot of mistakes a "traditional project manager" would not have and those were the things I was trying to point out.
I've met few programmers who could estimate their time-frames so well. Of course I would and do take their voices into account if they worry about missing deadlines, but usually if it looks like they will not meet a deadline or critical pass that just means adding or changing out programmers or picking up the slack myself.
1. Don't piss off programmers. Make them comfortable. 2. They are being paid, make sure they do the work they need to by the time it needs to be done. Stick to schedules. I can not stress how important it is to stick to schedules. If a programmer can't meet targets you feel were set fairly then you may have to fire him/her. If they claim it just takes them longer and you can deal with that then offer them lower pay - in the end results matter and you're on a budget. 3. Listen to advice from your developers carefully. If their ideas are dramatically different than yours in ways you think would be detrimental to the project then they may not understand something. If their ideas are good integrate them. If you don't understand their ideas but they sound good ask the other developers in the pool - a lot of developers get the idea they can do something really cool with some random technology and it just ends up being them the only one that understands it and it never ends up working right. 4. Designate a planner. This will probably be you. The planner takes the goal and the design and makes it into a step by step development cycle programmers can follow. Define critical passes and designate resources such that they come together well. 5. Watch your repositories! Each commit is a record of what a programmer thought. If they misunderstood something you should be able to see that they are going off course by looking at their code. Every day you don't catch this is another day wasted and probably another day it will cost you to bring the code back on course.
That's about all I can think of and all things I really wish I had known before handling teams of developers. Overall you just really need to remember to be focused on results and you really need to watch commits and source changes carefully so you can catch people going off course.
Then install it manually or search for a PPA. Or better yet if you don't find a PPA make one. They just took it out of the main repo, they didn't ban you from installing it.
You've completely misunderstood. Sun Java will no longer be available in the main repository, instead the alternative OpenJDK will be available in the main repositories. If you want Sun Java you can still get it, it's just not in the main repository. By the way, OpenJDK by the way is actually free as in freedom - distributing OpenJDK is holding up the principles of free software significantly more than the license encumbered Sun Java. And it's not just Ubuntu that did it, I recall Sun Java being taken out of Debian at some point years ago over licensing issues.
That's optional and I don't think it's enabled by default. It's not enabled on my workstation and I don't ever remember disabling it but I know I set it to "critical security updates" on my servers.
Hey, I live in a country where the only acceptable levels of lead in most things is 0 as well and I'm glad I do. Still, the Chinese manufacturer there did have kind of a point.
I've got two kids and we were very careful about where we put things. A corner of my office became the Lego and small toy room and we made a habit out of closing the door. On top of that by the time they were toddlers both of my kids didn't shove everything in their mouths like a lot of other kids did, so I guess we did something right there? Regardless when you have kids being careful about what they can reach and making sure you minimize their possibility of injury is something every parent should be doing. Baby ate two magnets in two days? I'd guess bad parents, not bad magnets.
Slashdot Mirror
Ok, thank you for clarifying that. In retrospect my comment was pretty stupid, wasn't it.
Aah, now I see - thank you for informing me. Now I feel stupid for making that comment.
"Somehow I doubt you know them all."
I can't even remember how old I am half the time let alone recollect the prefectures of my own country. Hell I can't even remember what countries surround German and I actually lived there for a while.
Anyway, cyber-security of shipping companies is the least of the EU's problems right now. How about you work on finding a way to get the Greeks to do more than 3 hours of work a day?
Or that the don't really need it? So someone finds out I ordered something from Amazon... ok? I mean unless someone was trying to intercept a specific package or something? Maybe? The box has your name, address, and sometimes phone number and e-mail address written right on it!
Zing! Nice one. And by some amazing coincidence the quote that is coming up at the bottom of the page as I type this is:
"Q: What do you have when you have a lawyer buried up to his neck in sand? A: Not enough sand."
Radical to max.
Why don't we just have Apple, Google & Co., Microsoft and all the mobile manufacturers just exchange a billion dollars with eachother every other week and just skip the lawyers. I didn't even read the article or the summary because I just don't care anymore. Everybody's wrong, software patents and at this point any patent dealing with mobiles or phones is bullshit, and the whole process of suing everyone who even approaches the market will just stifle innovation and kill good ideas.
I think RealPlayer changed their name to Helix at some point so that name is probably cursed or something. Though I do agree, you have an excellent point and I like the name.
Stupid name? Cinnamon vs GNOME? Come to think about it all these years I've been telling people "I use GNOME", I wonder how that sounded to them. Maybe I should have been putting emphasis on the G or something and made it sound like a rapper name. "I use gee-nome dawg".
And even if your phone doesn't there are other dialers out there that probably do, not to mention 3rd party Internet phone apps like Skype which probably do. As long as the manufacturer doesn't distribute the app is it alright?
Come to think of it maybe manufacturers should just distribute a vanilla Android ROM preloaded with whatever crap adware they want and put a sticker along the lines of "Works With Cynogen!" and make the devices openly rootable. Maybe even give the Cynogen guys a hand in the background to make an easy installer to make it as easy as possible.
See title.
http://pioneer.jp/carrozzeria/cybernavi/ That's the only kind of video a navigation unit should ever be displaying.
First off I'm actually a programmer so I entirely understand your points. And I've never fired a programmer because they didn't meet one deadline. But thus far I've had two programmers who ended up just not being able to handle the project, missed multiple deadlines, or just straight out didn't care about finishing the project and made no real effort to finish.
To be honest the only programmer I've straight out fired was one that started writing tons of dummy code and doing things like copying big chunks of code to other files so his commits would look huge and it would look like he was making progress. I wasn't the project lead and wasn't monitoring him directly but he actually pulled this off for a few months and then disappeared a week before an alpha release. Needless to say the lead, who was a designer, hadn't realized his assumption of "he looks like he's writing a lot of code and says he's making progress" wasn't an accurate way of ascertaining things.
Every other time I've given them options to fix things. We work on budgets and the programmers understand that when they come in. It's hard to ask for more money and our deadlines are usually set very late. A week long project for example we'll usually set for 3 weeks. Extensions aren't something we like to do but sometimes we have to, that's just how things go and most customers are understanding. But I've had two programmers that just couldn't get it done and both times they constantly said "just a few more days and it'll be completed", and they always had the option to ask for help but never did. Both times they didn't meet deadlines that were before final release so it wasn't so much of a problem it just meant bringing in another programmer that could do it - I offered them the opportunity to stay on at lower pay and reminded them working with a more capable programmer would help them increase their skills. One accepted and is a much better programmer now, one left.
So that's where I'm coming from on point #2. Would you not have done the same?
Meat packages have QR codes which link to a complete record any nationally raised "meat" when it was still alive, including the farm it was raised in and medical records. Restaurants started displaying the QR codes prominently when the American BSE scare occurred, and the reception was so good many places display information on all the vegetables as well... though granted the information is not nearly as thorough as the meat.
Well you wouldn't give a ruler to a child who was too young to use one. You know, just like you don't give young children screwdrivers and knives.
Of course my son brought Legos out of the office occasionally but that doesn't invalidate having them in a separate room away from the baby. It's a preventative measure and it's far more responsible than just leaving them out in the living room.
Tell you what, go ahead and leave all your Legos and knives and screwdrivers out in reach of your toddler who you never took the time to teach not to stick everything they see in their mouth. You sound like an awesome parent, letting your kid learn from their own mistakes and all. Oh and don't bother securing doors and taping padding to sharp edges, that's mollycoddling them.
You sound like me two years ago. Feel free to learn my mistakes all over again.
Very well put, I couldn't agree with you more.
I'm doing all the planning myself now, but here it's common to have "planners" who break designs down into tasks, do the scheduling, take into account delays and alter the plans to try and minimize extended development schedules or having to drop features. Planners all have programming and design experience so they're able to estimate pretty well usually. Having worked in teams with planners in the past I have to say I really miss having one.
I set up schedules with the programmers, but we need to fit those schedules into client time frames so sometimes I do have to make assumptions or harder schedules. As for watching commits it's not about micro managing so much as making sure everyone is keeping up and looking out for developers straying from the design. When different modules are developed separately and need to be put together at later points you really need to make sure they are built in a way they will fit together. You could say it's my way of "making sure all your people are productive, clearing roadblocks". I don't deal with recruitment/staffing and there is no management reporting - I deal with a loose knit group of developers/designers/planners/creators mainly on paid OSS projects and I often am the one getting those jobs. I'm not in an office building and none of my developers are forced to come in on any project - they come in because they like to work with me and because I find interesting work for them.
Now if I were in a corporate environment I'd be a lousy manager, but not because I'm too strict but because I'm too lax. I once screwed up by not watching a coder closely enough - he ended up blowing about 2 months when he though he had a better idea of how to do something instead of using a library which I told him to use; which would have implemented the same functionality in a day. When I found out I actually gave him another month to fix things and he still didn't. That killed the project and cost me quite a bit of money - had I been stricter and micro managed more it would not have happened. Other times I've put a lot of time helping developers meet customer deadlines and not collected pay for my time. As you can guess developers really like that kind of management - but it's bad management and these are things you should avoid doing. To say the least I've made a lot of mistakes a "traditional project manager" would not have and those were the things I was trying to point out.
I've met few programmers who could estimate their time-frames so well. Of course I would and do take their voices into account if they worry about missing deadlines, but usually if it looks like they will not meet a deadline or critical pass that just means adding or changing out programmers or picking up the slack myself.
I'm sorry, on what points? Keep in mind this is just from my experience and the environments I've been in, I wouldn't expect it to apply to everyone.
1. Don't piss off programmers. Make them comfortable.
2. They are being paid, make sure they do the work they need to by the time it needs to be done. Stick to schedules. I can not stress how important it is to stick to schedules. If a programmer can't meet targets you feel were set fairly then you may have to fire him/her. If they claim it just takes them longer and you can deal with that then offer them lower pay - in the end results matter and you're on a budget.
3. Listen to advice from your developers carefully. If their ideas are dramatically different than yours in ways you think would be detrimental to the project then they may not understand something. If their ideas are good integrate them. If you don't understand their ideas but they sound good ask the other developers in the pool - a lot of developers get the idea they can do something really cool with some random technology and it just ends up being them the only one that understands it and it never ends up working right.
4. Designate a planner. This will probably be you. The planner takes the goal and the design and makes it into a step by step development cycle programmers can follow. Define critical passes and designate resources such that they come together well.
5. Watch your repositories! Each commit is a record of what a programmer thought. If they misunderstood something you should be able to see that they are going off course by looking at their code. Every day you don't catch this is another day wasted and probably another day it will cost you to bring the code back on course.
That's about all I can think of and all things I really wish I had known before handling teams of developers. Overall you just really need to remember to be focused on results and you really need to watch commits and source changes carefully so you can catch people going off course.
Then install it manually or search for a PPA. Or better yet if you don't find a PPA make one. They just took it out of the main repo, they didn't ban you from installing it.
You've completely misunderstood. Sun Java will no longer be available in the main repository, instead the alternative OpenJDK will be available in the main repositories. If you want Sun Java you can still get it, it's just not in the main repository. By the way, OpenJDK by the way is actually free as in freedom - distributing OpenJDK is holding up the principles of free software significantly more than the license encumbered Sun Java. And it's not just Ubuntu that did it, I recall Sun Java being taken out of Debian at some point years ago over licensing issues.
If I had mod points you wouldn't be -1 right now. Troll/Flamebate or not your post is depressingly accurate.
That's optional and I don't think it's enabled by default. It's not enabled on my workstation and I don't ever remember disabling it but I know I set it to "critical security updates" on my servers.
Hey, I live in a country where the only acceptable levels of lead in most things is 0 as well and I'm glad I do. Still, the Chinese manufacturer there did have kind of a point.
I've got two kids and we were very careful about where we put things. A corner of my office became the Lego and small toy room and we made a habit out of closing the door. On top of that by the time they were toddlers both of my kids didn't shove everything in their mouths like a lot of other kids did, so I guess we did something right there? Regardless when you have kids being careful about what they can reach and making sure you minimize their possibility of injury is something every parent should be doing. Baby ate two magnets in two days? I'd guess bad parents, not bad magnets.