I failed to deliver.

Gal Schlezinger on January 18, 2017

I used to be a development infrastructure team leader. Part of my job, as I decided it to be, was to provide tools for teams to communicate with ... [Read Full]
markdown guide
 

Powerful and personal message here, Gal. I really appreciate you sharing your own experiences and flipping them into learning opportunities. Isolating yourself from others has a tendency to lead to a form of tunnel vision. Blocking out others and working in a silo without feedback can really lead you far astray.

There are those who can pull it off, though, but like you say in the article, they are probably focused on the product and are getting early feedback. Or just lucky that their needs match other users' needs :)

I wrote a little about this myself here: codingwithempathy.com/2016/02/23/p...

 

sorry it took me a long time to reply, I'm not that good with emails!
SOME INTERESTING STUFF YOU HAVE THERE and I agree with your post (obviously). oh, and your blog has the awesomest name I've seen in a while. 💯🔥💯
Thank for your reply buddy!

 

Found myself, almost the same guy as you in my team. Ideas for tools, coding for coding, python, js an d more, but there is no real users. Yeah, I also love VIM and CLI, also wrote many scripts for myself. Your idea is helpful, think about your real users and their real requirments, not only for code and technique.

 

Try to be a boring programmer. Make decisions about your product and not about your code.

I'd also add that even before the product consider what is the problem the product will solve.

Nice post.

 

Indeed. Writing code without a clear product definition isn’t as exciting as free-hand tattoo artist, unfortunately.
Thanks for the nice words David!

 

Describing the times we fail is even more powerful than the times we win :)

As someone before me wrote, you can't satisfy everyone, but to satisfy the biggest amount of people possible get their feedback and fast. Small batches are the key here. Deliver little functionality in a short time then start to work on the next part.

When I did an internal project for HR department I asked them lots questions about how they want the stuff to work. I showed the how the app worked till now so when something wasn't ok I could quickly readjust without throwing out to much of an app.

Lot's of people are still lost in development because they want to deliver a great product in one go. Bot how are you tell your product is great without people using them in the first place? Get them something to use before you're all ready to go.

When you work alone... have you ever tried to start an inside company community: there are people willing to work for few hours a week for free just to learn something new :) I'd go for that chance if someone gave it to me :)

 

Thanks for the suggestions Aga! Short delivery spans probably can help for not falling in love with code or features. Community driven projects can also work and I'll try it on my next project! Thanks!!

 

You can't satisfy everyone - that's why we use personas :)

 

I agree! Unfortunately, UX wasn't a thing in my organization for a long time. There are some awesome people around my organization who try to make this whole area of UX better.

There are still some organizations who don't understand the importance of a good UX designer 🤷🏻‍♂️

 

Your coworkers/users don't give a damn if it's implemented with JQuery or React as long as it's useful.

 

Exactly.
However, we should also avoid creating tech debt (writing our own mega frameworks on top of jQuery)
Thanks for reading Lluis!

 
 

Great article! I couldn't agree more with the things you said. :)

 

Haha "couldn't agree more... unfortunately..." 😜
Thanks, David!

 

There is one thing for sure: you didn't fail to deliver. At least not with this post. Thanks for the great article.

 
code of conduct - report abuse