Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Comment: Re:Answer (Score 3, Insightful) 250

by Spazmania (#49784961) Attached to: How Much C++ Should You Know For an Entry-Level C++ Job?

C++ is not C. C++ written like C tends to be crap code - just an overly complex and distracting language for that coding style. If C++ is the right tool for the job, you need to be using a coding style very similar to C# and Java

That's a bit of a problem, because when you program in C++ the same way you'd program in Java, you lose the efficiency and simplicity of C without gaining the clean design of Java. Java is superior to C++ in almost every reasonable use of C++ *except* the ones which call for programming in C but with, you know, a little bit plus.

If all of that sounds wrong to you, congrats, you're a C coder

I resemble that remark.

Comment: What do you want to do? (Score 1) 1

I'm a software engineer / system administrator / network engineer. I seek jobs which employ all three skill areas because that's what I enjoy.

What do you -want- to do? Will you enjoy work in operations as much as you enjoy work in development? If so, go for it. How? Find a job in a small enough company that folks wear many hats and then learn by doing.

Whatever you choose, don't waste your time with certs. The folks who care about certs have a slot they want you to fit. If you successfully add network engineering to your skill set, you will never fit that slot. You know too much software development and can't help but apply it in your job.

Don't worry overly much about offshoring. For anybody who is any good (at $210k I assume you're pretty good) the risk is way overblown.

Comment: Re:Do people really take this risk seriously? (Score 4, Insightful) 233

by Spazmania (#49752341) Attached to: Asteroid Risk Greatly Overestimated By Almost Everyone

I also disagree with the premise but in the opposite direction.

Risk is the probability of something happening times the damage if it happens.

If Damage = Death of All (functionally infinite), the Probability need only be more than infinitesimal for the Risk to be significant. Is the probability of a mankind-killer asteroid more than infinitesimal? Well, it's happened a couple times before, so while the probability appears quite small it's certainly more than infinitesimal.

Comment: Re:Idiots (Score 1) 221

Even if you dedicated a core and sat in a busy loop polling the NICs for new packets, you'd still have to wait for the receiving NIC to get the whole packet, you'd still have to set up a DMA transfer to ram, you'd still have to look up the address in an O(log n) trie too large to stay in the L3 cache and you'd still have to set up a DMA transfer from ram to the outbound NIC which would still wait for the entire packet before beginning to transmit it.

"Big Iron" routers don't do this. They wait until they have the whole packet. Then the address is looked up in the O(1) TCAM*, a special tri-state static ram that isn't present in your generic x86 machine. Then the packet is transmitted across the backplane to the outgoing interface without ever touching main memory or the the main processor.

Even then the packet tends to get buffered at least twice with a stochastic probability of waiting in the buffer for other traffic to clear. And that's if you're using a high-quality service provider that avoids running links over 80% of capacity.

* TCAM = Ternary Content Addressable Memory. Bits are organized in rows containing an address or subnet. Each bit can have three states: 1, 0 or "don't care." The address to be looked up is injected at the top of the TCAM and compared against all rows in the TCAM during a single clock. The TCAM outputs the position of the first matching row.

Yes, it's a heater.

Comment: Re:Idiots (Score 1) 221

It's not about the number of cores, it's about the expense of the context switches when servicing the interrupt. The x86 architecture doesn't have register banks the way the old Sparc chips did. Every context switch the registers have to be dumped to ram and the new contents loaded from ram. That's an expensive operation.

Comment: Cakewalk (Score 2) 384

by Spazmania (#49737515) Attached to: Ask Slashdot: Best Way To Solve a Unique Networking Issue?

Get a switch which supports VLANs, 1 vlan on each port and the trunk on your laptop. Then run the mfg's software inside virtual machines, each of which has one of the vlans connected to its virtual ethernet, using the mfg's IP address. Now you can run all the updates in parallel.

The better solution is for the mfg to give you software and a configuration that does not suck. But if you're stuck with it, the above will work just fine.

Practical people would be more practical if they would take a little more time for dreaming. -- J. P. McEvoy

Working...