news.volyx.in

Woodworking as an escape from the absurdity of software (alinpanaitiu.com)

730 points by imaq · 834 days ago · 518 comments on HN

Article summary

The article discusses the author's experience with feeling burnt out and disconnected from the software development industry, and how they found solace in woodworking as a creative outlet. The author shares their journey of making a chess board and a flute, and how these physical activities helped them cope with the stress and absurdity of software development. The article also touches on the challenges of estimating time and effort in software development, and how this can lead to frustration and burnout. The author reflects on their privilege as a software developer and the importance of finding meaning and fulfillment in one's work.

Main themes

  • Burnout in software development
  • Woodworking as a creative outlet
  • Estimating time and effort
  • Privilege and fulfillment
  • Software development challenges

What commenters say

  • Software engineers are not good at estimating how long tasks will take due to the inherent uncertainty and complexity of software development.
  • Estimating effort, rather than time, is a more accurate and useful approach in software development.
  • The use of abstract measures like t-shirt sizes or story points can help to emphasize the relative complexity of tasks, but may not translate directly to time estimates.
  • Some argue that estimates are impossible to make and add no value, while others believe they provide useful data for prioritizing tasks.
  • The business need for time estimates can lead to pressure on developers to provide inaccurate estimates, which can perpetuate a cycle of frustration and burnout.
  • Estimates can be useful for rough ordering of tasks by complexity, but may not account for unknowns or external factors that can impact completion time.
  • Experience and research can help improve the accuracy of estimates, but even then, estimates may not be precise due to the inherent unpredictability of software development.
  • The value of estimates lies in their ability to facilitate communication and planning, rather than providing a precise prediction of completion time.