I don’t wanna what it is


Deadline Driven Development

DDD or Deadline Driven Development, a term popularized in a well written article by Joshua Partogi (1) is real yet interesting problem to solve. It is not easy to tackle but nothing impossible right?
For me as software developer having enough experience of DDD is understatement, I’m fed up with it. No MVP, impossible deadline, no clear long term product and bussines vision, Long crunch time and everything in between. Don’t blame developers who think they’re a victim of vicious process.
Fortunately that article comes with good solution by prioritizing, slicing by the amount of cost of delay then doing continuous improvement afterwards. I will not try to explain that points, but I will add my own here.

The main point is to stop thinking as a bunch of victims and realize that we are also part of that vicious cycle. Get the position and speak up, present your concerns and ideas with clear reasoning and back it with good data. It is our job to be a good break for them, and giving options for each concerns.
Crying about how bussines or products people never understand engineer is useless, they will never fully understand us. Always improve team’s confidence for the next wave of impossibility in terms of technical efficiency and ability.

I said that full mutual understanding is not possible but at the end of the day we must agree that our goal is the same.

(1) https://medium.com/modern-management/deadline-driven-development-metodologi-software-development-terpopular-di-indonesia-1ea67ab0cfd0

Alerting is an Art

Too much will make us overwhelmed which eventually lower our alertness to alerts that are important.

Too little makes us do not aware of the state of our system and may miss a problem.

Determining key metrics is the most important step to good alerting, then formulate any form of alert for those metrics. Then divide it into four important quadrants, make sure exposure for critical alert are greater than others or not buried by alerts that are in lower quadrants.

After all that division, now we can determine who should get each alert.

Oh and making sure alert recipient to understand key metric and urgency of each alert is also important.

Gadis permen

Dulu aku kenal seorang wanita yang indah parasnya dan menyenangkan perangainya. Sekali waktu dia meminta permen padaku, tapi aku tak ada karena sudah lama tidak suka permen. Pada perjalanan pulang kusempatkan mampir ke warung untuk membeli segala jenis permen, siapa tahu dia meminta lagi maka bisa dia pilih yang paling disukai.

Esoknya benar dia menanyakan hal yang sama padaku untuk ke-dua kalinya, walau hatiku sangat girang tapi kubilang tak punya. Aku tak berani menunjukkan kegiranganku padanya, aku takut dia berpikir aku membeli permen itu untuk dia, walaupun benar adanya. Biar besok bila dia bertanya lagi akan kuberi.

Kali ini dia bertanya lagi, dan aku masih belum berani memberinya dengan alasan yang sama. Kupikir esok saja kalau dia bertanya lagi. Tapi tidak, dia tidak pernah bertanya lagi hingga kini. Permen-permen itu kutaruh saja akhirnya berserakan di meja.