1,861 karma · joined February 1, 2013
Access (and to a lesser extent, Excel) empower anyone to model their data and manipulate it without asking permission. The problem is they don’t scale well, there are no backups, they don’t show up in a data catalog anywhere, no integration with enterprise SSO, etc. They do benefit from file-focused solutions for these issues (eg the Access file lives on a network drive which is backed up) but they fall far short from what you expect from a production database.
So my challenge is: how can I let anyone in my organization create a new database, with all the backup/authentication/discovery/scalability out of the box, for them to connect to Retool?
https://techcrunch.com/2019/09/27/to-curb-lobbying-power-eli...
OTA isn’t a panacea though. You have to figure out ways to make it financially reasonable for people to blow the whistle on massive firms. The Waste, Fraud and Abuse laws might be a good template.
This 1000%. Working with text on iOS is such a pain now.
You might want to contact an employment attorney in your state for a consultation. Your state Bar association can give you a referral and probably a free consultation. They will be particularly interested if this was the culmination of a pattern of bullying behavior (consequences vary by State) or if there’s some kind of protected class involved (eg you are over 40 and the manager wants a younger team).
It might seem like an unnecessary hassle, but legal action can help your remaining colleagues and possibly put some money in your pocket.
> Federally funded research and development centers (FFRDCs) are public-private partnerships which conduct research for the United States Government. They are administered in accordance with U.S. Code of Federal Regulations, Title 48, Part 35, Section 35.017 by universities and corporations. There are currently 42 recognized FFRDCs that are sponsored by the U.S. government.
https://en.wikipedia.org/wiki/Federally_funded_research_and_...
FFRDCs have a special legal ability to provide “neutral” input on technical matters. In theory Congress could hire Mitre or other FFRDCs to perform this service for them. That might take some tweaks to the law because FFRDC contracts seem to be aligned to specific executive agencies.
Personally, I’m a big believer in Federal in-sourcing combined with civil service reform. Using contractors for public interest positions, even contractors with special designations like FFRDCs, clouds the issue with contract management.
Of course, it’d be very difficult to design Civil Service reform properly and politically impossible to implement it, so creative contracting is probably the way to go for now.
It stalled for many many reasons, including:
- XML is kind of awful
- Over-general solution without clear advantages for a specific use case
- Mis-aligned incentives
- easy to abuse open query capabilities
- Hard to use for both data publishers and consumers
I think that JSON Schema with incremental enhancement via JSON-LD is a more promising tech stack for another try. That would let you take advantage of the massive investments in the current API ecosystem while carrying forward the best parts of the old Semantic Web Effort.
Of course the incentives are still hard to sort out. Commercial entities WANT lock-in. They will Embrace/Extend/Extinguish anything they can because they need a moat to make money. Honestly anti-trust regulations might be needed.
I think it’s a shame, it’s a lovely concept. The Capability-based security alone is game-changing.
Details here: https://sandstorm.io/news/2018-08-27-discontinuing-free-plan
Christ nobody wants to live in 1935-1945. That period set the All-time record for violent death
https://www.vox.com/2015/6/23/8832311/war-casualties-600-yea...
Asciidoc definitely seemed like the best option. The biggest thing for me was the ability to do complex numbered headers.
Unfortunately the tooling wasn’t really good enough for my use case. I needed a clean way to move between Asciidoc and Word, and it wasn’t really possible. Pandoc claimed support for both Asciidoc and word, but it was only partial and couldn’t round-Trip the document. I considered developing & contributing the functionality, but I didn’t know the language the tool was written in and couldn’t justify investing more time in the experiment.
Maybe it’s time to review the tooling situation and take another crack at it...
FTL was just confusing, hopeless death for me.
Relevant XKCD: https://www.xkcd.com/1053/
Paul’s blog posts on the subject are useful background: http://paulgraham.com/lisp.html
You should probably start with this one: http://paulgraham.com/avg.html