honey-badger

5 ms·

1.
What AI First Engineering Orgs Look Like(arpitbhayani.me)
2 points by honey-badger 2mo ago|1 comments
2.
The Courage to Criticise(anupam.de)
1 points by honey-badger 8mo ago|0 comments
3.
The Siren Song of LLMs(anukrit.de)
3 points by honey-badger 1y ago|0 comments
4.
Big Store and Small Store(anupamobserved.com)
1 points by honey-badger 4y ago|0 comments
5.
WeAreDevelopers 2022 – My 3 highlights(anupam.de)
1 points by honey-badger 4y ago|0 comments
6.
Should you read The Unicorn Project?(anupam.de)
3 points by honey-badger 4y ago|0 comments
7.
by honey-badger 5y ago
Quality Acceleration is brilliant! I love it. >In this case, I wouldn't say you absolutely need a full quality team, but having some folks whose primary focus is testing and test automation to help skill up your dev teams sounds rea
8.
by honey-badger 5y ago
A valuable perspective, and brilliantly articulated. The process of software creation and its quality assurance is so intricately intertwined due to the nature of software itself, that it is near impossible to neatly divide labour.
9.
by honey-badger 5y ago
Great perspective. Now if you were to take the place of Management and tell this exact story, how would it sound?
10.
by honey-badger 5y ago
Not necessarily. In all likelihood, the market punishes bad software quality, but with a longer and more complicated feedback loop. It is easy to see the increased traction due to building new features. It is difficult to understand the slo
11.
by honey-badger 5y ago
Your comment is super helpful! A few months back, we went from scenario 2 to scenario 1, and I can attest to it being substantially better.
12.
by honey-badger 5y ago
Does the QA team comprise domain experts? What is your domain?
13.
by honey-badger 5y ago
QA Engineer here. We don't have a centralized QA department, but we do have a dedicated engineer who is responsible for QA that is integrated within the development team. Before I joined my team, it didn't have a dedicated QA memb
14.
by honey-badger 5y ago
That is interesting! It rings true, but I never looked at it that way.
15.
by honey-badger 5y ago
Well, the truth is that developers often underestimate how hard it is for non-developers to write scripts. The reason why they don't understand why something like RPA exists is also known as 'The curse of knowledge'.
16.
by honey-badger 5y ago
It's also a marketing problem. You need a solution that appears sexy to the worker, the boss and a champion high enough in the organization to overrule outdated IT policy. I think RPA exists because every organization is plagued by peo
17.
by honey-badger 5y ago
Precisely. In some narrowly defined scenarios where data migration is otherwise like untangling a giant ball of yarn, RPA serves an invaluable need. However, the manner in which it is marketed is out of proportion to the narrower scope in w
18.
by honey-badger 5y ago
Damn! You are like the bystander who gets taken out during a gang raid in your neighbourhood.
19.
by honey-badger 5y ago
Author here. I agree entirely with what you say here. But consider this. I once automated an RPA process to create service records for the customer service department. I did this by automating over a Java based UI app, with reliable selecto
20.
by honey-badger 5y ago
It's a terrible name that has unfortunately stuck. Deliberate obfuscation.
21.
by honey-badger 5y ago
All hail Stefan! Apart from a prolific and generous developer, he's a great human being too. He has turned into a good friend. As for low-code and no-code, I understand your aversion. Those solutions aren't for somebody like you :
22.
by honey-badger 5y ago
Spot-on! From the beginning, I have hated the term 'RPA'. It reeks of deliberate obfuscation, like putting a shiny package around a used sock. PS: I checked out Axiom yesterday and am excited to see the problem you're solving
23.
by honey-badger 5y ago
What you say here is partly correct. To your list of reasons, I would add 3) The existence of business problems that are valuable in their own right, but not compelling enough for regular developers in the firm to care about
24.
by honey-badger 5y ago
Amen! RPA is also about democritizing IT by handing (ideally) every white-collar worker the ability to write scripts that can automate pieces of their daily-work. Of course, those solutions aren't likely to be elegant and their code wo
25.
by honey-badger 5y ago
All your observations are spot-on. Kudos! You have understood this space much better than most software developers ever will :) And yes - the exhortation in my article was essentially for RPA developers to max out on the use of the text-bas
26.
by honey-badger 5y ago
That is a symptom of hype. In the long run, this will change due to commoditization, as I point out in the article.
27.
by honey-badger 5y ago
Author here. In an ideal firm, where data is handled responsibly, you would not need RPA at all. In large organizations though, data tends to accumulate in monolithic islands that are only exposed to each other with legacy UI based applicat
28.
My biggest mistake as an RPA developer(anupam.de)
82 points by honey-badger 5y ago|71 comments