This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (13)
- # asami (9)
- # aws (1)
- # aws-lambda (1)
- # babashka (37)
- # beginners (70)
- # calva (19)
- # cider (23)
- # clara (10)
- # clj-kondo (15)
- # cljdoc (14)
- # clojure (3)
- # clojure-bay-area (1)
- # clojure-europe (40)
- # clojure-nl (3)
- # clojure-serbia (1)
- # clojure-uk (31)
- # clojuredesign-podcast (1)
- # clojurescript (9)
- # community-development (7)
- # crux (7)
- # data-oriented-programming (1)
- # datomic (44)
- # emacs (13)
- # figwheel-main (14)
- # fulcro (6)
- # jobs (6)
- # malli (15)
- # meander (7)
- # off-topic (74)
- # other-languages (1)
- # pathom (3)
- # portal (3)
- # re-frame (25)
- # reagent (6)
- # reitit (2)
- # reveal (1)
- # rewrite-clj (6)
- # ring (4)
- # shadow-cljs (11)
- # specter (7)
it is merely a very happy coincidence that allows me to trivially remember the ticket number
I've learned of the awful world of Atlassian. Weve started using it for OpsGenie. Just trying to navigate their site and logins and stuff makes me want to throw the computer out the window.
When did everything become so bad? Computers nowadays feel like devices to slowly kill you via death by a thousand cuts, everything is slow, buggy or just outright broken. Nothing is documented, nothing works and it's so all bloody frustrating. When did this become acceptable! I should go live in the woods:confused:
I don't understand it. Atlassian are a hugely valuable company yet the stuff they make is complete garbage. I just can't understand how enough people used this crap and thought it was acceptable that the company ended up being successful.
what I would love in similar software is good APIs so that I can for example do my own cli or simplified frontend without having to use their UI messes
yeah, i've been trying to interact with the opsgenie api for a few days. The documentation is absolutely terrible
I have a small POC of a dashboard for JIRA.. I gave up doing that because I ended up reimplementing their UI, it is just too inflexible.
I want to check if an alert was created, i get 3 fields back: IsSuccess: true/false Success: true/false State: "Alarm was created" (but could be other strings...) WTF! I want to know 1 piece of information, but this is conveyed through 2 bools and a string...
These systems are incredibly configurable, and they must get suggestions for enhancements from dozens of heavy users. Part of what you are seeing might be a poorly configured instance of JIRA. Part of it is probably the accretion of features without saying "no" often enough for a dozen years of the lifetime of a popular product.
When you see a snapshot of the end result of such a long process, it often looks like a mess. If you saw each individual decision as it was made, each one of them might look much more reasonable than the final system does.
Usually Atlassian say no - and your option is to buy an addon from the marketplace
It can be hard to say no to feature additions, especially from large customers paying you a lot of money.
And if the addon gets commercial success then then they will consider adding it
OK, so you probably have a lot more experience with JIRA in particular than I do. So if you buy 3 add-ons developed by different teams, there is probably absolutely no guarantee that they will be smoothly integrated with each other?
https://jira.atlassian.com/browse/JSDCLOUD-4082 here is one example of a feature that they haven't implemented since 2016
I mean, yeah they might have lots of features but there's just no excuse for garbage like this:
We use the cloud stuff at work and it’s slow, and clunky in terms of the UI/UX. I got selected for a random user survey via Zoom last year and some of the stuff I showed them as being broken, the Atlassian person didn’t even know about — and I will say almost everything I raised during that call has since been fixed so I’ll give them props for that.
But when a software product is popular with (enterprise) companies, it usually ends up with a giant mass of options and features and flags and configuration — and there are often combinations that don’t quite work properly — because they’re getting pulled in every direction, and those corporate purse strings are pulling strongly.
So I sympathize with their position (I worked at Macromedia/Adobe so I’ve been on the other side of the “corporate user” fence) but, yeah, it does tend to lead to bloat and a sub-par UX for “more discerning” users.
For us, the fully-integrated nature of JIRA/BitBucket, connected to Slack, and with “good enough” integration into VS Code makes it worth it overall (but it’s a bunch of trade offs).
It’s the same reason we’re an Office 365 shop: for the price, we get a decent bundle of integrated services that, across the whole company, serve enough people “well enough”.
They can't possibly have to deal with the mass of garbage that most devs have to deal with nowadays, poorly documented open source crap that half the times doesn't work, crap like Atlassian etc.
To be fair, at least a lot of this corporate “crap-ware” has plenty of documentation most of the time. A lot of OSS projects have much worse documentation.
I was on a call with someone from MS tech support for one of teh Azure services we use. The service just randomly keeps... stopping... Just stops... And we have to go into the portal and reset it... I was on the phone with him for a while and he forgot he was sharing his screen. He started googling my issue and he ended up on stack overflow!
Most large companies’ tech support is aimed at the vast majority of their less technical users — the ones who have no chance of figuring stuff out. You’re an “above-average” user.
The other thing that happened was I was using cosmosdb and it suddenly stopped working on new years eve
Got got in touch and they actually hooked me up with one of the engineers writing CosmosDB
And he was super kind and understanding, but his solution was to try to help me change our Backend
I had an issue with my Surface Laptop 3 that involved the CPU overheating and getting throttled after a firmware update. I spent a week going back and forth with MS tech support trying to convince them it was a firmware bug — similar to the one that had surfaced eighteen months earlier (that took them six months to fix). He wanted me to do all sorts of reinstallation and reformatting — and would not budge from his insistence that I stop using Insider builds… a few weeks later, there was a new firmware update and — guess what? — it fixed the problem!
we experimented with cosmo db a couple of years ago, we didn't think it was production ready yet
But speaking of Azure, we run RabbitMQ via CloudAMQP hosted in Azure. One day it went down for about 40 minutes, which isa LONG time for us. Here was the email exchange with CloudAMQP CloudAMQP: "Azure preformed maintenance on your instance, involving a restart" Me: "And it took 40 minutes?" CloudAMQP: "Yes, it started at 13:49:30 and was reported finished at 14:27:02" Me: "Any reason why it took 40 minutes?" CloudAMQP: "I was migrated to a new underlying host which is why it took some extra time. I can't find anything else in the logs." Me: "40 mins is quite a lot of down time." CloudAMQP: "That's why we don't recommend Azure. AWS will notify about two week ahead of scheduled maintenance, and you can manually reboot the instance before that, and GCP can even live migrate VMs between physical hosts causing 0 downtime during maintenance. Azure does neither." Great! MS just decided to upgrade something without telling us, and knocked out instance out for 40 minutes!
Well you are not entitled to an SLA unless you use an availability set with the machines in different update and fault domains
What Sean mentioned is definitely the case with Azure - they outsource most support to organizations who do not have any special training or access to help you, they have access to the same docs you can get from searching the web
A better channel for Azure might be to call your Presales/Evangelist/etc. and they might be able to give you a pointer or reach out to the product guys
What you see on GitHub, Stackoverflow and their doc sites is all the documentation there is
And even thought it looks like community docs it is mostly written by MS employees.. kinda like the Chinese volunteers in Korea..
FWIW, AWS instances can — and do — randomly lock up completely and become unrecoverable and you have to build and deploy a new instance. Cloud services all tend to be like that.
Yup, we have ~200 ec2 instances and we see some kind of failure around once a week... VMs just stop responding, ephemeral drives bite the dust, network partitions, etc. It's normal and unsurprising that once you get beyond small scale you start to see some cracks.
Couple thoughts here, I've had good experience with AWS support. I've found what seems like bugs (500 exceptions), and support have been able to give technical answers about areas that aren't supported that we're hitting. We've also had performance issues with RDS dbs in prod with AWS, and support were able to diagnose the issue down to the host node the DB was on.
EC2 instances definitely fail, go offline, etc. The AWS argument is that this is perfectly normal in any cloud environment, and you should be using load balancers etc. to cope with that. I'm surprised the rate is as high as 1/200/weekly though. I've not run at that kind of scale before though. I did have a non-HA Datomic DB go down on me once though as a result of an EC2 lock up :)
I also was forced to use Atlassian products in some of my jobs. Every time, the excuse is the same: "it's just poorly configured...". So I call it a downright lie - their products are bad, and people use the "configuration card" to reason about
I mean, bitbucket didn't allow me to create a pull request if the branch changed when I opened the page, and also lost all approving status when the branch is updated; its UI is inconsistent, sometimes it does syntax highlight, others don't.
It also sometimes will allow me to start two comments, and other times it'll close the others without telling me.
Jira is worse - create a card, task, subttask, and story were ALL in different places (context menu, submenu, other screens, etc).
There's at least one interesting review,
I would marry this if it was allowed and I wasn't already married
Found this to be an interesting option. Been using Miro lately to organize loose thoughts before putting more structured ideas into my zettelkasten, but this might be a bit more natural. We’ll see!