HN user

kaustyap

21 karma
Posts0
Comments22
View on HN
No posts found.

I second it. My brain is also tuned to discard most of the information which is easily available for retrieval through print or online resource. I have to write any new information or concept multiple times In order to retain it for few days.

Not sure why no one is talking about serious data breach of personal and credit card information in this case. On the contrary, everyone is very concerned about compromise of github ssh key in another thread.

When company fires such an employee who is innovating and cutting costs, it's like killing golden goose. I am not sure why any employer would think of loosing such valuable asset when in fact they can get more automation done from him.

Starship Update 7 years ago

Right at the end of Q&A session, he seems to spell out his methodology to achieve gigantic proportions: 1. If designing is taking long time to build then it's wrong design and unnecessarily complex. Undesigning is the best thing. 2. Best process is no process. It weighs nothing and costs nothing. 3. Best part is no part. 4. If the schedule is long then it's wrong, if it's tight it's right.

Looking at the demographic representation of users worldwide, does it make sense to deduce that top 5 countries (Ukraine, Turkey, Indonesia, Pakistan, Vietnam) are ones with emerging software industries with many novice programmers and the countries at the bottom have well established industry with experienced programmers?

I prefer not to use mouse at all while coding which I just can't do with IDE. Vim, cscope, ctags provide me all the powerful utilities that I need for faster navigation and editing. Most of the times refactoring needs multiple source files to be looked at and edited simultaneously. In these cases, I split vim in different (even up to 4) screens which enables quick cut-N-paste operations across different files.

It kind of sounds like marketing pitch by fitbit to let potential clients in health industry know that they have so much of data to sell. Otherwise It seems odd for fitbit to share this information with the author.

One of the organization which I know had developed network monitoring tool to determine quality of experience for youtube videos by analyzing packets flowing over the network. The customers of the product were mostly carriers. So obviously they are watching and interested to know bandwidth usage for youtube.

There was a famous pool game with different formats (8-ball, 9-ball, snooker etc) in early 2000. The game-play was pretty realistic but it was demo version and it asked for 6 digit password to unlock all features. I just loaded the executable in editor and voila the only readable digits among the binary data was the password. It was pretty stupid of developers not to encrypt the password!

On contrary I found scrum to be empowering for developers at least in my organization. Earlier, we used to have Technical Manager who provided estimate for a feature/project just based on his gut feeling which often was challenging and not feasible. But then developers needed to burn midnight oil to achieve the targeted release date. It often put enormous pressure on highly talented and competitive developers who had to cover up for less skilled developers. Now the development team is empowered to give its own estimation considering all factors. Mind you, in can lead to overestimation, but then we have experienced Technical Lead working also as a scrum master and individual contributor who is there to correct the course.

In general scrum will work best when 1. The product owner is from technical background with enormous experience under his belt in product development/architecture. The Product owner does not work alone in silos to create backlog but interacts with development team regularly to refine the backlog. In our case, the product owner is someone with 20+ years of experience who has worked in roles like developer/architect.

2. The scrum master is also highly technical person who has been working on the product for several years. In our team, the same person wears different hats as per the need like scrum master/technical leader/individual contributor.

It may not be exactly as per scrum guidelines but worked fine so far for us. Ultimately we need to look for good practices in each methodology and bend it as per our needs.