Ragic – Editable forms with relational data(ragic.com) |
Ragic – Editable forms with relational data(ragic.com) |
I tried Ragic just now for 10-15 minutes and it is far from simple, like their landing page claims. It is nothing at all like a database and it also is nothing at all like a spreadsheet (and not in a good way).
Edit: Looking at previous discussions about it here on HN, the criticism in this 5 year old comment all still holds true: https://news.ycombinator.com/item?id=3960207
http://www.alphasheets.com/ is still mostly in stealth (as far as I can tell) but they let you mix and match SQL, Python, R, and Excel formulae in a spreadsheet.
Airtable seems pretty polished (https://airtable.com/).
Both of these are definitely spreadsheets, though. Not sure if you're looking for something more specialized for a certain vertical or problem domain.
Due to piss poor project managers and lack of business requirements and/or realistic deadlines.
For example, let's say a team is given 4 projects. They provide rough effort estimates and schedule those projects on the calendar, with normal buffer for support issues, changes, etc. Then a new ultra-high-priority, life-of-the-company-at-stake project comes down from the CEO, and everything else gets pushed back by months.
So, are those original 4 projects technically late? By many studies' definitions, they would be categorized late.
Furthermore, does it matter if they are late? If you're late on 80% of your projects but deliver on time for 100% of your critical projects, is that so bad?
Not having the demo ready for the tradeshow is a real problem. Not having the compliance changes in by the deadline is a real problem. Not having the integration upgrade done before your partner turns off the old version is a real problem. And so on. Missing some date that was arbitrarily chosen, probably months or years ago, eh, that doesn't necessarily bother me.
I'm not arguing that it's good to be late. It's obviously better for projects to be delivered when expected to let businesses make projections, plan, etc. I'm just saying the real world is messy and full of tradeoffs. If you're constantly reacting to fires and unexpectedly missing deadlines, that's a sign that better project management is needed. However, if you're working with business stakeholders to reprioritize efforts and adapt to changing realities, that can be good in my opinion – even though externally it can appear that projects are "late".
Edit: To be clear, I'm not really agreeing or disagreeing with parent's comment on the source of lateness. I'm commenting on using stats like these as evidence that something is broken in software development.
https://mobile.twitter.com/patrickc/status/51568968982347366...
2) There is no perpetual license to worry about, only pay as long as you need your data.
3) Access allowed business people to muddle through creating database that IT hated to have to maintain... this is obviously different.
They need to redirect any http to https for the sign-up page; they already do this for the login page.
-- [1] http://oppsdaily.com/ [2] https://nugget.one/daily
But the row limits are too low for many obvious uses. I assume this is for technical reasons? Otherwise it doesn't make much sense that if you pay for 20 users to share a database you get the same number of rows as if you pay for two.
1) Being able to link tables in different bases https://community.airtable.com/t/link-to-other-base/107/112
2) Being able to create linked records from form view
1) Foreign keys to users (for e.g. "assigned to", "team members")
2) Better programmability - right now, anything moderately complex requires a bunch of intermediate column (that then have to be hidden from all views). Objective spreadsheets (MIT SAIL) seems like something to aim for.
3) Programmatic (API) access to row history - at least read, for reports