HNHacker News
TopNewBestAskShowJobs

sudeepj

579 karma · joined January 23, 2015

submissionscomments
sudeepj··on Ask HN: The rising “Hackathon Hackers” culture
There is nothing inherently wrong with hackathons. Software development is one of few disciplines in which one can cook-up something valuable quickly in few hours. Imagine medical students trying out this in their discipline :)

However, there is somehow perception that creating via hacking == great engineering. Hacking is a part of engineering. Engineering requires discipline, attention to detail, due diligence and long term view. Think about all the amazing bridges, or design of fighter aircrafts. Sure there might be moments where something was solved with clever hacks in these endeavours, but its the rigor of engineering that makes the product final shape.

There is also non-technical aspect. Great hacker may not be == great team person. All the amazing things around us were created by "teams".

sudeepj··on Ask HN: Studying large code bases
I recently changed my job and I am trying to figure out how the product works there so here is my strategy:

1. Knowing the actual purpose of the product(or system) is must.

2. Using the product yourself helps a lot. This gives you end-user perspective.

3. Reading the code in a context is far more effective. A context here could be a test case or a use case. More granular the scenario the better it is.

4. If you are not able to understand a piece of code, revisit it later and move on. In the meantime note the input and output of "that specific" code. Many times after your move on and read other parts one starts to connect the dots.

5. Never assume anything!

Example: I do not know much of Linux kernel so lets say I want to know when I do "fopen" in C where (& how) does the kernel make entries in its own data structures.

sudeepj··on Letter to a startup, from an employee
Slightly indirectly related to PTO .. Fortunately, I had a great manager with whom I could talk freely on many subjects including this one. I had kind of "rebelled" once about the work-life balance. He did say one which stuck with me. There are cases where one might have to work extra: 1. Your own screw up (includes productivity) 2. Screw up by other teams which affects your work 3. Bad project management which includes unrealistic deadlines

The only thing that you can control is #1 by becoming more productive and more automation.

The #2 is interesting because it is a 2-way street i.e. there will times that someone else might have to work more because you or your team screwed up.

About #3 .. well there is nothing to be done Either endure or leave.

sudeepj··on Show HN: Python based driver to assemble automations from re-usable parts
My first open source project ... looking forward for a feedback
← PreviousPage 7 of 7