I 💗 WEBCON BPS series: Conclusion
LinkedIn Post I 💗 WEBCON BPS: Speed is not enough
Carousel
Speed is not enough
Mike Fitzmaurice said once1
The demand for applications in today’s business world is unprecedented, but:
- Quality cannot be compromised for speed.
- It’s not enough to build applications quickly and easily.
- Our platform supports the entire application lifecycle
- They need to be enterprise-grade, which means more than just scalability.
- It allows you to deliver future-proof apps that grow and evolve along with your company.”
Is this just marketing talk2, or is it real?
This is a question one can answer only for oneself, but my posts may provide insides for such a decision. In the past six month I’ve shared 16 reasons why I still love implementing applications with WEBCON BPS, even so I’m using it for more than five years. Below you find an overview which of my posts contribute to which topic.
Quality cannot be compromised for speed:
- Part 05: Greatly reduced testing time
- Part 07: Gather debugging information
- Part 08: Being CEO for a day (working on behalf)
- Part 09: I no longer hear “Who send these test mails?”
- Part 10: Yes, remove this … AARRRGH (Dependency tracking)
- Part 15: If you repeat yourself, you are doing it wrong
Building applications quickly:
- Part 01: 99% Low-code/no-code implementation 1% high code
- Part 02: Leveraging benefits aka early go-live in < 2 month
- Part 04: Change request there’s a typo
- Part 05: Greatly reduced testing time
- Part 06: Time to market
- Part 15: If you repeat yourself, you are doing it wrong
Application Lifecycle:
- Part 02: Leveraging benefits aka early go-live in < 2 month
- Part 03: Transporting applications Dev->Test->Prod
- Part 04: Change request there’s a typo
- Part 11: From OnPrem to SaaS and back? Without migration effort? 🤣
- Part 14: Multilanguage and evergreen documentation
Enterprise-grade applications that evolve with your company:
- Part 08: Being CEO for a day (working on behalf)
- Part 11: From OnPrem to SaaS and back? Without migration effort? 🤣
- Part 12: Same process, multiple subsidiaries but different data sources?
- Part 13: Ever evolving
- Part 14: Multilanguage and evergreen documentation
- Part 16: In numbers I trust
Series
| Part | Title | Blog | |
|---|---|---|---|
| 01 | 99% Low-code/no-code implementation 1% high code | Blog | |
| 02 | Leveraging benefits aka early go-live in < 2 month | Blog | |
| 03 | Transporting applications Dev->Test->Prod | Blog | |
| 04 | Change request there’s a typo | Blog | |
| 05 | Greatly reduced testing time | Blog | |
| 06 | Time to market | Blog | |
| 07 | Gather debugging information | Blog | |
| 08 | Being CEO for a day (working on behalf) | Blog | |
| 09 | I no longer hear “Who send these test mails?” | Blog | |
| 10 | Yes, remove this … AARRRGH (Dependency tracking) | Blog | |
| 11 | From OnPrem to SaaS and back? Without migration effort? 🤣 | Blog | |
| 12 | Same process, multiple subsidiaries but different data sources? | Blog | |
| 13 | Ever evolving | Blog | |
| 14 | Multilanguage and evergreen documentation | Blog | |
| 15 | If you repeat yourself, you are doing it wrong | Blog | |
| 16 | In numbers I trust | Blog |
Comments