I'm actually the person who wrote this. To be honest, I did write this for some content marketing in mind and didn't expect it to blow up here. But I literally did not use Chat-GPT...not sure what that says about my writing or how good GPT is lol
Fair. I suspect what it means is that in the future there will be no reason for anything but an AI to write "content marketing", because it all reads like AI's anyway, and has about as much originality.
Examples of horizontal tools could be something like a Scheduling App, a CRM, or even a Spreadsheet with the idea being that these tools could be used in all verticals/industries. The idea being that someone in healthcare and someone in tech could both use the tool, albeit a little differently. To bring it full circle, because the end user can be so different, it makes onboarding horizontal products really difficult.
With the tech drawdown, been seeing more and more analysis on if software and tech has really increased productivity in the US. Anecdotally, it seems obvious that software has made our work way easier, but perhaps we are not doing anything "productive" with the time we've saved?
I am considering it. I have a fiduciary duty to try to fetch a fair value for the assets, but if no one wants the codebase, I'd consider opening it up. Still TBD as I just announced this a couple days ago :)
That makes sense. I was mainly wondering for old/past companies that don't end up selling their code base versus for Friday specifically. But maybe thats the answer, most companies end up selling their codebase and it does get reused. Good luck on everything!
I’m a huge advocate of this, and have seen it play out well with the Linux Foundation and Mapzen. In this case, their employees seemed to be very thoughtful about how their projects could live on and be useful beyond the company lifecycle.
Aside from the code getting a license and legal audit, finding a trademark sponsor was important to them too so that someone doesn’t come along and re-commercialize their free and open work under the old brand.
On the flip side, this process is a lot of extra work to do in a very busy and risky time for a buisness. Efforts to open source may fail and I understand when people in charge choose to spend their time prioritizing their employee’s needs first, technology second. I can understand why the open source priority isn’t practical if the company doesn’t plan for this possibility ahead of time.
for open sourcing you have to be careful about licenses.
As long as you are not "distributing" it is absolutely fine to mix GPLv2, Apache License and proprietary code you got from some vendor all together. But as soon as you distribute this, it becomes messy.
And then come all the question on technical integrations, ego ("ugly code!!"), ...
Basically I found an interesting article found here( https://news.ycombinator.com/item?id=25043741) and summarized some key points from the comments while adding my own ideas.