Skip to main content

Wiring the planet

Search This Blog

Essential books for software engineers

on March 05, 2013

Get link
Facebook
X
Pinterest
Email
Other Apps

You become a great software engineer by writing a good chunk of code over many many years. However, books can help accelerate the process. Here are some books that I have personally found very useful.

Algorithms and Data structures

The Algorithm Design Manual
Data Structures and Algorithms in Java (2nd Edition)

Programming

Clean Code: A Handbook of Agile Software Craftsmanship
Programming Pearls (2nd Edition)

Object-oriented design and patterns

Head First Design Patterns
Head First Object-Oriented Analysis and Design
UML Distilled: A Brief Guide to the Standard Object Modeling Language (3rd Edition)

Java

Effective Java (2nd Edition)
Java In A Nutshell, 5th Edition

Functional programming

Functional Programming for Java Developers: Tools for Better Concurrency, Abstraction, and Agility

Javascript

JavaScript: The Definitive Guide
JavaScript: The Good Parts

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

Post a Comment

Popular Posts

Handling exceptions in Apache Camel

Apache Camel is an open source framework for building applications using standard integration patterns. One of the main features of the Apache Camel is the DSL or the Domain Specific Language that it provides for defining mediation and routing rules. A developer can use this DSL through Java, Spring or Scala APIs. The Java APIs are implemented using a "fluent" design pattern . For a novice Camel programmer, it might be a little hard to understand how the fluent design pattern fit withing the mainline Java code. In this blog, we will look at the exception handling within the Camel routes that are built using Java fluent APIs. Following is a simple example of building Camel routes using Java APIs. final class HttpExample { private HttpExample() { } public static void main(String[] args) throws Exception { CamelContext context = new DefaultCamelContext(); final String url = args[0]; // get the target URL from the command line context.addRoutes(new...

We probably lost a $10K coding challenge because of a crappy UI

I attended a Hackathon last weekend and learnt a very important lesson about the role of proper user interface design in communicating one's message. We built some cool stuff, had an eloquent presenter and a solution to a real problem. However we failed to get attention. I would say "What we've got here is (a) failure to communicate".. Let me tell you about our experience. How it started? The 24 hour Hackathon was part of the AT&T Developer summit. Although I have been to a few Hackathons and Startup weekends, this was the first time I competed in one. The event started on a Saturday morning. Because of flight delays, I reached a little late and missed some networking opportunities at the beginning. Around noon, I walked into a slightly chaotic and noisy room where groups of people were having busy conversations. Fortunately for me, two of my colleagues were there with whom I could collaborate. After some discussion, we decided to compete in ...

A better way to define Java error codes

"Use enums instead of int constants" - This is one of the recommendations in the book "Effective Java" . So what's wrong with int constants? Consider these error codes: public static final int INVALID_REQUEST = 0; public static final int MISSING_PARAMETER = 1; public static final int MISSING_HEADER = 2; Here are some limitations if you are using the int constants in your code. There is no type safety since compiler will not complain if you pass the INVALID_REQUEST to a method which expects a different a error code, say MISSING_HEADER. There is no namespace for int constants so there may be name clashes. No way to translate constants to printable strings which is meaningful for a user. The alternative is to use the "enum" type as shown below: public enum MyExceptionCodes { INVALID_REQUEST(0, "The request is invalid"), MISSING_PARAMETER(1, "Required query parameter is missing"), MISSING_HEADER(2, "Required he...

Powered by Blogger