It is interesting that you point this out. I've been seeing port scans for TR-069 for the past 4 days. I've since added the port to a rule that will permanently ban an IP if they try to connect on that port.
Exactly. IOS 9 and 10 were not needed. They didn't bring anything really new, only made things harder to use. The best IOS version was the IOS 8 before the update that introduced Apple music. There was absolutely no reason to make changes, except to support new hardware.
People in the gutter. More bots, less jobs, more homeless people in the gutter. It will also reach the hipsters that create those bots, though they may enjoy 20-30 years of "prosperity" on the back of others, while the society around then is crumbling, at there will be a morning, where they will wake up, and there will be no one left to steal from but themselves, they would have to exit their automated house, and get out of their automated car, into the automated grocery store, only to find out there is no produce on the shelves, and there won't ever be, because all other people are dead, and the hipster automation killed them.
All developers that create automation are mass murderers:)
No, they aren't saving anything, it is pretty clear from the video. They are a non-functioning startup with false claims, both on the video and their website, which still has job openings about developers so they can actually ship anything that remotely works.
This article is false, this is just in ideation phase, with some mockup.
If you watch the video, most of all they are a company for harvesting personal data, like correct addresses, names, phone numbers and services, which is valuable to marketers. These bozos don't do anything for you, you are a product for them.
like linkedin knows what your nationality is. Especially for expats, who are still legally citizens of their original countries but reside somewhere else, linkedin has no clue.
I suggest that you are over exaggerating and looking in the wrong direction. The government doesn't make it expensive. The "for profit" element in the western countries is what makes it expensive. The greedy desire to have anywhere from 400% to 6000% profit.
Is that the same Samsung that is currently being investigated for corrupting the president of South Korea. A president that is currently only supported by 5% of the country population. Those sameshit guys have it coming big way.
With regards to (a) I would very much like to do it. However RND management - the project manager of the team and his manager, who were developers some time ago, see me, the product manager, as an enemy. I am defined as not part of the team, not allowed to participate in any team ceremonies, and under the project manager insistence I am not allow to sit on planning meetings or explain acceptance criteria, participate in estimation, and the team is forbidden from asking me questions at any time except on a specially called for meeting once a week. RND team managers insist on complete separation between me and the team, that I should just give them requirements and they produce on them some time later. They get offended at the mere suggestion that I should spend more time with them and at least sit on standups. Basically they don't want to be in contact.
With regards to (b) I am. However, there is a full contrast where I've previously worked with teams that were spot on - RTM within 2 days error over 9 month period. Teams where even though I was the product manager I sat on every standup, helped them create every test plan, explained the reasoning behind every acceptance criteria, answered any questions of anyone who would walk up to me as soon as they came, pointed out use and corner cases in planning, etc. a team where the team used me as SME providing services to them, and there the project manager understood that we work together. Those were also teams where QA came up with a 26 hours estimate for a particular test plan execution, and I argued that it is 1 hour execution, they were angered at me at first but sat together in a room and I ran through the plan in 62 minutes. The QA lead signed off on the results. No one's pride was hurt, we went together to get some lunch.
Well, let me see how really detached I am from technical work:
At start of project:
My estimate: 490 Story points, +2 senior developers, +1 senior QA, 3rd party cost $20k, GA in 9 months
The team estimate: 305 Story points, no new headcount needed, 3rd party cost 15k, GA in 8 months
Status at the 8th month mark:
220 Story points done, 160 newly estimated story points remaining, 80 story point swag remaining, +4 junior developers, +3 junior QA, 6 months away from GA.
Lather, rinse, repeat
I constantly have to tell the team their estimates are low and unrealistic, as I hear them not discussing corner cases, they take it as an insult to their pride that their estimates are accurate, yet 5 releases down the line they consistently underestimate by as much as 80% and miss release dates by as much as 9 months. Where we were supposed to have a team if 16 senior people, now we have an ever growing team that lastly counted 40 junior people. Every 2-3 months RND management see that they are behind, go out and find some guy fresh out of college, 2 or 3 other developers take 2 months to train the new hire, and as a result we are getting even farther behind, while the new guy is only interested in refactoring to the latest technology buzzword instead of writing new functionality. Refactoring is important, but I generally prefer to have the most senior guys do it, and only after they have been tasked by the Architect to do so.
I go to senior management and tell them, I need X to fund the project. RND management goes to senior management and tells them they need 0.6X to complete the project, senior management buys that number, in reality the project is finished at 1.1X and significant delay. I've done 5 releases with these guys, every time it is the same.
They didn't make 7 better than vista. They just rebadged vista and changed the default UAC policy, nothing else and waited until the CPUs caught up. The winSxS bloat that is in 7 came from vista.
Windows 8 was where they did a ton of optimization so that the runtime resource requirements dropped down to almost XP levels, though the winsxs bloat remains. And Windows 8.1 made something useful out of 8 (got rid of most of Metro crap, though I actually like the tile interface for start page). 8.1 Update 1 broke the improvements to metro a little. If you have software today that works on 8.1 changes are in 5 years it will still work, and allow you to do the same as you do today, be it word processing, gis, cad, endpoint simulation, etc.
There is no reason to have a computer connected to the internet 24/7, use a gateway, allow internet access only when needed.
I have been many things - network engineer, NOC manager, support engineer, defect reproduction engineer, business requirements analyst, product owner, product manager.
I have been in most all places of the lifecycle of a product, both on and off the development team, and also on the customer side. My comment is encompassing all my experience in all those positions, not focusing on a single one.
More often than not, when being on the customer side I have seen products with really good potential shipped prematurely lacking a critical feature with the vendor just not having plans to deliver it, despite all the assurances of the sales guys. I've had to settle for products which were generally inferior but that had that small little thing that actually permitted those product to be used and made legal or compliance happy.
And when being on the PM or BA side I've always made sure we covered that small little thing, that actually allows us to close the sale and actually take the customer with our product to production. I have taken hours to explain to developers and QAs how the customers would use a product and why certain thing makes more sense done one way for business users while it was awkward for the developers.
What I have found out, there are some cultures that say "No" when in fact they mean that they won't be able to do it with current resources. Which is absolutely fine to disclose, but for some reason, they don't do it. They just say "no".
Often PMs aren't unreasonable and don't expect that features are for free. It is perfectly reasonable for a Dev team to present cost estimate which is not only story points but also headcounts, equipment needed, account for decreased productivity and opportunity cost.
Then it is up to the PM to present and defend that cost to execs in a cost/value analysis and if numbers work out the PM can actually help the team get funded and get the job done. But if the team only says "no" instead of "yes, but..." by providing a complete analysis for a means to make it a "yes" sometimes it just doesn't get to a "yes" and the whole product gets scrapped.
I am not trolling, I just work in a dysfunctional organization - just this morning I finished a conversation with my development team who refused to implement a feature and a small change in the QA process that is required by regulation, because it was inconvenient for them and adds 5 minutes to each end to end test case. Without that feature, there is no certification, without certification there is no go to market, without go to market there is no sales, without sales there is no income for the company and by extension no salary for said developers. That is what I mean that we don't make the software just to be comfortable for developers, we actually make the software to sell and profit.
Most developers seem to forget that companies don't make software so it is comfortable for the developers. Most developers argue with the Product Managers that certain new features should not be done, because they are too much of a hassle or go against a policy in the development team. Most developers forget that the company makes the software to sell, and have a profit in the process. Most developers should do their job faster and with better quality and stop arguing with their Product Managers.
What actually makes you qualified to answer any questions? It seems like you are famous for being famous, not for any actual work you have done. You seem to have written books and you are famous for your books, but in most case, it seems to be like the old proverb (not an English one) - those that are knowledgeable and capable work in the field and achieve, those that aren't knowledgeable and capable teach others (or write books, get rich quick schemes (just send me 1500 first), etc.)
Slashdot Mirror
It is interesting that you point this out. I've been seeing port scans for TR-069 for the past 4 days. I've since added the port to a rule that will permanently ban an IP if they try to connect on that port.
Look at this. https://www.att.com/cellphones...
It is the best replacement for a smart phone since sliced bread.
Exactly. IOS 9 and 10 were not needed. They didn't bring anything really new, only made things harder to use. The best IOS version was the IOS 8 before the update that introduced Apple music. There was absolutely no reason to make changes, except to support new hardware.
People in the gutter. More bots, less jobs, more homeless people in the gutter. It will also reach the hipsters that create those bots, though they may enjoy 20-30 years of "prosperity" on the back of others, while the society around then is crumbling, at there will be a morning, where they will wake up, and there will be no one left to steal from but themselves, they would have to exit their automated house, and get out of their automated car, into the automated grocery store, only to find out there is no produce on the shelves, and there won't ever be, because all other people are dead, and the hipster automation killed them.
All developers that create automation are mass murderers :)
No, they aren't saving anything, it is pretty clear from the video. They are a non-functioning startup with false claims, both on the video and their website, which still has job openings about developers so they can actually ship anything that remotely works.
This article is false, this is just in ideation phase, with some mockup.
If you watch the video, most of all they are a company for harvesting personal data, like correct addresses, names, phone numbers and services, which is valuable to marketers. These bozos don't do anything for you, you are a product for them.
like linkedin knows what your nationality is. Especially for expats, who are still legally citizens of their original countries but reside somewhere else, linkedin has no clue.
Cox went downhill somewhere between 2011 and 2014. They are no better than Comcast now.
And then we'll get Miranda and reavers.
I suggest that you are over exaggerating and looking in the wrong direction. The government doesn't make it expensive. The "for profit" element in the western countries is what makes it expensive. The greedy desire to have anywhere from 400% to 6000% profit.
You mean any guy who ever picked up any girl any place in the universe is guilty of fraud?
It is possible, but it will be about 65HP, which is the average European car. Do murican's really want to drive 65hp cars and trucks?
Is that the same Samsung that is currently being investigated for corrupting the president of South Korea. A president that is currently only supported by 5% of the country population. Those sameshit guys have it coming big way.
With regards to (a) I would very much like to do it. However RND management - the project manager of the team and his manager, who were developers some time ago, see me, the product manager, as an enemy. I am defined as not part of the team, not allowed to participate in any team ceremonies, and under the project manager insistence I am not allow to sit on planning meetings or explain acceptance criteria, participate in estimation, and the team is forbidden from asking me questions at any time except on a specially called for meeting once a week. RND team managers insist on complete separation between me and the team, that I should just give them requirements and they produce on them some time later. They get offended at the mere suggestion that I should spend more time with them and at least sit on standups. Basically they don't want to be in contact.
With regards to (b) I am. However, there is a full contrast where I've previously worked with teams that were spot on - RTM within 2 days error over 9 month period. Teams where even though I was the product manager I sat on every standup, helped them create every test plan, explained the reasoning behind every acceptance criteria, answered any questions of anyone who would walk up to me as soon as they came, pointed out use and corner cases in planning, etc. a team where the team used me as SME providing services to them, and there the project manager understood that we work together. Those were also teams where QA came up with a 26 hours estimate for a particular test plan execution, and I argued that it is 1 hour execution, they were angered at me at first but sat together in a room and I ran through the plan in 62 minutes. The QA lead signed off on the results. No one's pride was hurt, we went together to get some lunch.
Well, let me see how really detached I am from technical work:
At start of project:
My estimate: 490 Story points, +2 senior developers, +1 senior QA, 3rd party cost $20k, GA in 9 months
The team estimate: 305 Story points, no new headcount needed, 3rd party cost 15k, GA in 8 months
Status at the 8th month mark:
220 Story points done, 160 newly estimated story points remaining, 80 story point swag remaining, +4 junior developers, +3 junior QA, 6 months away from GA.
Lather, rinse, repeat
I constantly have to tell the team their estimates are low and unrealistic, as I hear them not discussing corner cases, they take it as an insult to their pride that their estimates are accurate, yet 5 releases down the line they consistently underestimate by as much as 80% and miss release dates by as much as 9 months. Where we were supposed to have a team if 16 senior people, now we have an ever growing team that lastly counted 40 junior people. Every 2-3 months RND management see that they are behind, go out and find some guy fresh out of college, 2 or 3 other developers take 2 months to train the new hire, and as a result we are getting even farther behind, while the new guy is only interested in refactoring to the latest technology buzzword instead of writing new functionality. Refactoring is important, but I generally prefer to have the most senior guys do it, and only after they have been tasked by the Architect to do so.
I go to senior management and tell them, I need X to fund the project. RND management goes to senior management and tells them they need 0.6X to complete the project, senior management buys that number, in reality the project is finished at 1.1X and significant delay. I've done 5 releases with these guys, every time it is the same.
With bing rewards they actually pay you. you can get as much as $1.50 a month - a $5 gift card every 4 months or so.
Buy single player games, those that run on your machine, just like the games we grew up with. Don't connect to internet. So.. don't buy from steam.
They didn't make 7 better than vista. They just rebadged vista and changed the default UAC policy, nothing else and waited until the CPUs caught up. The winSxS bloat that is in 7 came from vista.
Windows 8 was where they did a ton of optimization so that the runtime resource requirements dropped down to almost XP levels, though the winsxs bloat remains. And Windows 8.1 made something useful out of 8 (got rid of most of Metro crap, though I actually like the tile interface for start page). 8.1 Update 1 broke the improvements to metro a little. If you have software today that works on 8.1 changes are in 5 years it will still work, and allow you to do the same as you do today, be it word processing, gis, cad, endpoint simulation, etc.
There is no reason to have a computer connected to the internet 24/7, use a gateway, allow internet access only when needed.
Don't ascribe traits predominant in US to the entire human race.
I have been many things - network engineer, NOC manager, support engineer, defect reproduction engineer, business requirements analyst, product owner, product manager.
I have been in most all places of the lifecycle of a product, both on and off the development team, and also on the customer side. My comment is encompassing all my experience in all those positions, not focusing on a single one.
More often than not, when being on the customer side I have seen products with really good potential shipped prematurely lacking a critical feature with the vendor just not having plans to deliver it, despite all the assurances of the sales guys. I've had to settle for products which were generally inferior but that had that small little thing that actually permitted those product to be used and made legal or compliance happy.
And when being on the PM or BA side I've always made sure we covered that small little thing, that actually allows us to close the sale and actually take the customer with our product to production. I have taken hours to explain to developers and QAs how the customers would use a product and why certain thing makes more sense done one way for business users while it was awkward for the developers.
What I have found out, there are some cultures that say "No" when in fact they mean that they won't be able to do it with current resources. Which is absolutely fine to disclose, but for some reason, they don't do it. They just say "no".
..." by providing a complete analysis for a means to make it a "yes" sometimes it just doesn't get to a "yes" and the whole product gets scrapped.
Often PMs aren't unreasonable and don't expect that features are for free. It is perfectly reasonable for a Dev team to present cost estimate which is not only story points but also headcounts, equipment needed, account for decreased productivity and opportunity cost.
Then it is up to the PM to present and defend that cost to execs in a cost/value analysis and if numbers work out the PM can actually help the team get funded and get the job done. But if the team only says "no" instead of "yes, but
I am not trolling, I just work in a dysfunctional organization - just this morning I finished a conversation with my development team who refused to implement a feature and a small change in the QA process that is required by regulation, because it was inconvenient for them and adds 5 minutes to each end to end test case.
Without that feature, there is no certification, without certification there is no go to market, without go to market there is no sales, without sales there is no income for the company and by extension no salary for said developers.
That is what I mean that we don't make the software just to be comfortable for developers, we actually make the software to sell and profit.
Most developers seem to forget that companies don't make software so it is comfortable for the developers. Most developers argue with the Product Managers that certain new features should not be done, because they are too much of a hassle or go against a policy in the development team. Most developers forget that the company makes the software to sell, and have a profit in the process. Most developers should do their job faster and with better quality and stop arguing with their Product Managers.
Both are true. The devices are insecure by design, and are not secured in practice.
What actually makes you qualified to answer any questions? It seems like you are famous for being famous, not for any actual work you have done. You seem to have written books and you are famous for your books, but in most case, it seems to be like the old proverb (not an English one) - those that are knowledgeable and capable work in the field and achieve, those that aren't knowledgeable and capable teach others (or write books, get rich quick schemes (just send me 1500 first), etc.)
What benefit would there be to fueling with people inside the ship? Would they save 30 minutes?
They would have the people in outer space every time, even if the engines never leave the launch pad.