Java still loves you - Please wait

You must've got that irritating message popping up when you log-in to your windows where it says there is a new version of Java available (or even worse the windows UAC pop-up with the worrying question of "Do you want to allow the following program to make changes to this computer?" ). Well take solace in the fact you are not the only one in history - Java has been irritating the humans with this for quite some time. Joel even wrote a small article in his blog as far back as 2009 and came up with the wise words

 

"...This whole damn dialog could read

Java Loves You—Please Wait

without any loss in functionality..."

 

Well nothing has changed in the intervening years. The message is exactly the same wildly pompous message of 

“By installing Java, you will be able to experience the power of Java”

Actually somethings have changed - Java is now Oracle and the UI has managed become even worse (how they managed this feat is amazing though, extra brownie points for the red java.com hyperlink).

 

Then ...

Java installer in 2009

And now ...


PS. Just a quick disclaimer- we are no Java hate group, actually we love it. Kaz Software has a very strong Java team (it has always had one right from our humble beginning). We work and have worked on all sorts of Java based web applications and love the robustness of the platform. 



Burn the cubicles - in the pursuit of happiness

Kaz revolves around the word happiness. It’s around everything we do. We continually ask ourselves: “are we happy?”. We have a rule of thumb about failure that says: if one day we wake up and think of going to work as a pain then we will know that we have failed.

Many question our principle of happiness as the core business philosophy. Many are clearly baffled that this can be true. And many just laugh it away as a triviality – not believing it to be true. But if you think about it it’s the most obvious thing, it’s amazing that so many companies in the world miss something so basic. The pursuit of happiness is inherently a human endeavor. We spend most of our waking life at work, a significant number of modern human relationships are connected with work – given these facts isn’t it obvious that we need work to be based around happiness?

So what does the pursuit of happiness entail at workspace? There is no sure shot formula – you just have to go by your feelings. But if you were to ask us, what is one thing we must do as the first step in the pursuit for happiness – we would scream:

Say NO to cube farms

Cube farms are evil. They are inhuman. They were made by some alien droids that had no concept about being human and living a normal human life. If you want to achieve anything close to being not sad – burn those cubicles.

So if not cube farms then what? People have to work somewhere. Well we believe that the most natural space in our lives is our homes. So if we can mimic anything about our home at workplace that will bring happiness. So that is why we love our office that is not a purpose built open space for cubicle animals. We work in houses built in the 70’s that we have converted to offices ourselves. They are not inhuman multi-storied building but human two storied buildings (amazingly the two building we are based in are exactly the same architecture because they belong to the same family!). They have open space in front with large trees that have real fruits in the summer (an amazing thing by the way in the concrete mess of Dhaka). They retain old mosaic patterns that were very popular in Dhaka during the 70s and 80s.

 

 

Our seating is as asymmetrical as possible – almost chaotic. We try to give large tables that all look a bit different from each other. We sit with the wall at the back – so that it feels safe and we don’t feel watched. Our monitors are kept in a way so that the screen cannot be viewed by someone approaching us – so that we have our privacy. As un-cubicle like, as possible.

So once again, do everything you can to your workspace to stay away from the cube farms. Be happy!

// Shameless plug begins:

Get our expert help in your software projects today!

// End of shameless plug :)

 

 

Lessons in creating a software business

We are ten years old this month. We started out on June morning in 2004 as a “company” where we had no rules, no goals and no clear plan of what we would do to sustain ourselves – we only knew that we just have to make it a place where people are happy. Over the decade we have learnt many lessons on what to do and what not to do in the business of software. And today I want to write about the lessons we value the most. It would have been great if someone gave me this list ten years ago, but I also wonder if I would have believed it enough to follow it!

Creating a company based on a single vision works

For us it was the vision of: “work should be place of happiness”. It sounds nice, it sounds right but is it good enough to carry a company to profit and permanence? I honestly feel it is – in these ten years a lot of things have happened, many business decisions had to be made and many a crisis had to be overcome, but it was always this single vision that guided us in all our thoughts. Having a single vision meant we could easily decide among multiple options that we had in front of us. It gave us the road to travel and the strength to walk that road fast.

I am not sure if our particular vision is important, it was for us and it worked great. But I think any overarching simple vision that you truly believe in, that everyone in the company can understand and embrace would have worked. Having a simple vision is important. Without it (or with too many of them) I feel we would have been lost.

Software business is all about the right people

Selecting the team members in any company is important. But I feel in the business of software this one thing can make it or break it. You could have the lousiest idea about a software product in the world, but if you have the right people they change it into something amazing – and obviously the other way round. I think in no other modern world business is the product of the business is so malleable, so sensitive to the craftsmanship of the people building it.

So, hiring decisions are the most important decisions in a software company. We learnt to be patient, to be more exact and to be more careful when hiring new team members. If this meant that we lost important business we learnt to live with it – that’s how it is in this world.

Think only in the long term

All our decisions that have been based on short term thinking have failed or have haunted us. Somehow this very ephemeral world of software requires a very non-ephemeral structure to stand on. So we learnt that buying this server “just” for this six month project doesn't mean we can compromise on the quality. We learnt that bending the rules “just” this once to meet this deadline backfires pretty soon. There is nothing short term in software business – it’s hard to believe that this is true given how software projects work.

If you are not hiring a great C++ guy now since you don’t have any projects right now, it’s probably a big mistake. If you are saving a few dollars on a server you’ll probably regret it next month. The list is really long and scary – but if you do want to be successful you just have to believe that you will be around for a very long time.

Only thing that works is an environment of trust

Software is so inherently a collaborative effort that only if people feel safe in trusting others that the whole thing works. Otherwise you spend all your energy trying to force external systems and rules to make that collaboration happen – and it keeps failing. Only an environment of trust can achieve software products that are on time, relatively bug free and usable.

An environment of trust builds up primarily from the actions and policies of the company. It builds up from the actions that people in positions of power take and how those actions are perceived. Any system or rule that you bring that has an impact on that perception has to be considered carefully before it is put in place. So if you thought that nifty time tracking tool you just bought will turn the company around, think again, it might be the first nail in the coffin.

Never, ever be “set in stone”

Software is always a moving thing. And no wonder that a software company should also be like that. What works today, what worked so well last time, has every chance of failing to tomorrow. You will always have to adapt your rules, policies and business practices. If you are doing great as a business now, beware tomorrow the technology might change or the customer’s need for a certain feature might evaporate. That’s how it is in this game. And the only way is to be able to adapt.   

people software company


Failing Better - the secret of great software careers

Samuel Beckett's words "Try again. Fail again. Fail better." are one of the best mantra in a software career. 

It may seem counter intuitive, after all doesn't "fail" equate to "crash" or something similar in software? It does, but that crash if timed right (preferably early on in the development cycle and early on in the developer's career :) ) may prove to be the best thing that happened to the software or the person who wrote it. A crash, you see, tells a developer what not to do. It gives her a chance to find a solution in a better way, it teaches her the invaluable lesson of things to avoid the next time she writes her code. The more fails she has, the more experienced she becomes and the more robust her code becomes.

cool projects for your resume (2).png

The value of experience in software is not in the fact that this person spent that many years in front of a computer, it is in the fact that this person knows that many ways of not doing something. So if you are in the career of writing code for living, welcome the mistakes you make, learn from them and make sure you avoid making that mistake the next time. 

S. A. Andrée and Knut Frænkel with the crashed balloon on the pack ice, photographed by the third expedition member, Nils Strindberg. The exposed film for this photograph and others from the failed 1897 expedition was recovered in 1930.

S. A. Andrée and Knut Frænkel with the crashed balloon on the pack ice, photographed by the third expedition member, Nils Strindberg. The exposed film for this photograph and others from the failed 1897 expedition was recovered in 1930.

I was recently reminded of this when reading about an Arctic expedition that had failed a long time ago.

It was the Andrée's Arctic balloon expedition of 1897 - where three people attempted to fly to north pole on hydrogen balloon and thereby by passing all the dangers and difficulties of a trip by the seas.

In theory great, but they failed in their planning and their safety precautions. They never returned and for a long time nobody knew what happened to them. At last in 1930 their last camp and remains were found in an island. They left detailed log of what they did and many pictures. From these we know that their balloon crashed on the 3rd day of the trip and they tried to walk their way back to civilization. They may have failed, but they taught future explorers about what not to do, about survivals in the extreme cold environments and, of course, not balloon out to north pole with late nineteenth century technology! 

I'll finish with a definitive quote attributed (sometimes) to that great inventor, Thomas Edision, in the context of his failures with creating the light bulb: “I have not failed. I've just found 10,000 ways that won't work.” 

Foundations for a career in programming

One thing we get asked often is how we train our junior coders. And the answer is never an easy one, since we don't have a set training program for this. But we follow some principles, which over the years have worked remarkably well in creating top professionals. Kaz developers are highly valued in the industry - a sure sign that our principles are working. Here are some of the basic principles we use for developing our younger technical staff.:

Charlie Chaplin - The Kid

Charlie Chaplin - The Kid

The master and the apprentice

Coding is a craft, and it needs to be learnt just like how any other craft in this world is learnt - through working as an apprentice to a master craftsman. Using this as the guiding principle, we put our new recruits into a team where there is a guru lead to guide them through their work. The freshers are put on real projects as soon as possible, typically starting with back-end tools working in a pair with a more senior resource - usually the lead. The pair programming model works like magic and we have noticed that within the first few weeks we can transform a not-so-sure person to a very confident coder who can contribute directly to our code. This master-apprentice approach is really a long term process and as the junior programmer works through a wide range of challenges the professional skills improve greatly.

A Swiss knife 

One of the first thing we ensure about freshers is that they are not put in a single technology for too long. The idea is to give them a taste of various technology/programming languages/domains/problem sets so that they can have a balanced view. Our fear is that if a fresher is stuck with a single thing for too long, she might try solving every problem with that single tool rather than choose the correct one (or look for a correct one that she doesn't know about). The aim is to create a Swiss knife rather than a single blade knife. We think after two years of experience in this mode, a resource can be put in a technology where she can start being an expert - by that time she has gained enough experience to know that there are other things out there.

So our freshers go from doing a .NET based auction site this month to a Javascript heavy social app the next month. They may be doing xml conversion the month after. With the wide variety of programming skills available at Kaz this is easily achieved.  

The art of disagreeing 

A major skill in a life in software is the ability to argue well. It is a skill that has to be learnt, practiced and perfected daily. We teach our freshers to be fearless in putting their views across. We teach them to overcome their worry of being wrong - which is typically the biggest block for new comers. We try breaking the ice in every way we can so that they feel comfortable in voicing their disagreements to seniors within the team.    

The loss of ego

Ego kills a great software career - it as simple as that. Ego pushes a person to make irrational decisions about technology. Egos also mean that technology meetings never come to a compromise. Since great coders come with great egos this is a huge problem in the professional software space where teams need to make decisions together and work in harmony.   

It's also one of the hardest thing to get rid of! We try breaking the ego by examples. Our senior resources make a show of displaying that they can be wrong. Saying "Oh I see your point now and I was totally wrong" is something that is pretty common in our culture - and this helps freshers a lot. In some cases individual counseling may also be given - always by someone who is respected for her technical skills.

Creating a tech addict

A life in software is also a life of constantly staying in touch with the latest developments. We take active steps to motivate our freshers to keep reading up new technology and try using those in their work. We move our new recruits into projects that uses new platforms that will challenge them and make them read and learn the new API sets or new paradigm of coding. Our culture of technical excellence also brings in the peer pressure for staying on top of new things - which soon becomes a habit, an addiction! We think this addiction is a must for a great career in software.

So those in short are our secrets for creating great developers. Are we missing anything?  

 

Planning the perfect company event

We've been arranging trips and other company events for the past nine years. And we think we are experts in this field now - at least in arranging  events for software companies.

 We do our yearly anniversary trip which is usually a 8-10 days' trip outside the country, we do a 2-3 days' trip, called the picnic for some long forgotten reason, every year. Apart from these big regular ones, we do several weekend trips to various places within Bangladesh and dozens of smaller events like the borderline insane "hudai party" (see our fb page at fb.com/kazsoftware for more pictures and stories) or more mundane stuff like release dinner parties, training workshops, various sporting events, brainstorming off-sites, etc.

We know pretty well when an event is far from perfect, and we've learnt a few things about what makes a company event approach perfection.

 While planning and finalizing the Thailand trip for this year's anniversary party (Yesssssssssss.... its going to be super cool with 8 days of fun in Ao Nang Beach Krabi) I remembered some of the things we have learnt and thought it would be good to share with my readers. So here goes:

1. Think BIG

It's best to think big. Because if you don't your plan keeps getting budget cuts and will start losing it's charm. Budget will always make things difficult for you whatever the size of company you are - but if you don't aim high the trip/event plan will never be great. So we think seriously big, I mean HUGE and then cut things down one at a time to fit with the money in hand. For example, the moment we thought we could do Thailand this year the first thing we said was that we would never do the old and tired Bangkok-Pattaya thing. It's just not us, 2 days in a crazy city and 2 days in a crowded dirty beach. We searched for the most pristine beach out in Thai coast, found the most expensive looking resort and said we wanted to stay there for 7 days (since 2 days is just too little and saying 8 days would have killed our boss). The resort seemed very happy that about 40 nerdy guys wanted to stay over there, and gave us the cost - a figure which can easily be the deposit for personal jet to fly us out there. So we googled again to find the next best one out on the beach... and the cycle went on.

2. Never underestimate the power of a group

Group travel or group booking does wonders to bring the cost down in any place. Use the group's number to bring down hotel prices, make the bus company give out free seats and make the restaurants give out extra special menus. The power of the group does amazing things to an event plan - use it and over use it. 

3. Have a high up champion 

Make sure someone from the management (or any decision making group) is a strong supporter of the event. Having a powerful champion will solve your problems of fighting the enemy within in the struggle to organize that perfect event. You'll need her support for sure. Since you are thinking big all the time - you will run out of budget, ideas that are real fun may not seem all that good for the company to powerful people, and the list goes on. Your supporter will help you sail through the red tape and make things possible. Without a champion at the right place, you will compromise at all levels and soon end up with an event that is just plain boring.

4. Involve everyone in the group

All decisions should have a feeling that it came from the group. This is vitally important to break the "us and them" feeling that creeps up in company events. The group should be consulted at every point of decision making like venue, things to do etc. This makes the group feel that they are part of the event's planning and that feeling helps them overlook a lot of issues that might otherwise sour the event and draw criticism from the participants. So run surveys, impromptu meetings or just plain group discussions on email to ask for ideas or help.

5. Have an element of surprise

Obviously company events need to be formal to a certain degree. There would be memos describing the event in as boring a way as memos describing appropriate dress code in a business meeting for the nudist resort's website :) But an element of surprise as in the sentence before (hopefully there was one) help liven up the actual event. A surprise could be as simple as ice-cream that wasn't in the menu or a little gift - but it should be done around the beginning to have the right effect.

No longer that much of surprise these days, since we do  it all the time, but we did a branded T-shirt for our trip to Goa a few years back and gave that as gift.

No longer that much of surprise these days, since we do  it all the time, but we did a branded T-shirt for our trip to Goa a few years back and gave that as gift.

6. Create hype

Hype is probably more important than the event itself. The right kind of hype when mixed with the right kind of planning can make a very low budget event a great success. A great thing for a company is that most of the hype can be done for free. Free hype could be as simple as a group emails describing how good the event would be or some aspect of it which is likely to be exciting for the group ("we will see the new VS from MS - still in secret beta!") . Posters in the hallway or even whiteboard screaming out messages can create a lot of hype. But one thing to remember is that hype should be matched somehow in the event itself - or it would be a disaster! So only hype things you know will happen. 

For example, for our Anniversary party at Thailand a series of amazing pictures of sights around Thailand does a great job at building up the excitement which makes the party much more fun.  

 

A picture of the reclining Buddha at Wat Pho in Bangkok, circulated over email or FB page does a great job an creating hype for the upcoming party.

A picture of the reclining Buddha at Wat Pho in Bangkok, circulated over email or FB page does a great job an creating hype for the upcoming party.

7. Create an icon for larger events

Iconography is something people understand. Using a theme, wording and icons help promote an event, makes it more interesting and easier to talk about. For a custom software company like us creating icons, posters and themes is relatively easier since we have our own design teams. Here is our banner for the Thailand trip this month...

 

banner.jpg

Where the wild things are

The title is a tribute to Maurice Sendak whose birthday is today.

Maurice wrote and illustrated amazing children’s books. And his famous “Where the wild things are” is a classic – if you have read it as a child (and actually even as an adult) the images of wild things and the little boy’s reactions to them leaves an indelible mark on you.

Where the wild things are is about a boy (Max) who fell asleep in his room and his dreams. He dreamt that he travelled to a land far away where the wild things are. He conquers the wild things with his look and becomes their king. But he starts missing his home and decides to come back home. When he wakes up he finds his supper waiting in his room.

So what’s the connection between a custom software company in Bangladesh and the children’s picture book? There isn’t a lot really, but I really wanted to introduce Maurice (many of my readers are based in Bangladesh and may not know him that well) and made up my own little connection.

The land of the wild things represents our fears. For a software company like us, that hires the best in the market, the biggest fear is the fear of loss. Our fear of losing our talents to other companies locally is not that great – because we are genuinely a great place to work in Bangladesh and thus represent a top choice for people to work. Thus we rarely lose our talents to other Bangladeshi companies. But those wild software companies in far off lands in the West are a different thing altogether :(

The West has a magical hold on the imagination of people living in developing countries. We tend to think of the West as the fairy tale land where every wish comes true. Our constant exposure to western media from movies to songs to news enhances that magic every day. And in the tiny world of software, is there any other monster more awe inspiring than the likes of Google or Microsoft or thousands of other fabulous software companies that we read about, hear about and watch pictures of everyday?

So where the wild things are for us is the West – those beautiful magical shores of California or fiery autumn forests in New England. And the wild things are those monster software companies that live in that land.

See that’s a good connection! And to extend the connection even more, I hope that our children will one day come back from the land of wild things again to their own little rooms in their own land where their supper waits for them.  

Side note: So how many of our talents have we lost to the wild things? Too painful to answer accurately, so let me just say “many”. We’ve lost so many to the wild things like Microsoft, Amazon or LinkedIn  that I keep seeing their logos on Maurice’s drawings every time I turn open his book to read to my sons…

 

The boy in the picture (second character with the crown) is Max who goes to where the wild things are in the story and he represents our lost talent.

Offshore software development in Bangladesh

Today I will make a case for outsourcing software projects to Bangladesh.

The new offshoring destination in the block

Bangladesh is fast becoming a major player in software development outsourcing. The volume of software projects offshored here has doubled almost every year for the last couple of years. More than twenty thousand people are now working in software or IT services industry. The software industry in Bangladesh is mainly involved with exporting services like custom software development, SQA, design and graphics to European and North American markets.

Micro offshoring revolution! 

Separate to this formal sector, a huge informal sector of Bangladeshi freelancers are driving a micro-sourcing and micro offshoring revolution! Bangladesh consistently tops the freelance work location on sites like oDesk, eLance. This is really an amazing phenomenon, driven mostly by teenagers

​Average cost of a 25 people software project. Source: KPMG study

​Average cost of a 25 people software project. 

Source: KPMG study

Bottomless resource pool

Bangladesh is the 8th most populous country in the world. There is a huge supply of young, trained and English speaking (English being taught from day one at our schools - a side effect of being an ex-British colony) resources. The total cost operation for a typical software offshoring operation is almost 40% lower than countries like India or Philippines. Apart from resource costs other costs like infrastructure, support and management the price advantage with competing outsourcing destinations is significant. Cost of living in India for example is fast becoming comparable with countries like Malaysia or Thailand and thus the future of outsourcing advantage to India is decreasing every year.

This is where Bangladesh outshines others - with very similar educational standards, Bangladeshi resource pool is not fully tapped and its potential to become a major software outsourcing destination is exactly like India of the 90's. A recent KPMG study is a very good read to get an idea about this. 

Maturity of the industry

Software organizations are also becoming mature and standardized. Companies like us that has been doing software development outsourcing from Bangladesh since 2004 have gained huge experience over time. The wide range of projects that we (and other companies around us) have done exposed our developers, testers and mangers to the challenges of software development process. This has created a strong base of experienced, mature and skilled resource who in turn mentors new comers in the profession. A lot of our alumnus has formed separate companies of their own to do offshored software projects, and have carried on the maturity and experience into new areas of works. This migration has also had an effect of evolution on the culture of workplace and software creativity that Kaz values.

More such companies are being setup with proper development  process and management required for outsourcing needs. The creative culture for software development of such organizations are also noteworthy.

We look forward to a great future in software outsourcing in Bangladesh.

 

N.B. Just in case you are new here: we are a custom software company  in Bangladesh making custom web, desktop and mobile apps for other companies and being very good at it! Check out this page to know more about our software development work culture and environment.

What, where, when and how of customized software

Living and breathing software sometimes I forget how the rest of the world perceives this entire space. Sometimes a question from a friend brings me back to reality and makes me think that our world is just another secret world of black magic, potion, secret recipes and spells. 

In those moments of lucidity, I can almost see why our world of custom software development can be something mysterious to people outside this world.

People understand software from the high level of course - they just have to these days. They understand Microsoft is where Word comes from. But when it comes to small shops, like ours, that do one off mobile apps or custom designed software it's hard to understand. The questions that come out are at different levels, the obvious ones are: Why is there a need for such custom software? Who in the world would want one? How would we ever make one? 

So today I will write a small article that sums up the answers from a craftsman's point of view. Note that it is really an attempt by a craftsman to explain is craft and his shop to someone outside his craft - so our techie readers may find this a bit irritating and may well jump ship now! 

 

​Getafix and his cauldron of magic potion.

​Getafix and his cauldron of magic potion.

What?

A customized software is a piece of software written according to the requirements of a customer. It is specific to his needs and if written right it solves just his problems.

Where?

A customized software is usually written at the software company and not at the customer's site. But sometimes the requirements are such that it makes sense to move the developers to write the software at the customer's place. 

When? 

A custom software application should only be written if there are no off-the-shelf software available that does the job. Simply because its much cheaper and much faster to get an off the shelf software. And writing a customized solution would just be waste of effort and money.  For example if you wanted to make MS Word it would probably cost you a few billion dollars (by the way does anyone know the real figure? Googling didn't help).

 

How?

 The process of writing the software can vary. It starts with some initial discussions about what is needed - the requirements. These requirements are then usually put into one or more documents called the specs. Most of the times some pictures would be drawn up to show how the software would solve the problems and meet the requirements. A half working version of the software can also be made quickly to give the customer a feel of the software. Then the work is split up in smaller parts and the software is made it phases. There is a lot of to-and-fro between the customer and software group to see if things are working or not. All throughout testers check if there bugs in the system and the developers fix those bugs. At the end the custom solution is given to the customer - the deployment.

So that is roughly a quick description of the world of custom software. Hope I've not put too many jargon in.  

N.B. Just in case you are new here: we are a custom software company  in Bangladesh making custom web, desktop and mobile apps for other companies and being very good at it! Check out this page to know more about our software development work culture and environment.