That's a pretty big change in just one year since it's 4% greater. The article is misleading.
I did a series of interviews at Google in Kirkland, WA (between Seattle and Microsoft) because I had a free place to stay a couple of blocks away for a friend that's out of the country for two years working for Microsoft in Dublin that was looking for a house sitter. I also had two other friends that are also black that did the same. All three of us gave up before the end of the process. Despite being able to get rid of $1,500 a month and live somewhere nice and have a higher paying job, Google's interview process just made it not worth it. My two friends also gave up since both of them ran out of vacation time to take off from their current jobs to keep going back to Google.
The way I feel about the process is that if you screen resumes well, do a good phone screening, then in person interviews with three or four people, then another interview with someone more senior and you still can't make-up your mind then the problem is with your process, not the candidate. It shouldn't take six months of waffling to make a decision.
Why do you say four times a day is obscene? If you're on four scrum teams then that is what Agile requires. Even worse are the multiple Agile ceremonies that they require you to attend per team per sprint that take many hours each.
and this story is correct in that we haven't completely embraced DevOps. Our dev and DevOps teams use Agile so there's a ridiculous two week minimum delay for any fix since you have to add the JIRA issue to a new sprint before you can fix it. Agile doesn't work well with things that must be fixed for customers. Even worse is since most of our developers are on four scrum teams, they have four stand-ups per day where they need to talk about what they've accomplished and what they commit to doing before the next stand-up. Actually getting work done has suffered since you need to do something superficial each day for four times each day.
And that was the max memory allowed in a mid-2012 model and all new Apple laptops since. We've bought a few Lenovo laptops to get 64 GB and even more Dell Precision 5520 laptops to get 32 GB. They're terrible laptops that have constant problems, especially with drivers and Windows updates so they've cost a lot of developer time just because Apple refuses to allow more memory.
Yep. Not increasing the amount of supported memory in their laptops for over six years is just killing them in the Pro market. We've been buying Dell Precision laptops to get 32 GB of memory, and they're just garbage. We're averaging >50% downtime for them Windows updates and BIOS updates making them unusable. For my personal Precision 5520, I think I've only been able to use it for about five weeks since I first got it last July. The last report I saw for our MacBooks was that IT only had to touch them less than once a year due to problems. Apple laptops are great, but stagnating for six+ years with memory upgrades just means they're not not usable for our use case.
Especially since they haven't allowed memory upgrades beyond 16 GB for over six years! We still have hundreds of four+ year-old MacBooks since we can't upgrade them for more memory. Just sucks having engineers waste time with old and slow laptops, but at least they still basically work unlike a Dell or other PC laptop. As soon as Apple finally allows more memory, we're going to replace most of the laptops used in our company.
Not really. I've worked for several ISPs, and you're right the incremental cost for bandwidth is in general cheap (but not as cheap as the $0.00001 per gigabyte you mentioned), but there's always peering points that are overloaded that are very expensive or even impossible to upgrade.
The last peering upgrade I worked with charged $25/month per Mbps. We did that to help customers get to yelp.com.
It sucks to plug your laptop in to your $250+ USB-C docking station then have the battery die before the end of the day since most high-end laptops need more power than that.
Or worse, the country decides to do a "haircut" like Cyprus did. In other words, they just stole money out of accounts in banks. At first the number of taking 1% was floated then I think the final number was 47.5%. Why would you ever save money if the government could just take almost half of what you saved? That's after paying taxes on making it in the first place.
I'm beginning to think the logging problems with systemd can't be fixed since they've been broken for so many years. Just sucks that there's so often nothing in the journal except the exit status and that output, especially to stdout or stderr, is just swallowed. It's ridiculous that you can start something by hand, see the error message, and fix the problem in a few seconds while systemd can't do the same.
That's what it's all about. When you have one or two scrum meetings a day where you have to talk about what you accomplished since the last meeting and what you commit to before the next meeting, of course you have to work hard. We do two scrum meetings a day during the week, 9am and 8pm, and one at noon on Saturdays and Sundays. People don't think long-term or about quality. All they care about is getting their code reviews done and being able to merge before the next meeting.
But seriously despite the asinine definition that is illogical that the Agile Manifesto gives to this garbage, it's ridiculous to ruin the lives of programmers to push them to complete work before one or two daily meetings. Where I work now, we have four daily meetings, and if you don't have something done then our CEO requires you to wear a pink skirt and sing Total Eclipse of the Heart. Also,. Agile requires that you intentionally ruin any long term planning since you don't think long-term but instead think of sprints. Making software is a marathon, but according to Agile you work people to death for two weeks, abuse them, insult them, insult them, and then repeat that process every two weeks. It's all about abusing people as much as you can legally without being charged with a crime.
Well that's ISO-9001. You don't fix quality problems. You only document them.
The manufacturing company I used to work that I did machine controls for for was certified based on customer contract requirements rather than an actual improvement to the quality. It was fine producing crap as long as it was documented.
> measuring defects
The company I work for now does a ton of QA and create reports, but for most of them there's nothing actionable from that information. Don't measure something you can't use. It's a waste of time.
and for the first time in our history we have more job openings than job seekers. Just sucks for those of us that oppose him that he is keeping campaign promises.
Slashdot Mirror
That's a pretty big change in just one year since it's 4% greater. The article is misleading.
I did a series of interviews at Google in Kirkland, WA (between Seattle and Microsoft) because I had a free place to stay a couple of blocks away for a friend that's out of the country for two years working for Microsoft in Dublin that was looking for a house sitter. I also had two other friends that are also black that did the same. All three of us gave up before the end of the process. Despite being able to get rid of $1,500 a month and live somewhere nice and have a higher paying job, Google's interview process just made it not worth it. My two friends also gave up since both of them ran out of vacation time to take off from their current jobs to keep going back to Google.
The way I feel about the process is that if you screen resumes well, do a good phone screening, then in person interviews with three or four people, then another interview with someone more senior and you still can't make-up your mind then the problem is with your process, not the candidate. It shouldn't take six months of waffling to make a decision.
I hope there's enough left over after legal fees for yourself.
We met at the Linux Expo in 1998, and I enjoyed meeting you.
And systemd written in JavaScript can now less efficiently drop your log messages.
How is that true when this is a ballot initiative? The politicians can't be lobbied to vote for or against it.
Like, the FBI saying, "We'll make sure Hillary wins".
That wasn't the FBI. That was only a few agents that were investigating her.
Why do you say four times a day is obscene? If you're on four scrum teams then that is what Agile requires. Even worse are the multiple Agile ceremonies that they require you to attend per team per sprint that take many hours each.
Four times a day!? That's obscene.
The industry doesn't consider that bad. Agile requires at least one stand-up per day per team you're on.
and this story is correct in that we haven't completely embraced DevOps. Our dev and DevOps teams use Agile so there's a ridiculous two week minimum delay for any fix since you have to add the JIRA issue to a new sprint before you can fix it. Agile doesn't work well with things that must be fixed for customers. Even worse is since most of our developers are on four scrum teams, they have four stand-ups per day where they need to talk about what they've accomplished and what they commit to doing before the next stand-up. Actually getting work done has suffered since you need to do something superficial each day for four times each day.
My 16GB Macbook was no longer able to keep up, ...
And that was the max memory allowed in a mid-2012 model and all new Apple laptops since. We've bought a few Lenovo laptops to get 64 GB and even more Dell Precision 5520 laptops to get 32 GB. They're terrible laptops that have constant problems, especially with drivers and Windows updates so they've cost a lot of developer time just because Apple refuses to allow more memory.
Apple is destroying one of their best markets.
Yep. Not increasing the amount of supported memory in their laptops for over six years is just killing them in the Pro market. We've been buying Dell Precision laptops to get 32 GB of memory, and they're just garbage. We're averaging >50% downtime for them Windows updates and BIOS updates making them unusable. For my personal Precision 5520, I think I've only been able to use it for about five weeks since I first got it last July. The last report I saw for our MacBooks was that IT only had to touch them less than once a year due to problems. Apple laptops are great, but stagnating for six+ years with memory upgrades just means they're not not usable for our use case.
Especially since they haven't allowed memory upgrades beyond 16 GB for over six years! We still have hundreds of four+ year-old MacBooks since we can't upgrade them for more memory. Just sucks having engineers waste time with old and slow laptops, but at least they still basically work unlike a Dell or other PC laptop. As soon as Apple finally allows more memory, we're going to replace most of the laptops used in our company.
> once the infrastructure is in place
Not really. I've worked for several ISPs, and you're right the incremental cost for bandwidth is in general cheap (but not as cheap as the $0.00001 per gigabyte you mentioned), but there's always peering points that are overloaded that are very expensive or even impossible to upgrade.
The last peering upgrade I worked with charged $25/month per Mbps. We did that to help customers get to yelp.com.
Not really since he did it to protect American jobs at Qualcomm. The agreement requires them to buy parts from American companies.
That was just a dumb name for a product for children.
It sucks to plug your laptop in to your $250+ USB-C docking station then have the battery die before the end of the day since most high-end laptops need more power than that.
Asking for a friend.
> a business in a country with a 100% tax rate
Or worse, the country decides to do a "haircut" like Cyprus did. In other words, they just stole money out of accounts in banks. At first the number of taking 1% was floated then I think the final number was 47.5%. Why would you ever save money if the government could just take almost half of what you saved? That's after paying taxes on making it in the first place.
> Log message problems can be fixed...
I'm beginning to think the logging problems with systemd can't be fixed since they've been broken for so many years. Just sucks that there's so often nothing in the journal except the exit status and that output, especially to stdout or stderr, is just swallowed. It's ridiculous that you can start something by hand, see the error message, and fix the problem in a few seconds while systemd can't do the same.
Except for losing log messages and not providing a proper exit status. It's really hard to troubleshoot problems without log messages.
> get them to work harder.
That's what it's all about. When you have one or two scrum meetings a day where you have to talk about what you accomplished since the last meeting and what you commit to before the next meeting, of course you have to work hard. We do two scrum meetings a day during the week, 9am and 8pm, and one at noon on Saturdays and Sundays. People don't think long-term or about quality. All they care about is getting their code reviews done and being able to merge before the next meeting.
so by definition it can't fail.
But seriously despite the asinine definition that is illogical that the Agile Manifesto gives to this garbage, it's ridiculous to ruin the lives of programmers to push them to complete work before one or two daily meetings. Where I work now, we have four daily meetings, and if you don't have something done then our CEO requires you to wear a pink skirt and sing Total Eclipse of the Heart. Also,. Agile requires that you intentionally ruin any long term planning since you don't think long-term but instead think of sprints. Making software is a marathon, but according to Agile you work people to death for two weeks, abuse them, insult them, insult them, and then repeat that process every two weeks. It's all about abusing people as much as you can legally without being charged with a crime.
It was 48 degrees this morning here in Seattle, so what global warming?
Well that's ISO-9001. You don't fix quality problems. You only document them.
The manufacturing company I used to work that I did machine controls for for was certified based on customer contract requirements rather than an actual improvement to the quality. It was fine producing crap as long as it was documented.
> measuring defects
The company I work for now does a ton of QA and create reports, but for most of them there's nothing actionable from that information. Don't measure something you can't use. It's a waste of time.
and for the first time in our history we have more job openings than job seekers. Just sucks for those of us that oppose him that he is keeping campaign promises.
when I yell that there's something on the wing.