Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="LWDPressRelease" data-source="post: 4911278" data-attributes="member: 77732">Thanks. We stay pretty busy. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":-)" title="Smile    :-)"  data-smilie="1"data-shortname=":-)" />I've been doing software development - for pay - for 29 years now. So I remember those days. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":-)" title="Smile    :-)"  data-smilie="1"data-shortname=":-)" />I wholly agree with this tendency. I find myself tempted down that path as well sometimes. But, with our tiny size, its more about expedience and not losing all the time spent spinning up on new technologies. That being said, we're actively switching over to another language for an upcoming product that isn't substantively tied to our existing codebase. So it's a balancing act.On this point, I disagree. Such a business will *sometimes* be stuck in catch-up, but switching to a wholly new language or toolset is *not* required to innovate. Languages and toolsets are merely tools that a good developer keeps readily available in his toolbox. You come up with an idea and then choose the best tools for the job. Sometimes, one particular tool is clearly best for the task, but many times, the pros and cons of different tools result in multiple tools that are roughly equal in utility for completing the task. If any of those tools is one where you already have greater competence, or if using a familiar tool will save you many months or a year in development time, the "best" tool for the task from a business standpoint is *not* necessarily the best tool from a purely technical standpoint. So it's all a matter of ensuring the business is being smart overall.I'm one of the two developers, so I'm very familiar with this issue. We're also very proactive about this. We periodically rewrite large chunks of our framework, evolving it over time, so that number is below 30% for us. However, there are definitely still a few areas that would seriously benefit from a rewrite. Those are the areas we'll likely be hitting the next time we revamp chunks of the codebase. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile    :)"  data-smilie="1"data-shortname=":)" />No problem. As I assumed, you meant well, but the words could have been chosen better. And I don't blame you for being exasperated at the software development industry. I was a developer here in Silicon Valley for 15 years and got fed up with it, so I went freelance for awhile and finally ended up creating my own products.Sounds like an opportunity to share lots of war stories. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile    :)"  data-smilie="1"data-shortname=":)" /></blockquote>

Verification