Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
"Future-proofing" isn't simply "going the extra mile" or "adding random junk". Future-proofing is an attempt to anticipate how others might want to use your code beyond those use-cases you originally wrote it for. How well you "future-proof" depends heavily on how well you anticipate what people are likely to want further from your code. So, like many things, knowing your audience is key.
Howโs it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK ๐ฌ๐ง
Education
10 plus years* active enterprise development experience and a Fine art degree ๐จ
It's fine to anticipate, but in my book don't actually add those features until the "future" is the present. The thing about the future is that I can change.
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
"Future-proofing" isn't simply "going the extra mile" or "adding random junk". Future-proofing is an attempt to anticipate how others might want to use your code beyond those use-cases you originally wrote it for. How well you "future-proof" depends heavily on how well you anticipate what people are likely to want further from your code. So, like many things, knowing your audience is key.
It's fine to anticipate, but in my book don't actually add those features until the "future" is the present. The thing about the future is that I can change.
I generally consider "future is present" to encompass "things I assume people will be opening tickets for inside the next 6-12 months".