5 ms·
I feel the same way about Access, too. It doesn't matter whether they're "real programming", it matters that they let real people solve real world problems for
by taneq 7y ago
I feel the same way about Access, too. It doesn't matter whether they're "real programming", it matters that they let real people solve real world problems for themselves, who otherwise would have to pay real programmers real money to develop real applications.
- sixdimensional 7y agoCitizen developers in an organization are not a bad thing. But it is important to properly support them, with the right tools and training, but especially when the harder problems need to be addressed by specialists.
- TeMPOraL 7y agoI second the "right training" part. I think any organization working with any kind of data should invest in making all their office employees Excel power users. Wrt. right tools, I think Excel is the right tool. It may lack safety affordances, but it does its job cheaply and efficiently (and you already paid for it since you probably need to open Word documents anyway). As for "harder problems addressed by specialists" part, it happens, but I'd argue not that often. Are they using Excel to half-ass CFD sims of their rocket engine nozzles? Sure, they probably could use a proper software for that. Are they doing their own specific munging of customer or process data? Their workflow is probably too specific and too fluid for it to be shoehorned into a "serious" application without a tremendous loss of productivity.
- mirimir 7y agoYeah, Access got me started learning SQL. And Jet is actually not a bad database engine.
- Someone1234 7y agoHas Access solved the corruption issue that plagued it for tens of years? While you can connect it to a "real" database engine trivially, a common use-case is via a single MDB file that could become damaged. You could damage the MDB a number of ways including: - Leave Access running before shutdown (or power loss) - Intermittent network outage to the file server - Multiple users trying to access the same MDB (or anti-virus scans/locks, even on another user's machine) - JET inconsistent versions / Access inconsistent versions / Patch Levels The biggest headache though with Microsoft Access was never the product itself. It was that the product didn't really have a natural evolution. You'd start with a single MDB/single employee, but one day you'd need two employees or more (and security, and more tables, and this and that), and while you could migrate the MDB into a real database engine ($$$) and use Access as the front end, the record locking was funky and scaled poorly (plus control was limited). The whole product felt a bit like a mouse-trap. A nice shiny piece of cheese, that genuinely tasted good/worked well, but as soon as you tried to move it SNAP. I don't dislike Access, but it was always painful when a business outgrew it (whereas Fortune 500 companies live and die on Excel).
- chaostheory 7y agoAccess and FileMaker made sense before the advent of open source, specifically Rails. Django, Postgresql, and MySQL. Both products make little sense now.
- jacobolus 7y ago> Rails. Django, Postgresql, and MySQL These are much harder for non-programmers to use than Access. With Access, almost completely non-technical people can set up their own database and make the queries they need to answer their own questions. With Postgres accessed from a general-purpose programming language, non-technical people need to hire someone to help them with every basic task. As far as I can tell Access has nothing to do with making websites, so it’s unclear what Django or Rails has to do with anything.
- chaostheory 7y ago> As far as I can tell Access has nothing to do with making websites, so it’s unclear what Django or Rails has to do with anything. You can make apps with Django and Rails. They're not just "websites". Web apps are also still useful even when they're not public facing. > These are much harder for non-programmers to use than Access. With Access, almost completely non-technical people can set up their own database and make the queries they need to answer their own questions. That's the thing. Access and FileMaker aren't typically run by non-technical people. Yes, they aren't initially programmers, but they're usually technical people. FileMaker & Access users, whether they realize it or not, become programmers. I feel that you're confusing Access & FileMaker users with users of Excel. > With Postgres accessed from a general-purpose programming language, non-technical people need to hire someone to help them with every basic task. A relational database is not a big leap from either Access or FileMaker. I know all of this because I used to work closely with a team of these people, and at some points I've even helped maintain their code.
- jacobolus 7y ago> I feel that you're confusing Access & FileMaker users with users of Excel. I know several people who use or used Access / Filemaker who were non-technical with previous experience mostly consisting of Word / light Excel use. For example, my anthropologist parents used Access for analyzing their manually gathered census data for a small rural village. The volunteer docents at a local museum in my hometown used Filemaker for managing the museum collection. > whether they realize it or not, become programmers Using the graphical tool in Access to construct queries does not require becoming a proficient programmer. > A relational database is not a big leap from either Access or FileMaker These are relational databases. They just have user interface affordances intended for non-technical users. Postgres does not.
- sbuttgereit 7y agoI'm in that category of people the regularly have to unwind the web of Excel or deconstruct the Access databases that grow to rival SAP in terms of intricacy... ... I actually agree with the overall premise that these tools do let non-tech types do real work and I think department power user types should have these things. But we must also recognize that these tools are a bit like a black hole, too. Not unlike many applications created by professional developers, these users will tend to continually add features and bells and whistles until they pass the event horizon that exists between good judgement and bending these tools to be what they aren't (the most common is turning Excel into a database). On one side of that horizon you can pull back and reasonably find better technology to implement sophisticated capabilities and on the other you start to reduce efficiency as results as the errors and issues with the misuse of these systems overwhelming the benefits. Worst part is... you never really know when you've passed through that horizon... until you're spaghettified that is... So in-house technologists need to be aware of these things and give good support, and then also provide the technical judgement on when these approaches start to break.
- davedx 7y agoThis is a good take. I once build a Rails app that translated a giant Google Sheets document into a web application. What I found really fascinating was that: 95% of my development time was spent building CRUD, access control, UI that was already more-or-less provided for free in Sheets 5% of my development time was spent writing unit tests and services that implemented the actual logic and formulae in the spreadsheet. Even though this was the tricky, business critical "thinking carefully" part, it was also the least time consuming. It just goes to show, even compared with Rails, applications like Excel and Sheets give you a LOT for free, out of the box, accessible to everyone.