News for hackers. Stuff that matters.
Re:Steps to Building an Engineering Competency Matrix by polymerase on Saturday March 02, 2019 @01:58AM (#19287990)
"Consistently writes production-ready code that is easily testable, easily understood by other developers, and accounts for edge cases and errors."

That should be the bar for an E1, let alone E3.

Re:Steps to Building an Engineering Competency Matrix by leib on Saturday March 02, 2019 @04:51AM (#19288505)
You'd expect a new software engineer to do that without code reviews or help from the more experienced?

Lower your expectations ...

Re:Steps to Building an Engineering Competency Matrix by mandeepj on Saturday March 02, 2019 @03:17AM (#19288240)
Exactly my thoughts. I have made the edits in my local copy. Copied E3 into E1, and marked other cells in the row as 'see E1'.