Richard Yang, a UX designer at Sony, shares his path from a guy with zero experience in design to a respected professional with a high paying job. Much like with any professional, in the past, present or future, it wasn’t an overnight success, but an inhuman amount of work and dedication, with plenty of failure.
OpenSource.com runs this article on “What to know before jumping into a career as an open source lawyer“. Whether or not you are planning to take that path, the article has a few interesting links and quotes.
Recently, at work, we’ve been trying to get a hold of a lawyer with Open Source experience. Just for the consultation or two. I wasn’t very optimistic about it, as I had a feeling those are rare beasts. My suspicion was confirmed to a degree. But this article reaffirms it even further:
Only a few dozen new grads a year are hired to do anything even vaguely involving open source. Only a few dozen lawyers in the entire world dedicate more than a quarter of their time to open source. Only a lucky handful, like those at Software Freedom Law Center (SFLC) and Software Freedom Conservancy (SFC), work primarily directly for communities and volunteer developers.
The article also links to a couple of books on the subject, which I’m pretty sure I’ll need to buy and read soon, unless we find somebody who is actually a lawyer and has done some work in Open Source space.
The Tech Contracts Handbook is a practical, user-friendly reference manual and training guide on cloud computing agreements, software licenses, and other IT contracts. It’s a clause-by-clause “how to” resource, covering the issues at stake and offering negotiation tips and sample contract language.
The Handbook is for both lawyers and businesspeople — including contract managers, procurement officers, in-house and outside counsel, salespeople, and anyone else responsible for getting IT deals done. Perhaps, most important, it uses clear, simple English, like a good contract.
Topics covered include:
- Software-as-a-service (SaaS) subscriptions
- Warranties and service level agreements (SLA’s)
- Data security and privacy
- Disaster recovery (DR)
- Limitations of liability
- Open source software
- Nondisclosure agreements (NDA’s) and confidentiality
- Technology escrow
- Copyright and other intellectual property (IP) licensing
- Internet and e-commerce contracts
- And much more …
The second one is “A Primer on Intellectual Property Licensing“.
A PRIMER ON INTELLECTUAL PROPERTY LICENSING (Second Edition) is a compact, practical guide to one of the most dynamic and popular areas of legal practice today-intellectual property licensing. Developed by an attorney in private practice who specializes in Silicon Valley technology licensing, this guide presents the basic rules of law you need to know for a licensing practice, along with helpful examples of contractual language, practice tips, and insights on custom and practice in the industry. This textbook is appropriate for a law school or business school seminar, or for practicing attorneys who wish to expand their practice into this exciting field. Individual chapters from this text are also available for seminars and CLE presentations (in electronic format).
Amitj Aggarwal, former Staff Engineer at Google (2008-2012), has collected a whole bunch of data in regards to engineers salaries, in USA and worldwide. His points seem to be overly optimistic at times, but I don’t have any links handy to contradict his research.
Here are a few points to get you started:
- Zoho, Salesforce pay 40% more than Oracle, Cisco, GE!!!
- Top 7% or so engineers at Netflix, Amazon, Google, Facebook are paid more than $1.4M per year. Next 10% make $700K on average.
- Facebook has lost relevance to Slack, LinkedIn, Snapchat, Pinterest and Quora. If you are working at Facebook ask for a 50% raise else move to a startup.
- Oracle is loosing to cloud startups. If you are working at Oracle ask for a 60% raise else move to a startup.
- ENGINEERS DO NOT WASTE MONEY ON AN MBA. You will make 2X more on average as an engineer.
- Tableau, Splunk, Slack, Airbnb, Quora, Twitter, Facebook, Google pay more than $320K salary to their top hires. Definitely interview at these fine places. Uber top engineer salaries are $190-340K per year.
- Starting salaries for fresh software engineering graduates is now $130K-160K. Ask shamelessly. For the best ones its ~$180K.
- Apple pays 60% more than Samsung.
Software Engineering Tips shares some tips on how to figure out if you are a bad programmer, and how to remedy that.
Signs that you’re a bad programmer
- Inability to reason about code
- Poor understanding of the language’s programming model
- Deficient research skills / Chronically poor knowledge of the platform’s features
- Inability to comprehend pointers
- Difficulty seeing through recursion
- Distrust of code
If you are not a bad programmer, check if you are mediocre one.
Signs that you are a mediocre programmer
- Inability to think in sets
- Lack of critical thinking
- Pinball Programming
- Unfamiliar with the principles of security
- Code is a mess
And, finally, here are some signs that you shouldn’t be a programmer.
Signs that you shouldn’t be a programmer
- Inability to determine the order of program execution
- Insufficient ability to think abstractly
- Collyer Brothers syndrome
- Dysfunctional sense of causality
- Indifference to outcomes
The article also suggests some alternative career paths for you.