Sira Pîşesaziya Nermalavê

FiroşyarIt's an exciting time to be in the software industry. With the dot com boom and bust, and now “web 2.0” and social networking in the mainstream, we're still in our infancy but growing up.

On a grade level, I'd say we're probably around the 9th grade. We're still uncomfortable in our skin, we get excited by the the software that looks a little ‘overdeveloped', and we're just starting to build friendships that will hopefully last a lifetime.

Consumers are finally getting serious with our software. Product managers are finally getting some good taste – complimenting a great product with good design that's sales and marketing worthy.

That said, the fallacy of the software purchase still exists. When you buy a new car, you generally know that it's going to be comfortable, ride well, how it corners and how it accelerates just from the test drive. If you read about it in an auto magazine by a great journalist, you get a real feeling about how the car is going to feel before you ever get in it.

Software has test drives and reviews as well, but they never live up to our expectations, do they? Part of the problem is that, while cars go forward, backward and have doors and wheels, software doesn't follow the same rules… and nor do any two people use it alike. It isn't until we're mired in our day to day work that we figure out what's ‘missing' with the application. It's missed when it was designed. It's missed when it was developed. And worst, it's always missed in the sale.

This is because you and I don't buy software for how we're going to use it. Often times, we don't actually buy it at all – someone buys it for us. The software we use is often mandated due to a corporate relationship, discount, or the manner in which it interacts with our other systems. It amazes me how many times that companies have a robust purchasing process, certification requirements, service level agreements, security compliance, operating system compatibility… but no one actually uses serîlêdanê heya demek dirêj piştî kirîn û pêkanînê.

It's, perhaps, one of the reasons why pirating software is so rampant. I don't want to even count how many thousands of dollars of software I've purchased that I used and gave up on, and never used again.

Dîmen ji Pargîdaniya Nermalavê

The view from the software company is quite different altogether! Though our applications usually fix a primary problem and that's why people pay for it… there are so many tertiary issues out there that we have to take into consideration when developing it.

  • Çawa xuya dike? - berevajî baweriya populer, nermalav is a beauty contest. I can point to dozens of applications that should ‘own' the market but don't even make the cut because they lack the aesthetics that grab the headlines.
  • Çawa difroşe? - carinan taybetmendiyên bazirganî têne kirin, lê ne bi rastî ew qas bikêr in. Di pîşesaziya e-nameyê de, ji bo demek li wir pişkek mezin bû RSS. Everyone was asking for it but only a couple Email Service Providers had it. The funny thing is, a year later, and it's still not adopted in the mainstream by email marketers. It's one of those features that are marketable, but not really useful (yet).
  • Çiqas ewledar e? – this is one of those ‘small' items that are overlooked but can always sink a deal. As software providers, we should always strive for security and have it backed up through independent audits. Not doing so is irresponsible.
  • Çiqas aram e? – surprisingly, stability is not something that's purchased – but it will make your life miserable if it's an issue. Stability is key to an application's reputation and profitability. The last thing you want to do is hire people to overcome stability issues. Stability is also a key strategy that should be at the foundation of every application. If you don't have a stable foundation, you're building a home that will one day crumble and fall.
  • Çi pirsgirêk çareser dike? - ji ber vê yekê hûn hewceyê nermalavê ne û gelo ew ê alîkariya karsaziya we bike an na. Famkirina pirsgirêkê û pêşxistina çareseriyê ev e ku çima em her roj diçin ser kar.

The secret of the software industry is that we DO NOT sell, buy, build, market and use software well. We have a long way to go before we graduate someday and do it all consistently. To last in this industry, companies often have to develop features and security to sell, but sacrifice usability and stability. It's a dangerous game. I look forward to the next decade and hope that we've matured enough to gain the right balance.

3 Comments

  1. 1

    Yek ji wan pirsên herî dijwar ên ku divê ez bersîv bidim ev e, "Ger hûn jê re dibêjin endezyariya nermalavê, hûn çima ji bo projeyên xwe nikarin encamên diyarker hebin."

    Bersiva min dişibe ya ku hûn li vir qala wê dikin. Ev pîşesaziyek nû ya nû ye. Bi hezaran sal me hilda ku em vegerin cihê ku Romayî bi endezyariyê lê vegeriyan. Yek ji kêliyên min ên bijare li Italytalyayê serdana Pantheon a li Romayê bû û dîtina qulikek ku Brunelleschi qaşo qulikek jêkir da ku fêr bibe ka Romayî çawa qubeyek wusa mezin danîne (dema ku wî dixwest ku fêr bibe ka Duomo li Florence çawa diqede) )

    Em dîsîplînek ciwan in û berî ku em bikaribin nermalava bi qelîte bi rengek domdar hilberînin wê demê bigire. Ji ber vê yekê pêşdebir hîn jî wekî celeb sêrbaz têne dîtin. Em hewce ne ku bi qasî ku em dikarin kontrol bikin (xefkirina taybetmendiyê, dihêle bazirganî mîmariya nermalavê bimeşînin, rêveberiya xirab), lê em nekarin vê rastiyê bihejînin ku hin nermalavan ew girtiye û hin jî na. Heya wê hingê, ev dem dema lêdana zêr e!

  2. 2

    Têgiha pir pêşkeftî di Web 2.0 de wusa rast e. Wusa dixuye ku gelek pargîdanî li dora 1 hilberek têne afirandin ku hûn nefikirin ku dê karibe pargîdaniyek tevahî bidomîne… wê hingê, ew yan dibe xwedan (ku ji bo pargîdaniyê mezin e) an jî piştî pejirandina kêmîn fîzik dike.

  3. 3

    Ez bi tevahî bi ramanê razî me ku pîşesaziya nermalavê bi tevahî di asta pêdivî de pêş neketiye berî ku karibe kontrol bike ku nermalav li xerîdar tê belav kirin. Ez dibêjim wateya wê ya rast rast e dema ku tu dibêjî ku nermalav bi her xerîdarekî re cûda tê bikar anîn û ji ber vê yekê ew her dem her kesî têr nake. Ramana nermalava korsanî ji ber vê nerazîbûna xerîdar çêdibe ji ber ku hûn rast dibêjin hûn ew qas drav ji bo nermalavek didin û wê bikar tînin û dûv re dev ji wê berdidin û carek din wê bikar naynin û ez texmîn dikim ku ev raman dema ku hûn qala xerckirina drav dikin ne guncan e li ser tiştek ku dê demdirêj nebe. Ji ber vê yekê di dawiyê de raman rast e heya ku em nekarin di kirîn, avahî, bazirganî, û karanîna nermalavê de domdar bin em nikanin van ramanên çewt derbikevin rawestînin.

Hûn çi difikirin?

Ev malpera Akismet bikar tîne ku ji bo kêmkirina spam. Zêdetir agahdariya danûstandinên we çawa pêvajoy kirin.