Hacker Newsnew | past | comments | ask | show | jobs | submit | daniel65464's commentslogin

If you are looking for something that generates selectors for you but also gives you some control and granularity, I made a free chrome extension called automize


Interesting enough I made a chrome extension that does almost exactly what you are describing. It’s called automize and it lets you very quickly generate custom selectors and export the code to puppeteer, playwright, selenium etc. it handles all the verifications as well as provides a handy ui that shows what you are selecting


This is from a stackoverflow post that I found when I was asking the opposite of this question myself:

"I've seen two applications of a well-known commercial Rete rules engine running in production where I work. I'd consider one a success and the other a failure.

The successful application is a decision tree app, consisting of ~10 trees of ~30 branch points each. The rules engine has a UI that does allow business folks to maintain the rules.

The less successful application has ~3000 rules slammed into a rules database. No one has any idea if there are conflicting rules when a new one is added. There is little understanding of the Rete algorithm, and the expertise with the product has left the firm, so it's become a black box that's untouchable and unrefactorable. The deployment cycle is still affected by rules changes - a complete regression test must be done when rules are changed. Memory was an issue, too.

I'd tread lightly. When a rule set is modest in size it's easy to understand changes, like the simplistic e-mail sample given above. Once the number of rules climbs into the hundreds I think you might have a problem.

I'd also worry about a rules engine becoming a singleton bottleneck in your application.

I see nothing wrong with using objects as a way to partition that rules engine space. Embedding behavior in objects that defer to a private rules engine seems okay to me. Problems will hit you when the rules engine requires state that isn't part of its object to fire properly. But that's just another example of design being difficult."

My company is absolutely the second case, and it makes development awful. On top of that because of how complex things have come, business users don't interact with these rules at all, and all the work ends up on the devs.


Great post. You could also use Automize.dev to generate those xpaths easier ;) Disclaimer: I am the author of Automize.


I would be interested in a full integrated workflow demo.


I learned this when I read Outliers by Malcom Gladwell. He talks about why the richest people in history all were born around the same time. This is a direct quote " On a list of the 75 richest people in history, which includes names from Cleopatra to Warren Buffet, an astounding fourteen Americans appear, all of them were born within nine years of each other." "Many familiar names appear on the list, like Andrew Carnegie (born in 1835), J. P. Morgan (born in 1837), and John D. Rockefeller (born in 1839)" He also talks about the tech people such as: Steve Jobs: 1955, Bill Gates: 1955...


I read elsewhere that it could be possible that Nintendo gave him an NDA that said something like "you only need to pay us back what you took (~300k) and if you break this NDA we will come for the full $14 million".


Just today, I tried switching from neovim back to intelij and I found myself quickly switching back because although I consider Jetbrains intelisense much better than Microsoft's tsserver, you just can't beat the customizability of neovim. I use a mostly stock vim configuration but have a few keymaps for things like switching files or plugin remaps and I found it to be very challenging to move it to Intelij. Has anyone made this transition before or have some tips? Lastly this is a bit nitpicky but I saw it mentioned in the article, the themes neovim offers are miles ahead. This is likely just my personal preference, but I could not find a good theme I liked supported by intelij.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: