Don't meet the qualifications.
I don't either.
I know.
18+ years of experience, but without a piece of paper that only means you were able to sit through 4 years of classes, you're worthless.
Hmm. The first one I owned and programmed on was in 1982.
I'm not worthless to those I'd want to work for. These days, if I were to ever make a job change, I'd be interviewing the employer that approached me more so than they'd be interviewing me.
Heh. I agree here also. I knew going into this company that I'd be fixing all the same old problems I've seen at every small company since the first job in 1991. It'll be another year or two and then they'll either grow, or I'll move on.
Having spent the first 15 years of my SW Engineering career in just that boat, it frustrates me. I did finally get my BSCS degree but now that I'm CTO I insist that we include the phrase "or equivalent experience" in our job postings and mean it. Many of our government contracts specify grade level requirements, but even those generally have a "y degree or x years" phrase.
Smart man.
I'm just gonna leave this here
ROFL! I had a 30+ year hardware design and low level (assembly mostly) acquaintance, post that he'd never heard of SCRUM last week on FB. I had to translate for him... "It's what we old farts used to call a planning meeting."
Then I told him to go Google Scrum Master. Haha.
He sent me a private note... "So how does any of this crap make the code any better?"
Beats me, man. Beats me. But the kids seem to like it.
I got bored and decided that I didn't have enough letters after my name...
-Jim, PMP, CSM, CMRP, CPSM, C.P.M.
Wow you really were bored. I like putting the letter i in lowercase in PMP in the "correct" position to both give a nod to Apple Marketing and also to accurately describe the usual job role accomplished by those with the cert.
What are you really testing with that? I would consider someone scoring VERY well on that test being basically the minimal level of computer competency to be a receptionist at a tech firm.
LOL!
Manufacturers get a prefix then assign them however they see fit. Usually sequentially or grouped by model or whatever. Doesn't matter how they do it, though. Just that they do
Also, they're not guaranteed to be globally unique anymore. Just unique to the layer 2 segment. If they aren't, bad things can and will happen.
It's a bit more complicated than that. Per RFC3927, 169.254/16 is assigned for link-local autoconfiguration, meaning if no static config assigned and no DHCP/BOOTP/etc assigned addressing. So if it doesn't know what to do, it'll follow the RFC spec to figure it out. You can't (per spec) use it for routable things.
10/8 is an RFC1918 (there are three nets assigned) private address that is not Internet routable, so you have to NAT things to get out to the world.
Heh. Ran across that whole "non-unique" even on Layer 2 problem twice in my career. It's a ***** to find. They never were globally unique because certain manufacturers who shall remain nameless, have screwed up before. (Cough, Intel... Cough...)
You forgot RFC 4193 in your discussion of private address space.
I can think of two solid technical ways to "get out to the world" without NAT of an RFC 1918 address.
Hints: Squid and ::ffff might be needed.
I just use 240.0.0.0/4 when I need addresses. They're reserving it for me, anyway.
Oh ok, kidding.
I really just always use 100.64.0.0/10 on my internal networks because everything I do is "carrier grade", baby!
(Heh. Kidding on that one too, of course.)
Want some fun? Look up who has 44.0.0.0/8 assigned to them, and then turn the debugging up real high on a Checkpoint Firewall.
You might notice some cute (and inappropriate) hi-jinx going on.
I believe the content filtering blades trigger it, but haven't confirmed that yet.
Oh, on the original post: You couldn't pay me enough money to ever move to Silicon Valley. Ever.