What To Look For When Reviewing C#

About the author

Artak Mkrtchyan is a software engineer from Redmond, WA with over 16 years of software development experience and has been a PullRequest reviewer since October 2019.

Follow Artak on Twitter @mkArtak

By Artak Mkrtchyan

Golang from a C Programmer's Perspective

It didn’t take long for Golang, or Go, to grow on me.

As someone with a background in C and Python, it’s interesting to analyze and compare how the same functionality is implemented in Go. For example, Go compiles down to assembly just like C does. To me, Go is a weird phenomenon as it seems to be a return to form of sorts for programmers. Take away all of the fancy classes, inheritance, and introspection and go back to creating low level structures that describe actual data… kind of.

By Michael Renken

Austin Golang User Group Recap

PullRequest co-founder and CTO Tyler Mann spoke to a packed room at the Austin Golang User Group about the importance of code review in the development life cycle, and security, error handling, and concurrency best practices in Go.

By Brian Rose

The $85 Billion Cost of Bad Code

A recent study from Stripe and Harris Poll found the average developer spends 42% of their time dealing with technical debt and maintenance issues, of which 3.8 hours are spent just on debugging “bad code,” or poor quality code that’s difficult to maintain. The opportunity cost of bad code comes to $85 billion annually — resources that could otherwise be used to build better software.

By Lyal Avery

3 Books on Clean Code Every Developer Should Read

Reading these books will make you a better programmer. You’ll understand the software development process more and reduce technical debt as you write and refactor code. These three essential books will help you learn about clean coding practices that might otherwise be learned in code review or lengthy refactorings.

By Brennan Angel