There's a lot less holding me back from Linux than before (I'm pretty much down to SC2 and VS 2010 for the major apps), so I'll probably switch within next year. But what I _don't_ want to do is to dual-boot. I switch tasks frequently, and rebooting frequently is a pain.
You can't prevent access to the info without stopping them from doing their jobs. All you can do is severely limit the access, and strike whenever someone abuses the right.
That's understandable, but it's very different than claiming that.NET is broken. I've also seen.NET bugs being fixed rather quickly - it really depends. By his definition, all software is broken because it has bugs. This isn't much different than a bug in the JDK, Ogre3D, XNA, libc or whatever.
They don't like.NET yet they keep pumping versions after versions of the.NET Framework, C# and Silverlight. Citation needed? I'm not understanding you well.
I'm not going to call him a liar when he truthfully admitted to doing extremely stupid shit with his password. I don't try and invent facts, I go with what's there.
About half of the people I work with have heard or have played Starcraft, and are interested in Starcraft II. Quasi-same thing for WoW. If they laugh at me because I bring it up when they ask about my hobbies, they're fucking idiots, because they're also laughing at themselves. Maybe the guy who hired you was an uppity get-off-my-lawn moron, but the bosses I've had weren't.
You stick it in your hobbies, not as one of your skills or as past work experience, obviously.
My favorite is seeing something like "select * from MY_TABLE where KEY_VAL=2". This is a trap when it's embedded in your code or your SQL. The asterisk will always return all data columns in schema order. If you try to rearrange the order of columns in your schema (perhaps your modeling method or modeling tool encourages keeping primary key fields in sequential order, and you add a new key field, for example) you will break any code or stored procedures that use the "select *" query.
What vendor lock-in? It's visual studio, and you're still working with source code. Switch over if you find out it doesn't do what you want it to do. He likes VS anyway.
I'm faced with the problem of updating firewall rules on an ASA. So I fire up ASDM to do so. And it fails, because its been a couple of weeks since I did it last,
Honestly, I've heard horror stories about SDM. It's the only Java app that I've heard about that behaves like this (Don't take me wrong, I understand one of the parents' argument about Java web apps, but I don't use them a whole lot), so I believe you on that.
I've always used the command-line to configure Cisco devices for that particular reason.
But the reality is that with DEBs and a repository, RPMs, and a repository, or MSIs and a SMS or Zenworks server, things Just Work(TM).
They don't at all. Your admin may update the app faster than the other company's admin. MSIs don't make things happen the same everywhere, neither do repos. The action of updating isn't guaranteed to happen *everywhere at once* just because you really really want it to.
His point is that you still have to perform apt-get upgrade eventually. Or your admin does. Or a cronjob does. Something does. On the web app site, users load the page and they get the updated version. They don't even have a choice of going back to the previous version. There's no management of upgrades because there are no upgrades. Everything is just accessed from a central location with a web app.
Re:Back to the original subject...
on
Time To Dump XP?
·
· Score: 1
There's a lot less holding me back from Linux than before (I'm pretty much down to SC2 and VS 2010 for the major apps), so I'll probably switch within next year. But what I _don't_ want to do is to dual-boot. I switch tasks frequently, and rebooting frequently is a pain.
Just open up his Google account and go through his email attachments, you'll eventually look at him.
What do you want them to do, hang him high?
You can't prevent access to the info without stopping them from doing their jobs. All you can do is severely limit the access, and strike whenever someone abuses the right.
and you're still too poor to afford a private jet.
Congratulations, you're a tool.
That's understandable, but it's very different than claiming that .NET is broken. I've also seen .NET bugs being fixed rather quickly - it really depends. By his definition, all software is broken because it has bugs. This isn't much different than a bug in the JDK, Ogre3D, XNA, libc or whatever.
Did that even have to do with a .NET bug? They moved away from the MS stack, not .NET particularly IIRC.
GNU SHALL NOT PASS.
You submit bug reports and they fix them. Java has bugs too, C++'s stdlib has bugs too.
What are GNU talking about?
They don't like .NET yet they keep pumping versions after versions of the .NET Framework, C# and Silverlight. Citation needed? I'm not understanding you well.
I'm not going to call him a liar when he truthfully admitted to doing extremely stupid shit with his password. I don't try and invent facts, I go with what's there.
If they can access the router when administrative access is disabled, what makes you think they cannot bypass the password system anyway?
On that note, I really gotta check up with newegg.ca on my brand new Pentium III. I should've paid for fast shipping =(
Don't talk about gaming in interviews.
About half of the people I work with have heard or have played Starcraft, and are interested in Starcraft II. Quasi-same thing for WoW. If they laugh at me because I bring it up when they ask about my hobbies, they're fucking idiots, because they're also laughing at themselves. Maybe the guy who hired you was an uppity get-off-my-lawn moron, but the bosses I've had weren't.
You stick it in your hobbies, not as one of your skills or as past work experience, obviously.
Netcraft hasn't confirmed it yet.
My favorite is seeing something like "select * from MY_TABLE where KEY_VAL=2". This is a trap when it's embedded in your code or your SQL. The asterisk will always return all data columns in schema order. If you try to rearrange the order of columns in your schema (perhaps your modeling method or modeling tool encourages keeping primary key fields in sequential order, and you add a new key field, for example) you will break any code or stored procedures that use the "select *" query.
What the fuck?
Hopefully only a few days so we can get rid of that silly Australia name.
I like to call GNU/Linux by its proper name as well: Linux.
I have a SSD that lasted more than 6 months. Now you're aware of one!
What vendor lock-in? It's visual studio, and you're still working with source code. Switch over if you find out it doesn't do what you want it to do. He likes VS anyway.
I'm faced with the problem of updating firewall rules on an ASA. So I fire up ASDM to do so. And it fails, because its been a couple of weeks since I did it last,
Honestly, I've heard horror stories about SDM. It's the only Java app that I've heard about that behaves like this (Don't take me wrong, I understand one of the parents' argument about Java web apps, but I don't use them a whole lot), so I believe you on that.
I've always used the command-line to configure Cisco devices for that particular reason.
But the reality is that with DEBs and a repository, RPMs, and a repository, or MSIs and a SMS or Zenworks server, things Just Work(TM).
They don't at all. Your admin may update the app faster than the other company's admin. MSIs don't make things happen the same everywhere, neither do repos. The action of updating isn't guaranteed to happen *everywhere at once* just because you really really want it to.
His point is that you still have to perform apt-get upgrade eventually. Or your admin does. Or a cronjob does. Something does. On the web app site, users load the page and they get the updated version. They don't even have a choice of going back to the previous version. There's no management of upgrades because there are no upgrades. Everything is just accessed from a central location with a web app.
Ahahahahahahahaa WHAT? ahahaha. Wow man. Wow.
I just add it to my personal settings.