6

Best:
- I built a good automation mechanism with a decent UI [slackbot]
- used as few frameworks and ext libs as I could. Mostly based on bare java
- client wanted to migrate it to Spring
- got 3 peeps assigned for the migration
- 2 months later their effort failed.
- win: my project has not been molested with Spring

Worst:
- i had an idea to develop smth on top of jmeter, using jmeter as a lib
- I downloaded and imported jmeter's src code
- static contexts, singletons, jmx/rmi everywhere [java is deprecating rmi support]
- not gonna happen... Not gonna build a new project on top of a legacy codebase.

Comments
  • 3
    Slack apps are always more effort than they’re worth
  • 2
    @wackOverflow not really, no. Especially if they save us from several days of manual work per week. Yes, days.
  • 1
    Ressiiiiist le-ga-cyyyy
  • 2
    @netikras must just be the ones I’ve made then lol
  • 1
    @wackOverflow maybe :) although slack api is not that bad rly. A websocket client in a reconnecting loop. Every event msg from slack must be immediately ack'ed, and processed afterwards. Any replies to slack are to be made via another api calls [restful this time], and are quite intuitive. Limits are somewhat annoying though, but nothing that can't be worked around.
Add Comment