Python 3.4.1 (default, Aug 24 2014, 21:32:40) [GCC 4.2.1 Compatible Apple LLVM 5.1 (clang-503.0.40)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> True = False File "<stdin>", line 1 SyntaxError: can't assign to keyword
That must be it. I clearly have trouble tying my own shoes. Leonard is also barely above average, with an IQ of only 173 and a Princeton PhD at 24. If you know a lot of Leonard characters but consider them below par, I suspect you may have a bit of Sheldon in you.
As long as we're being honest: my friends and I think it's hilarious. We've all been Leonard, probably too often for comfort, and we all have at least one friend from the rest of the gang. They talk about stuff we enjoy and do things (we would hate to admit that) we do. It's not Fine Art, sure, but it's fun.
Even though the show is basically about me and my friends (and apparently you and your friends, too), I never felt like it was making fun of me.
Too many words. Start recording, announce that he's holding you against your will, then barge out. If you make it out the door, you're done. If you don't, then whatever he did to stop you just got you a free timeshare for life and a nice side settlement to cover the travel.
I thought Find My iPhone didn't lock accounts after too many failed logins? [...] I call that a failure in Apple's security.
I call that a way to keep the guy who stole my phone from being able to DOS my attempts to find it afterward.
Or not. Maybe it was just an oversight. But you're making the common mistake of assuming that the requirement you care about is the only one that the designer should have cared about.
Using a password manager is pretty much the same thing as writing down your password. And personally, I think it's less secure than writing the password down on paper and storing it securely.
Thank you for warning us of your opinion in advance. That saves time later when trying to decide whether to have an intelligent conversation with you on the subject.
I love testing. Honestly, if forced at gunpoint to give up testing or version control, I'd be hard pressed to pick. Testing means I can update an innocent-looking line of code without worrying whether it's going to break some arcane business logic that a customer depends on, and that I can gut and reimplement an API while having a reasonable expectation that consumers will keep working afterward. I'm a huge testing advocate.
But.
I have no desire whatsoever to conform to an ISO document about their idea of the right way to do things. Standards are great for ensuring interoperability, but how often do you care about that in a test suite (beyond the minimal "can I make its output look like JUnit so Jenkins can yell at someone when it breaks")?
I'll sit down next to you and help you crank out a comprehensive test suite, because while that's a tedious pain in the ass, it's far less of a pain in the ass than not having one. But I couldn't possibly care less whether the result of our labors is "ISO 29119 Certified (tm)!", probably by a $300 outside consultant, so that we can put an "ISO 29119 Certified (tm)!" logo on our website for PHB's to smile approvingly and longingly at and then forget about.
I think Slashdot ought to consider that some articles, especially those about anonymous internet trolls going open loop, might be set to not allow anonymous posting.
I totally agree that those people should only be free to say the kinds of things we believe. I can't imagine the anarchy of allowing everyone the freedom to speak their opinion, however repugnant.
My first computer with a hard drive was an Amiga 2000 that came with a 120MB Maxtor. I was gleeful at its blinding speed and unfathomable capacity compared to my older floppy-based system. So much so, in fact, that I spent quite a few hours brilliantly doing the AmigaDOS equivalent of cp -R/media/floppy/ so that I'd never have to bother with those slow things again.
That was perhaps my first introduction to the importance of namespaces, a lesson which I carry with me unto this day.
Why would they have lower seek times? It seems like lateral, track-to-track movement would be at the same speed regardless of position. And since rotational velocity is constant, the average time for a sector in the current track to come around should be identical. What's missing from that line of thinking?
You're using "free" in the RMS sense, where the market itself is liberated. You and I agree on this. A free market is one that has been liberated from monopolists and others who want to lock it down for their own benefit.
The Koch brothers want a free-as-in-BSD market where they are free to manipulate it as they see fit without allowing others to benefit.
Which freedom is more important - that of the market or that of the actors in the market? I suppose the answer boils down to your demographic. If you're one of the billionaires who doesn't want to work for a living, you probably want the latter version so that you can run roughshod over rules meant to keep one person from screwing it up for everyone. If you are literally anyone else on the entire planet, you should probably prefer the first definition.
However, there are number of inexpensive (under $10) and free utilities that fixes the interface so that you boot to the desktop and never see it. But... most consumers wouldn't be smart enough to know this. They were forced to use the new UI.
I'm smart enough to know it, but dumb enough not to bother. I'm not an extensive UI customizer (outside of when using Linux and a tiling window manager) - you dance with the date you brought. If I'm on a Mac, I use it like a Mac because that's how all apps, settings, and utilities expect you to use it. Why fight against the current? I'll use the keyboard prefs to put the control key in the right place, but other than that, OK, today I'm a Mac user.
Same with Windows. Sure, I could install a shell that works the way I'm used to everywhere else. But that's struggling against The One True (Terrible) Way and seems futile. Worse, it means I'll only be proficient on that one particular computer, and somewhat lost when using someone else's. When in Windows, I do as the Windows does.
You can know all about the alternative interfaces and still not choose to use them. Personally, I just adopted the approach of not using Windows at all, ever, unless I absolutely have to. It's served me pretty well so far.
My story: Been using Linux and BSD heavily since the 90s. I don't really care if you spell "restart foo" as "/etc/init.d/foo restart", "/usr/local/etc/rc.d/foo.sh restart" "service foo restart", "systemctl restart foo", or just "pkill foo && foo". As an end user of the init systems, those are fungible.
As a developer of things that uses the init systems, there's a huge difference. SysV and BSD inits are close enough in functionality that if you learn one, you can pick up the other. systemd changes that totally, in ways that many of us aren't convinced are actually better. I love learning new stuff! I just changed jobs to learn new stuff! New stuff is cool... but only as long as there's a reason for it. I don't see systemd as being advantageous, at least on the server machines where I spend my days.
I'll be happy to pick up systemd if and when 1) there's no alternative short of maintaining my own private Debian fork, or 2) I can see a reason I'd want to rip out the tried and true, Unix-philosophy-conformant "do one thing and do it well" init systems we have today. As of this moment, systemd seems to do way too much. Given that it's a single point of failure for an entire host, that makes me distrustful.
I bought a Synology NAS and it comes with something called Cloud Station, which is basically Dropbox. You install the client on your machines and it keeps your ~/CloudStation folder in sync with your own NAS. Your data never leaves your personal control. I currently have about 4TB of open storage, which is a little more than the 8GB or so of Dropbox I've accumulated over the years.
I'm sure other NASes offer similar arrangements. Pick one you like, install it, then forget the whole idea of paying some company $$$ per month and praying they care about your privacy.
To be fair, Agile can be freaking awesome. I worked at a devotedly Agile shop and it was a developerocratic utopia. After the few meetings we had, all participants walked away with legitimate action items. You didn't just get called in to listen to something that didn't concern you - if you were invited, it's because you were specifically needed.
I've also worked in places where Agile was a stultifying cover story for "actually waterfall but that doesn't sound as cool so we'll never admit it". That might be the kind of/dev/hell you found yourself stuck in. But that's not Agile Done Right, and shops that Do Agile Right really do exist.
I know all of those words but still have no idea WTF the summary is talking about. Does this boil down to "Wikipedia teens with infinite free time are trying to build fiefdoms", which is the usual explanation for Wikidrama?
Should companies pay for part of the cable bill when employee are required to work from home?
I'm perfectly happy with the compensation of "we'll let you use the Internet connection you already had if you want to not come into the office and be distracted by a hundred meetings and other interruptions".
If you're good you should be in charge of more people
Ummm, no. The skills required to be a good engineer are not the skills required to be a good manager of engineers. There's some overlap, sure, but you can be an outstanding engineer but have poor leadership skills, or be an amazing and revered leader but terrible at actually designing the stuff your people are working on.
You should be in charge of exactly as many people as you are good at being in charge of. That's unrelated to how good you are at being one of the workers.
Programming is complex, system's programming doubly so and C++ is designed to help reduce that complexity, while at the same time remaining resource efficient, when it's used correctly. If it's too hot to handle for you there is always Visual Basic.
Or Go, which looks a lot like C Done Right, was designed for systems programming, and has a positively minimal learning curve compared to C++. I get why C++ exists and what problems it aims to solve, but I don't think I'd want to have to use it to solve those problems when there are more programmer-friendly alternatives.
I have Comcast, and have native IPv6 over my home-grade Internet connection. I can ping6 www.google.com from my autoconfigured laptop without problems.
I don't doubt that they're slow rolling it out everywhere, because when has Comcast ever been in a great hurry to upgrade their network? But here, at least, it works as advertised.
My ISP does IPv6, as does all my equipment. I had to disable it so that the rest of my family doesn't wonder why random sites don't work on their PC but work fine on their phone and while I can't remember the ones off to the top of my head, there are some big ones that regularly fuck up.
Wow, your setup sucks. My ISP offers native IPv6 and all our laptops, tablets, etc. come up with both protocols live. I have literally never, not once, zero times, ever had a problem that traced back to having IPv6 enabled. Maybe we just buy better equipment or have a better ISP or something, because it Just Works for everyone in our household.
In Python 3, they're keywords:
That must be it. I clearly have trouble tying my own shoes. Leonard is also barely above average, with an IQ of only 173 and a Princeton PhD at 24. If you know a lot of Leonard characters but consider them below par, I suspect you may have a bit of Sheldon in you.
As long as we're being honest: my friends and I think it's hilarious. We've all been Leonard, probably too often for comfort, and we all have at least one friend from the rest of the gang. They talk about stuff we enjoy and do things (we would hate to admit that) we do. It's not Fine Art, sure, but it's fun.
Even though the show is basically about me and my friends (and apparently you and your friends, too), I never felt like it was making fun of me.
Too many words. Start recording, announce that he's holding you against your will, then barge out. If you make it out the door, you're done. If you don't, then whatever he did to stop you just got you a free timeshare for life and a nice side settlement to cover the travel.
I thought Find My iPhone didn't lock accounts after too many failed logins? [...] I call that a failure in Apple's security.
I call that a way to keep the guy who stole my phone from being able to DOS my attempts to find it afterward.
Or not. Maybe it was just an oversight. But you're making the common mistake of assuming that the requirement you care about is the only one that the designer should have cared about.
Using a password manager is pretty much the same thing as writing down your password. And personally, I think it's less secure than writing the password down on paper and storing it securely.
Thank you for warning us of your opinion in advance. That saves time later when trying to decide whether to have an intelligent conversation with you on the subject.
I love testing. Honestly, if forced at gunpoint to give up testing or version control, I'd be hard pressed to pick. Testing means I can update an innocent-looking line of code without worrying whether it's going to break some arcane business logic that a customer depends on, and that I can gut and reimplement an API while having a reasonable expectation that consumers will keep working afterward. I'm a huge testing advocate.
But.
I have no desire whatsoever to conform to an ISO document about their idea of the right way to do things. Standards are great for ensuring interoperability, but how often do you care about that in a test suite (beyond the minimal "can I make its output look like JUnit so Jenkins can yell at someone when it breaks")?
I'll sit down next to you and help you crank out a comprehensive test suite, because while that's a tedious pain in the ass, it's far less of a pain in the ass than not having one. But I couldn't possibly care less whether the result of our labors is "ISO 29119 Certified (tm)!", probably by a $300 outside consultant, so that we can put an "ISO 29119 Certified (tm)!" logo on our website for PHB's to smile approvingly and longingly at and then forget about.
I think Slashdot ought to consider that some articles, especially those about anonymous internet trolls going open loop, might be set to not allow anonymous posting.
I totally agree that those people should only be free to say the kinds of things we believe. I can't imagine the anarchy of allowing everyone the freedom to speak their opinion, however repugnant.
(including an officer recall if the feed fails)
No, including "you are only a uniformed officer while the feed is live. If it stops, you are a regular private citizen until it's restarted".
Then it's not police brutality. It's armed citizen brutality, without all the protections of the badge.
My first computer with a hard drive was an Amiga 2000 that came with a 120MB Maxtor. I was gleeful at its blinding speed and unfathomable capacity compared to my older floppy-based system. So much so, in fact, that I spent quite a few hours brilliantly doing the AmigaDOS equivalent of cp -R /media/floppy / so that I'd never have to bother with those slow things again.
That was perhaps my first introduction to the importance of namespaces, a lesson which I carry with me unto this day.
And then LBA came along in 1996 and completely mooted the strategy.
Why would they have lower seek times? It seems like lateral, track-to-track movement would be at the same speed regardless of position. And since rotational velocity is constant, the average time for a sector in the current track to come around should be identical. What's missing from that line of thinking?
Let's put this in geek terms:
You're using "free" in the RMS sense, where the market itself is liberated. You and I agree on this. A free market is one that has been liberated from monopolists and others who want to lock it down for their own benefit.
The Koch brothers want a free-as-in-BSD market where they are free to manipulate it as they see fit without allowing others to benefit.
Which freedom is more important - that of the market or that of the actors in the market? I suppose the answer boils down to your demographic. If you're one of the billionaires who doesn't want to work for a living, you probably want the latter version so that you can run roughshod over rules meant to keep one person from screwing it up for everyone. If you are literally anyone else on the entire planet, you should probably prefer the first definition.
However, there are number of inexpensive (under $10) and free utilities that fixes the interface so that you boot to the desktop and never see it. But... most consumers wouldn't be smart enough to know this. They were forced to use the new UI.
I'm smart enough to know it, but dumb enough not to bother. I'm not an extensive UI customizer (outside of when using Linux and a tiling window manager) - you dance with the date you brought. If I'm on a Mac, I use it like a Mac because that's how all apps, settings, and utilities expect you to use it. Why fight against the current? I'll use the keyboard prefs to put the control key in the right place, but other than that, OK, today I'm a Mac user.
Same with Windows. Sure, I could install a shell that works the way I'm used to everywhere else. But that's struggling against The One True (Terrible) Way and seems futile. Worse, it means I'll only be proficient on that one particular computer, and somewhat lost when using someone else's. When in Windows, I do as the Windows does.
You can know all about the alternative interfaces and still not choose to use them. Personally, I just adopted the approach of not using Windows at all, ever, unless I absolutely have to. It's served me pretty well so far.
My story: Been using Linux and BSD heavily since the 90s. I don't really care if you spell "restart foo" as "/etc/init.d/foo restart", "/usr/local/etc/rc.d/foo.sh restart" "service foo restart", "systemctl restart foo", or just "pkill foo && foo". As an end user of the init systems, those are fungible.
As a developer of things that uses the init systems, there's a huge difference. SysV and BSD inits are close enough in functionality that if you learn one, you can pick up the other. systemd changes that totally, in ways that many of us aren't convinced are actually better. I love learning new stuff! I just changed jobs to learn new stuff! New stuff is cool... but only as long as there's a reason for it. I don't see systemd as being advantageous, at least on the server machines where I spend my days.
I'll be happy to pick up systemd if and when 1) there's no alternative short of maintaining my own private Debian fork, or 2) I can see a reason I'd want to rip out the tried and true, Unix-philosophy-conformant "do one thing and do it well" init systems we have today. As of this moment, systemd seems to do way too much. Given that it's a single point of failure for an entire host, that makes me distrustful.
I bought a Synology NAS and it comes with something called Cloud Station, which is basically Dropbox. You install the client on your machines and it keeps your ~/CloudStation folder in sync with your own NAS. Your data never leaves your personal control. I currently have about 4TB of open storage, which is a little more than the 8GB or so of Dropbox I've accumulated over the years.
I'm sure other NASes offer similar arrangements. Pick one you like, install it, then forget the whole idea of paying some company $$$ per month and praying they care about your privacy.
To be fair, Agile can be freaking awesome. I worked at a devotedly Agile shop and it was a developerocratic utopia. After the few meetings we had, all participants walked away with legitimate action items. You didn't just get called in to listen to something that didn't concern you - if you were invited, it's because you were specifically needed.
I've also worked in places where Agile was a stultifying cover story for "actually waterfall but that doesn't sound as cool so we'll never admit it". That might be the kind of /dev/hell you found yourself stuck in. But that's not Agile Done Right, and shops that Do Agile Right really do exist.
I know all of those words but still have no idea WTF the summary is talking about. Does this boil down to "Wikipedia teens with infinite free time are trying to build fiefdoms", which is the usual explanation for Wikidrama?
Should companies pay for part of the cable bill when employee are required to work from home?
I'm perfectly happy with the compensation of "we'll let you use the Internet connection you already had if you want to not come into the office and be distracted by a hundred meetings and other interruptions".
If you're good you should be in charge of more people
Ummm, no. The skills required to be a good engineer are not the skills required to be a good manager of engineers. There's some overlap, sure, but you can be an outstanding engineer but have poor leadership skills, or be an amazing and revered leader but terrible at actually designing the stuff your people are working on.
You should be in charge of exactly as many people as you are good at being in charge of. That's unrelated to how good you are at being one of the workers.
Trigger warning: butthurt.
Programming is complex, system's programming doubly so and C++ is designed to help reduce that complexity, while at the same time remaining resource efficient, when it's used correctly. If it's too hot to handle for you there is always Visual Basic.
Or Go, which looks a lot like C Done Right, was designed for systems programming, and has a positively minimal learning curve compared to C++. I get why C++ exists and what problems it aims to solve, but I don't think I'd want to have to use it to solve those problems when there are more programmer-friendly alternatives.
Well, right. They don't say, verbatim, "this call is allowed to be recorded". They say "this call may (meaning: is allowed to) be recorded".
I have Comcast, and have native IPv6 over my home-grade Internet connection. I can ping6 www.google.com from my autoconfigured laptop without problems.
I don't doubt that they're slow rolling it out everywhere, because when has Comcast ever been in a great hurry to upgrade their network? But here, at least, it works as advertised.
My ISP does IPv6, as does all my equipment. I had to disable it so that the rest of my family doesn't wonder why random sites don't work on their PC but work fine on their phone and while I can't remember the ones off to the top of my head, there are some big ones that regularly fuck up.
Wow, your setup sucks. My ISP offers native IPv6 and all our laptops, tablets, etc. come up with both protocols live. I have literally never, not once, zero times, ever had a problem that traced back to having IPv6 enabled. Maybe we just buy better equipment or have a better ISP or something, because it Just Works for everyone in our household.