81–90 of 240 posts
Earlier quoted context omitted.
Yes, that's correct. Although is fairly easy to get accredited if you are a member in order of the state association of engineers.
Well glad I live in California! I’m a college drop out and all self taught. Not a member of any associations. Happily doing lots of great engineering here in the states!
Wow, outside Edmonton... WTF. Do they have a data center there?
It all comes down to world-class talent and their willingness to relocate. John Carmack famously joined Oculus without leaving Dallas, TX. I also believe that Chrome's entire V8 team is based out of Aarhus, Denmark due to Lars Bak's desire to move back home.
In Canada you cannot call a software developer engineer unless he/she is an actual engineer
What's the definition for engineer? Anything that isn't software; ie electrical, mechanical, nuclear? Or does it just mean you passed the FE exam?
Sure, you have to have minimum a bachelor's from an accredited Canadian university, pass an ethics exam, and have supervised experience (or prove that you obtained the equivalent) to join in the first place, but if you don't pay the yearly fee you can only call yourself a "holder of an engineering degree".
Earlier quoted context omitted.
> This sounds like it’s doing packet processing in software From the article: > Based on a custom implementation of IPsec Seems pretty clear.
>custom implementation of IPsec What could possibly go wrong.
Sure, poor implementations can lead to problems, but the same holds true for just about anything.
Earlier quoted context omitted.
Reduce it how? By deploying expensive, unreliable, and hard-to-manage vendor crypto garbage? That is undoubtedly not a trade that a Google would make.
You reduce it by using custom routing ASICs that can handle orders of magnitude more traffic than a CPU with equal or lower power consumption. To put things into perspective: Cisco’s latest routing ASIC — the Cisco Silicon One — can handle 10.8 Tbps (in fixed mode). I’m sure Google and others have evaluated this, but it’s just kind of surprising that they opt to do per-packet processing in software. Disclaimer: I wri…
https://cloud.google.com/blog/products/networking/google-clo...
https://cloud.google.com/security/encryption-in-transit/appl...
In Canada you cannot call a software developer engineer unless he/she is an actual engineer
Earlier quoted context omitted.
Yes, that's correct. Although is fairly easy to get accredited if you are a member in order of the state association of engineers.
Well glad I live in California! I’m a college drop out and all self taught. Not a member of any associations. Happily doing lots of great engineering here in the states!
I'd encourage you not to discount professional bodies as irrelevant, or incapable of becoming more relevant, our industry could benefit from it in many ways - perhaps most frequently on-topic on HN is the ethical and whistle-blowing aspect. Also plenty of professional development and networking, and that only improves as more people that get involved from different (or rather one's own specific) areas.
Earlier quoted context omitted.
Need a degree from an accredited school in engineering + pass the engineering licensing requirements. In Ontario, where I live, that means passing an ethics exam + some years of work that is overseen by someone with a P.Eng. The challenge in software is usually the last part.
Would this mean an engineer in the US who moves to Canada would not be able to practice without getting work accreditation and a license?
Interesting, this is for encrypting server-server traffic. My question: how did Apple end up doing this work in Camrose, Alberta?
I used to go there as a kid. It was one small town, and I don't suppose it has boomed since.
https://www12.statcan.gc.ca/english/census96/data/profiles/R...
https://www12.statcan.gc.ca/census-recensement/2011/dp-pd/hl...
http://municipalaffairs.alberta.ca/documents/msb/2016_Munici...
(It's nice to see that all North American countries are as bad at making websites; practically a tradition at this point!)
Earlier quoted context omitted.
Reduce it how? By deploying expensive, unreliable, and hard-to-manage vendor crypto garbage? That is undoubtedly not a trade that a Google would make.
You reduce it by using custom routing ASICs that can handle orders of magnitude more traffic than a CPU with equal or lower power consumption. To put things into perspective: Cisco’s latest routing ASIC — the Cisco Silicon One — can handle 10.8 Tbps (in fixed mode). I’m sure Google and others have evaluated this, but it’s just kind of surprising that they opt to do per-packet processing in software. Disclaimer: I wri…