I appreciate from your POV this probably is silly but for us it’s very helpful to have explicit clarity since investors are questioning and demand certainty. I once had to rewrite https handshakes because a lawyer thought export compliance laws would be violated, so hopefully you understand my trepidation :-)
So this is a very relevant question and I have been trying to figure out if I need to migrate off timescaledb asap coincidentally over the last 2 weeks (We're pre-production anyway, so it's the time to do so!). Doing so has been super low priority, but since you're here .... :)
If I have a table that records timeseries data and then another table that has a customer-provided extensible set of metadata where a customer can define columns and other related tabular data, would that violate the license? The customer doesn't have a direct, like, psql level of access but the API intentionally provides a very similar level of interaction.
Does this qualify as providing Data Definition Interfaces? If none of those additional columns and such appear on tables set up as timescale tables does that make any difference?
We looked at it and there were a few problems we had with where it would force us to put VMs that we just weren't super comfortable with due to the in-process-ness.
More a byproduct of decisions made 5 - 7 years ago when the company was in raw startup mode versus a more mature roadmap.
Honestly with the schema thing I'd probably be fine with either/or!
A checksum would be crude and user-hostile, only being able to say "you did it wrong" but not really good at tell you what it means to do it right.
If I understand the concepts correctly then it seems like a shared ontology could potentially solve the problem in a non-hostile way.
Plus, it makes me happy because I feel like types are a real-world problem, so it is always nice if the type system could enforce that real-world-ness and all the messiness that comes along for the ride.
Yeah - I used to lead a department that would process somewhere around 10TB of CSV formatted data per day.
The edge cases are a hassle but they don't become less of a hassle from a business perspective by switching to json or really any other format. We tried an experiment of using more json and eventually gave it up because it wasn't saving any time at a holistic level because the "data schema" conversations massively dominated the entirety of the development and testing time.
Obviously being able to jam out some json helped quite a bit initially, but then on the QA side we started to run in to problems with tooling not really being designed to handle massive json files. Basically, when something was invalid (such as the first time we encountered an invalid quote) it was not enjoyable to figure out where that was in a 15GB file.
That said, I fully concur with the general premise that CSV doesn't let you encode the solutions to these problems, which really really sucks. But, to solve that, we would output to a more columnar storage format like Parquet or something. This would let us fully encode and manage the data how we wanted while letting our clients continue working their processes.
What I would really like to see is a file format where the validity of the file could be established by only using the header. E.g. I could validate that all the values in a specific column were integers without having to read them all.
On the flip side, the only time I've ever felt like my work was fulfilling and valuable was when was under-compensated and insanely overworked (like 80 hours was a pretty reasonable work week).
The "Tiny town" is 70,000 people who live in an multi-city metro area of around 600,000. That may not be like SF or NYC big, but it's also not just a random metro area. Having lived there for a few years, you're painting with a poetic brush a bit and I'd like to clarify how I see it.
Walmart owns Bentonville. The city council, mayor, and basically anyone there is almost completely subservient to their interests. Again - WM never moved in to the small community, the small community literally is Wal-mart.
For many years, people in the town worked in Wal-mart retail buildings & warehouses around Bentonville. Around 2013 the company started to struggle to compete and found that they needed to attract talent, so the Walton Family Foundation started spending somewhere around $300 million - $400 million a year in improvements and restoration projects. This included massive subsidies for companies that moved in to the area - WFF also paid partially or fully relocation money, but I have no idea how much they paid other than one restaurant owner I spoke to who was basically given moving costs, a building, and "free" rent for a year.
The whole "Wal-mart HQ" thing is just another in their line of tactics to attract new talent in to the area because they are struggling to build an ecosystem of talented developers and analysts. Which, again, there's nothing wrong with this tactic if that's what you're hunting for.
One thing I'll give WM for sure - they are 100% focused on building out a tech bubble for people who want a semi-urban lifestyle. There's a lot of TX & CA transplants and honestly it's working great for them.
All told, none of this is even kind of comparable to Amazon moving to NYC or Atlanta. Nor is it comparable to a company moving in to a small town brand-new.
I've worked with several recruiters who are trying to shop around as an outsourced recruiter. Basically, they take your resume and slap their name on it in an effort to show companies "You should use me because I provide well-qualified talent."
If you're not going through internal recruitment then this is a great way to go about it. The recruiter isn't just trying to get their 20%, so they spend a lot more time getting to know you and also getting to know where you're going.
The biggest down side is that you'll never hear a negative word about anything, so you gotta be good at asking some pointed questions.
I appreciate from your POV this probably is silly but for us it’s very helpful to have explicit clarity since investors are questioning and demand certainty. I once had to rewrite https handshakes because a lawyer thought export compliance laws would be violated, so hopefully you understand my trepidation :-)