beginners

12 posts
career

Free ebook: An engineer’s guide to getting more recognition at work

Know what is effective work. Define your priorities. Deliver on time. Assess yourself honestly. Help your peers. Understand your manager's priorities. Get a mentor. Document what you do. Ask for explicit feedback. Talk to your manager regularly.…

Issue59

Practical advice for new software engineers

Get feedback early. Don’t let writing the perfect abstraction slow you down.…

Issue56

What makes code bad?

Remove unreachable code, code that doesn’t do anything and code that was put to set up for future features that never materialised.…

Issue55

Five habits that help code quality

Keep coupling to a minimum. Apply the Principle of Least Astonishment. Minimise cyclomatic complexity…

Issue45

11 rules of effective programming

Leave your code better than you found it. Look for repeatable patterns from references or projects around you or online that have implemented a feature with similar requirements.…

Issue44

Just keep coding! - A letter to junior developers

Develop the willpower, voraciousness, and ambition to learn more and the willingness to go the extra mile. Enjoy the process, rather than focusing on the results.…

Issue36

5 powerful ways to make your code run faster

Optimize only if the program is important and it is genuinely slow. Don’t tune anything without using a good profiling tool first that can help find the hotspots in a program.…

Issue36

7 ways more methods can improve your program

Methods help you hide unnecessary details making the code easier to read. Methods that have well-written names make the programs easy to understand. Methods make programs shorter by avoiding duplication of code.…

Issue35

Does this code spark joy? Tidying up your code bit by bit

Use helper methods and differentiate between sections of code that are accomplishing different tasks. Ensure your tests pass at all times when making changes.…

Issue16

Top 5 Git security mistakes

Use .gitignore to prevent sensitive data from reaching the repository. Use PGP/GPP to sign your commits. Assign access rights to each repository & give access only to the developers who need it.…