Sign Up Now!

Sign up and get personalized intelligence briefing delivered daily.

Sign Up

Articles related to "engineer"

Salaries for blockchain engineers are skyrocketing, now on par with AI experts

  • That's quite a premium over the $135,000 salaries that typical software engineers earn on average, according to Hired, which uses data from its service to compile the stats.
  • In fact, salaries for engineers with blockchain expertise are on par with developers who specialize in artificial intelligence, and higher than any other specialized engineering roles, Hired says.
  • Hired added blockchain as a sub-role to its service at the end of 2017, and since then, the company has seen postings for jobs that seek employees with blockchain as a desired skill rise by 400 percent.
  • At the moment, these type of jobs tend to carry titles such as back-end engineer, systems engineer or solutions architect, but more of these positions tend to list blockchain as a desired skill for the job, according to Hired.

save | comments | report | share on

Paul Buchheit on Joining Google, How to Become a Great Engineer and Happiness

  • I wanted to go work on Linux stuff and figured I'd at least meet some smart people there, and maybe they'd later start a company that would actually be successful.
  • Partially I think Google had grown so much in my absence, but it was also partly a “boiling the frog” effect: before I spent time away, I hadn't noticed things slowly changing, but when I got back I realized, “Oh wow, here I am in a meeting with a bunch of people I don't know who are telling me to do stuff that I don't care about.” I knew immediately that if I stayed at Google, and wanted to be successful and influential, I would have to become more of a big company person.

save | comments | report | share on

Listening to one's self

  • The point is that no one else is paying their engineers ridiculous sums of money to manage 1000s of servers.
  • Can people benefit from the same kind of thinking (not the ridiculous work hours and culture but the engineering)?
  • Operating at such a large scale is so ingrained for Google that everything they do is "BIG" so it's no wonder then that they champion engineering approaches involving "BIG data".
  • If you go looking for engineering practices structured around having so much data that it doesn't fit on a single server then you're gonna have a bad time.
  • Instead of printing money you are now burning it because you adopted practices that were designed for unimaginable scale.
  • Anyone that has ever managed a large enough software system with a sprawling mess of dependencies has in theory gotten a taste of what it means to operate with microservices.

save | comments | report | share on

Why is Creating a Learning Environment Essential for Technical Teams?

  • But once you find these individuals, it’s crucial that you maintain that learning environment, for the sake of the software engineer as well as the company.
  • From leading Apple’s Finder and Applications group — the team developing the Macintosh’s user interface, which some say is what set Apple apart from their competition — to building the first investor tools at Charles Schwab, he’s seen just how much learning opportunities can motivate and empower software engineers.
  • By building a team of software engineers who are excited about solving problems for customers, you’ll not only be taking care of bugs but building out features and solutions that will facilitate further success for your customers.
  • beside redundant internal tools like building, shipping and analytics, that many companies are building (dunno why), I even saw entire products that can be replaced by OSS versions.

save | comments | report | share on

Did Uber Steal Google’s Intellectual Property?

  • (Today, Google Maps is the dominant navigation app, used daily by more than thirty million people.) Levandowski and his boss, Sebastian Thrun—another Grand Challenge alumnus—then proposed to Google’s leadership that the next step was developing self-driving cars.
  • During the next few years, Project Chauffeur grew to hundreds of employees, and Google spent a small fortune building a fleet of self-driving cars.
  • In 2010, employees began to hear rumors that Levandowski, on behalf of his outside companies, had met with some of Google’s competitors, including a firm that was working with Microsoft, to sell them the same navigational technology that Google was paying to use.
  • When Levandowski was questioned, he said that it was not his intention to help other companies compete with Google, but noted that he was contemplating leaving in order to focus on 510 Systems and Anthony’s Robots, which might become competitors of their own in the self-driving-car business.

save | comments | report | share on