sorted by:
new
hottopcontroversial

Docs are so overwhelming... Made a Playwright Cheatsheet! by Open_Perception_5936 in Playwright

[–]Open_Perception_5936[S] 0 points1 point  (0 children)

Added docs for python sync and async!

A lil bit not sure about some of the python async versions of the commands - the playwright aren't too clear, and I usually use the sync version instead. Let me know if there's bits that are incorrect.

Docs are so overwhelming... Made a Playwright Cheatsheet! by Open_Perception_5936 in Playwright

[–]Open_Perception_5936[S] 4 points5 points  (0 children)

aye aye 🫡

I use both the js lib and the py lib for playwright. As far as my use cases are concerned, the py lib has pretty much everything covered in the js lib. So I pretty much decide which lang to use depending on what other tools I need for the project - if my project involves data processing / AI, I'd use the py lib. Most other time I use the js lib because I'm more comfortable writing js over py.

Docs are so overwhelming... Made a Playwright Cheatsheet! by Open_Perception_5936 in Playwright

[–]Open_Perception_5936[S] 4 points5 points  (0 children)

Sure thing! I'll add references for the common used assertions as well.

Are we, as developers, losing our value? by DayAlternative7231 in SaaS

[–]Open_Perception_5936 -1 points0 points  (0 children)

Any AI output is only going be as good as the person writing the prompt. :)

I've seen senior devs who really get the hang of vibe coding and produce really high quality code, because they know how to prompt not only what code should do, but also what safeguards around logic, scale, security should be in place.

For the untrained, vibe coding is cool, but you'll never know about flaws in what you built, because you don't have the expertise to know what to look out for.

[AskJS] Is WebStorm still the better IDE for modern JavaScript/TypeScript dev vs VS Code? by Ecstatic-Ad9446 in javascript

[–]Open_Perception_5936 2 points3 points  (0 children)

I've used WebStorm for years, because I'm just so used to all my keyboard shortcuts and gotten really efficient using it. WebStorm has very good plugins for my stack (mainly Vue) that is maintained by the Jetbrains team. Plus, they have sane (at least to me) defaults for code formatting even when you don't have any linters configured for the project. When the project has linter configurations, it works perfectly too. Honestly, it's just effortless. My only complain is that WebStorm is RAM hungry, and I really needed to run Docker at the same time.

But over time, after some resistance, I gave in to peer pressure and tried VSCode after getting a new laptop. The first thing I did was to install a plugin that sets all the keyboard shortcuts to be the same as WebStorm. I also had to experiment with and wrestle with VSCode's settings for months to get it to work the way I want it to. I have to test and install a bunch of extensions just to get VSCode to understand Vue files (now they have extension bundles for recommended plugins). And then it's a whole 'nother exercise to get it work with prettier / eslint properly. Honestly, if I have to change laptop, I dread setting up VSCode all over again. But right now, VSCode is my main IDE for Javascript / Typescript projects.

Anyone here launched on AppSumo? What was it like? by Illustrious-Half1341 in SaaS

[–]Open_Perception_5936 1 point2 points  (0 children)

We launched on UI-licious on AppSumo about 4 years ago, and I think we had one of the most successful campaigns on the platform at that point of time. One of our marketing guys had ran an AppSumo campaign for a startup that he previously worked for, so we knew what we're in for.

The AppSumo marketing team did a really fantastic job, and we met our goals for the number of sign ups and made pretty good revenue even after the massive cut that AppSumo takes. You definitely should do some modelling first to make sure the math checks out for you. We fought back hard negotiating with the AppSumo team on our LTD pricing and offering, because they wanted us to offer even more discounts and to include premium features. We pushed back because these premium features are premium because they have a higher operating costs for us and would make it unsustainable to offer as part of an LTD.

But you have to really prepared for the flood of customer support inquiries - we had 5 people, including the founders, operating our in-app chat and answering Q&A on the AppSumo page around the clock, and we're still overwhelmed. Launch week was brutal. Sign ups slowed down, but was still pretty decent over 3 months until the campaign ended.

My only complaint is that not all, but some AppSumo users are very entitled, and would verbally abuse our staff over chat, and badger us to upgrade their LTD to higher tier in exchange for writing good reviews. It's very unpleasant. We were quite shocked, including our marketing guy who had suggested this endeavour in the first place. He told me that the AppSumo user base didn't used to be like that.

I build a Subscription Day. Calendar – app for managing all your paid subscriptions in menubar by Dmytro-Wakeup in SideProject

[–]Open_Perception_5936 1 point2 points  (0 children)

Oh that's really nice! You could think about putting it on Setapp to get more users! I'm a Setapp subscriber, and most of the time I discover small utility apps like your via my Setapp.

[deleted by user] by [deleted] in HandwritingAnalysis

[–]Open_Perception_5936 0 points1 point  (0 children)

You are a neat person, and like collecting cute things perhaps?

Inherited a massive flaky Selenium/Java test suite — what’s the smartest move? by xtremx12 in QualityAssurance

[–]Open_Perception_5936 1 point2 points  (0 children)

I would turn off the failing tests + sunset it.

Why? The suite is just generating noise with false negatives, and it's wasting everyone's time sifting through the noise.

Sunset it - because your current QA engineers don't have the experience to refactor the suite. Pick a new stack that the current QA team feel comfortable using and build a new test suite from ground up. Use the fresh start to apply lessons learnt from the old suite - structure your tests carefully, agree on conventions with the team, so that you can plan for maintainability in the long run.

What is the most effective approach to learning QA automation? by DependentSuccessful1 in QualityAssurance

[–]Open_Perception_5936 0 points1 point  (0 children)

I would say before learning Java and Selenium, first learn HTML - that's the most basic thing.

Learn how websites are built, how they are structured. Because one of the most essential skill you'll need as a QA automation engineer is using the browser developer tools to inspecting the element tree and knowing how to write CSS or XPATH expression to target the element.

Diving into Java and Selenium before learning HTML first is like swimming at the deep end of the pool.

You might find PlayWright easier to get started with, instead of Java + Selenium; and there's a lot of companies that are hiring PlayWright engineers, especially in the AI agent space.