7 ms·
During my first job after university, I spent a bunch of time developing apps using Lotus Notes. Because all of the company's 2000+ employees already used Lotus
by rahimnathwani 8y ago
During my first job after university, I spent a bunch of time developing apps using Lotus Notes. Because all of the company's 2000+ employees already used Lotus Notes for email and calendering, deploying these apps was easy.
And in many cases I was able to develop the basic functionality of a workflow app whilst I was talking with the main user to gather requirements. And, although the platform supported a proper programming language (LotusScript, with almost the same syntax as VB), I was often able to build what I needed with just the GUI tools and a few formulae (roughly equivalent to formulae in Excel).
There are a lot of Lotus Notes haters. I think the majority were put off by the email experience, which is very different from other systems.
But the ease of developing, deploying, updating and using internal-only workflow applications was truly awesome.
I hope App Maker is as easy to set up, for simple use cases at least.
- mcroft 8y agoI always got the impression that Lotus Notes was a great idea, but very poorly implemented. The concepts in it were good, it was just a shame it inflicted so much suffering.
- wycy 8y agoWhat aspects of Lotus Notes seemed like a good idea? Genuine question. I remember being horrified by almost everything about Lotus Notes. Sametime was great, though.
- slantyyz 8y agoI'll bite... 1 - Document Store (iirc, CouchDB was inspired by Notes/Domino) 2 - Replication - even past the 90s, it was one of the best tools for disconnected users 3 - Low barrier to application creation (it was about as easy as building something in Filemaker Pro) 4 - Easy publication of applications to the web (this was BEFORE 2000, so kind of a big deal back then) 5 - Administration of servers was pretty easy 6 - LotusScript (similar to vba) let you go much further than the prebuilt formula language (if you were willing to learn it) Keep in mind, these benefits were available pre-2000, and in that time many were strong competitive advantages.
- tonyedgecombe 8y agoReplication was huge, we didn't even have an internet connection when I setup a application replicating between three suppliers and a bank.
- slantyyz 8y agoYeah, when I first started to use Notes, using modems over POTS lines to call HQ was still a thing, so that replication was a big deal. Hell, I don't even think all laptops had ethernet ports back then either. In a lot of cases, you had to buy PCMCIA cards for that.
- kirbypineapple 8y agoI realized how great Sametime was after I was forced to move to Skype for Business. The meeting functionality wasn't great but there were other great features. I sorely miss the button that allowed you to drag a rectangle on your screen and it would automatically send the resulting screen capture as a message. Not as an attachment that you had to open up, an actual image in the chat. Why can't skype figure that out!?
- rahimnathwani 8y agoI still wish for a widely-deployed replacement for Notes/Domino. Sure, I can build CRUDish apps with Django, but there are simple use-cases that take me a week with Django, that would have been a day with Notes. It's crazy that things are slower for me 20 years later. I'm pretty sure I'm not dumber now.
- slantyyz 8y agoDoes Filemaker Pro solve that problem?
- rahimnathwani 8y agoI have never used it, but it's no longer available as of last month: http://www.filemaker.com/products/filemaker-pro/ http://www.filemaker.com/products/filemaker-pro/ "FileMaker Pro is no longer available. It has been replaced by FileMaker Pro Advanced which includes more features to help you develop and deploy custom apps faster and more efficiently."
- slantyyz 8y agoIIRC, File Maker Pro Advanced is basically FileMaker Pro with additional features enabled. You would be able to use that in its place, but it might have a higher price tag.
- Drakim 8y agoTools like that can be extremely productive, and easy for people of no or low programming ability to utilize. But just like excel, it's a double edged sword, as people "specialize" in it and create monstrous abomination applications way larger than the tool is fit to sustain. It becomes a rat maze of gotchas and obscure tricks, and nobody but the original creator really knows what's going on.
- tribby 8y ago> nobody but the original creator really knows what's going on. perl devs used to refer to this as job security :)
- panic 8y ago> nobody but the original creator really knows what's going on That’s true of most “serious” codebases too! Writing code that others can understand takes time and expertise (both expensive), and it’s often not worth it for one-off tools.
- oldcynic 8y agoA friend of mine spent a very lucrative few years in the late 90s, early 00s doing Excel contracting. Usually for banks who seemed to have quite a lot of these monstrous abominations and a wish to make them far more monstrous going by conversations back then. Paid for their Porsche 911 until the .com bust broke contracting generally.
- slantyyz 8y ago>> Tools like that can be extremely productive, and easy for people of no or low programming ability to utilize. Absolutely. BUT, in the early days, the value of return for end users is higher than the cost of development and maintenance. If the tool is useful and grows, it's going to flip where the cost of development and maintenance is higher the the return, and some tough decisions need to be made.
- Pamar 8y agoHi, I am the guy that came in a few years later and had to reimplement a bunch of custom (undocumented) Lotus Notes applications in order to move actual documents to a proper document management system (with access profiles and searchability) integrating the apps in an intranet portal, allow them to talk with other applications and finally put everything under SSO. Thank you for the experience.
- wslh 8y agoSpeed vs reliability is a common tradeoff in the workplace. Everyone hates the apps or tools that were built before you start working.
- Pamar 8y agoIn my experience speed vs. reliability soon transmogrifies in inertia vs. rational (and usually inertia wins). I'd like people that create "quick prototypes" and "just a throwaway excel with a few macros" realized that while they are valuably shortening the time to get something usable they are also shortening the time before their thing turns in a sort of albatross tied to the neck of the users.
- prepend 8y agoI find this better than the people who try to build 3-tier sql dB driven apps for all those scenarios. My estimate is that for every 20 “throwaway Excel,” only one becomes used heavily and required a painful redesign. Trying to build all these correct from the start is actually inefficient because 1) you don’t know which 20 is right until quite a while in; 2) the idea that better requirements gathering and design is a myth as functionality and use is frequently, in my experience, new based on the spreadsheet and users don’t tell this to the design team; 3) the cost of properly designing all 20 is enormous so trying to pick only the most likely 5 is still expensive and has a decent probability of producing zero useful systems. So while it sucks to be the engineer cleaning up some yahoo’s hack that got used by the CEO, I’m not sure what the solution is that is best for the enterprise.
- prepend 8y agoI worked for a huge consulting firm that had built a lot of workflows around Lotus. I hated it at the time, but then I moved to an org using Exchange. I asked how to do something simple like send a five question survey by email, allowing editing, and combining results into a dB and was surprised Exchange didn’t have an equivalent. The Exchange people pointed me to the SharePoint people who explained this is an entirely different license and then showed me how to do my survey. It took more development time and somehow had an even worse UI than Lotus. So there is stuff worse than Lotus, and I think that enterprises do need some simple way for non-devs to make modules or apps or whatnot that they can integrate into workflows. Basically like Access was in the early days where normies would make databases for paper stuff. The idea that a non-dev should hire people for simple data collection and analysis, while nice philosophically to me as a dev, is pretty crazy in the long run as it doesn’t scale.
- rahimnathwani 8y agoIf you don't care about confidentiality, then you can do a simple survey using a SharePoint 'List'. It's as easy to set up as a Notes database. But less flexible.
- prepend 8y agoThat’s what my IT people said. SharePoint is harder to use, integrates poorly into outlook, lists are a terrible data source, SharePoint permissions are buggy, and the pricing model is all different than outlook. It’s effectively a whole different platform than exchange and so it’s basically easier to use survey monkey or google forms. But hopefully this gets better with office365.
- fpgaminer 8y agoVery similarly was HyperCard. It was a bit before my time, but reading up on it, it seemed so powerful and yet friendly for non-programmers to use to make useful tools. For a demonstration of HyperCard's power, play the original Myst some time. The original Myst runs on HyperCard (the Mac versions anyway; it obviously had to be ported for Windows and other releases). Incredible. I struggle to think of tools like these that exist today. Access, perhaps? (and of course the tool in the article)