Skip to main content

Weapon of choice

Everybody has their favorite when it comes to cars, sports or jeans and the same goes for work tools. Some prefer OS X over Linux or Maven over Gradle and don't even get me started on browser wars.
I've had my share of trying out different tools to choose the ones I want to use but every now and then I change some of my tools. This time I'm telling what my day to day tools currently are and why I changed one of them.

The solid foundation


When I get to choose my tools there's one solid foundation that works as a base for all other tools. This has been my number one choice for over ten years with a little variety over time.

Linux.

No question about it, I've used for years, I know my way around it and it offers everything I need in work and at home. The variety comes from different distributions and desktop environments although those have also been very stable for the past four or five years, Debian has the stability I want and XFCE offers everything I need from a desktop.

Crafting tool


I've used various IDE's over the years for JVM languages and web development. There's one that I haven't tried, IDEA, even though I've heard good things about it.

My choice has been Eclipse and it's variations and plugins for several years now for a few reasons. I know how to work with it, it's open source and therefore free and because it's free (and I'm greedy) I can have the same programming interface at work and at home.

In my current work project all other developers are using IDEA and I'm alone with Eclipse but it hasn't caused any problems at any point. All IDE's have their cons and pros so there's no silver bullet in whatever you choose just choose the one that gives you greatest benefit.

Visual aid


I've done a lot of work with different types of technical web services and a lot of those services are being used from web applications. The browser plays a big part as visual tool and as a debugger to verify that everything works correctly from end to end in addition to the fact that just about everything works via browser nowadays. I've tried all the major candidates and for a few years I've used Google Chrome, until the last stable release. I already had some issues with a few previous releases of Chrome and even used the beta version for a while but finally I got tired of trying to figure out the problems that seemed to just accumulate after each release.

I looked into my toolbox and decided to try out Iceweasel, the Debian fork of Firefox, and still had some issues. After Iceweasel I tried vanilla Firefox and haven't looked back since. Firefox isn't new to me. I've used it for years and switched to Chrome a few years back because it's performance was better and rendering was somewhat nicer to my eye. Now, a few years later, Firefox has risen from the ashes and is my #1 choice for the time being.

I think I'm the only developer in our team who's using Firefox... I'm starting to see pattern here.

Comments

Popular posts from this blog

Simple code: Immutability

Immutability is a special thing that in my mind deserves a short explanation and praise. If you're familiar with functional programming you surely recognice the concept of immutability because it's a key ingredient of the paradigm. In the world of object oriented programming it's not as used and as easy to use approach but there are ways to incorporate immutability to parts of the code and I strongly suggest you to do so. Quick intro to immutablity The basic idea of immutability is unchangeable data.  Lets take a example. We have a need to modify a object's property but because the object is immutable we can't just change value but instead we make a copy of the object and while making the copy we provide the new value for the copy. In code it looks something like this. val pencil = Product(name = "Pencil", category = "Office supply") val blackMarker = pencil.copy(name = "Black marker") The same idea can be applied in functions and metho

Simple code: Contracts

Code works around contracts and contracts should be carefully thought and crafted. What are contracts A High abstraction level of contracts for code are API's. They define a interface that is basically a contract that the producer and consumer of the API agree to use to communicate with each other. Two common forms of API's are libraries that are used in code and external API's  that are used via HTTP, RPC etc. When thinking in a bit deeper contracts consist firstly of functions, methods or external endpoints and secondly of data, more precisely on data models and data types within the models.   Defining contracts Contracts should always be defined with careful thought. I've come accross few times to someone saying that "this is for intenal use only so it doesn't need to defined and/or documented as thoughtfully as a public API would be" but I disagree with that. The same care should be be given to internal and external contracts because the contracts are

Simple code: Functions and methods

What makes a good function or method? I don't think it's a single thing but a combination of things where each is significant. If one the things is flawed it affects to all others and the whole function is flawed. So what are those "things"? Have a meaningful name Function should have a name that describes it's purpose or functionality. When a function has a meaningful name it's easy to read and understand what's it's purpose. Let's take a example. If function's purpose is to find a customer by it's id a good name could be findCustomerById(id: String) or it could just as well be just  findCustomer(id: String) because the function signature implies that the customer is found by it's id the word find also implies that the customer might be found or it might not be found. If the function's name would be changed to getCustomer(id: String) it's meaning changes because now it implies that there's no fallback, the customer is e