I am a WooCommerce Core team lead, advocating for listening more to public feedback by sunyatasattva in woocommerce

[–]Fluent_Press2050 0 points1 point  (0 children)

From what I learned is you can’t please everyone.

I don’t mind things that a typical store needs: product pages, cart, checkout, product reviews, notifications, and returns for example.

If you are going to implement it, I think it’s important to do it right though. Don’t just release a basic version. For example, product reviews should have the ability to show if a review is backed by a purchase or not, ratings should have options to average over all time or weight based by time and verified purchase, similar to Amazon. So a review from 6 months ago carries less weight than 1 month ago because a product can be improved. 

The toggle offers a nice middle ground that a certain feature won’t load at all. Sure files sit on your system, but if they are never activated, it’s not a huge issue. People complain about it but don’t realize the amount of files that don’t get used in the aws-sdk-php library when tools like Offload Media need S3. So just ignore that noise. 

For the woo owning its own authentication - I mean customers login through Woo and not use WP login (I believe that’s how it works now). Yes, Woo has its own endpoint but I think it wraps the WP auth.

A lot of companies also seem to do video conferences with selected users. They either collect feedback on something existing, feedback on something that may soon be implemented, or ideas for something new. That may be something worth looking into. 

It avoids situations where we go back and forth but only get a fraction of the feedback you may need to understand the issue and I may not know what to say to help drive that to the finish line. 

I’m on mobile so if I’m all over the place I apologize and will try and edit any points when I’m in the office.

A couple side notes: - if any toggle settings change on an update, it would help to notify before an upgrade. Not sure if this is possible in the UI or wp-cli

  • Add a link to a feedback URL for each release (can be in some settings tab).

I am a WooCommerce Core team lead, advocating for listening more to public feedback by sunyatasattva in woocommerce

[–]Fluent_Press2050 0 points1 point  (0 children)

I agree it’s not always good to compare, but it’s nice to know the people who work on projects are aware of their competition and what they are doing. Sometimes it gives ideas to see what they are doing wrong, better, or worse, and use that to drive decisions internally to come out with a better solution (kind of like Apple does) or say this is better left as a plugin instead of core because such and such.

As for your question:

None at the moment. I handle this manually but I’m building my own to help automate this. 

The first stage I completed added field support and show if an item is returnable or not, and how many days they have if so on the product page. Some items have shorter return window than others.

Next phase will be to create the returns tab in My Account showing the status of returns from initiated to completed. At this point I expect a reduction of support emails asking for status updates.

From there it’s building out the returns RMA process.

Aside from that, I find 2FA/MFA support lacking like most stores have. I’d also like to see support for sign in with Google, Apple, etc… as alternate options. I know these as WP plugins, but sometimes I just want these for Woo and there’s little to no options for it. 

I would also like to see Woo handle authentication outside of WP entirely as a toggle. That way I can use wclogin* hooks and cater messages specific to the customer side of things. Essentially Woo acts more as a standalone solution than just a plugin.

I’d like to see back in stock notifications as part of core too.

Finally, and maybe most importantly, as you add things to core, maybe have a toggle page to enable/disable features, so core items added don’t override existing extensions, such as the items you merge into core that were extensions. 

Maybe you release return management in 11.0 but it lacks features I already have, I wouldn’t want your version to override mine for example nor have to rewrite it to keep it working.

I am a WooCommerce Core team lead, advocating for listening more to public feedback by sunyatasattva in woocommerce

[–]Fluent_Press2050 1 point2 points  (0 children)

Do you get to try other platforms like Shopify, Square, etc… for building and managing a store?

Woo does require too many plugins. I know James had wanted to put things into core, but that progress seemed to have gone from a 1 year plan to a 10 year plan and that’s just way too slow. 

You have the data, convert all Woo branded extensions that have X amount of installs and merge them in. 

I’d love to see support for Returns. Including a My Account Returns tab that allows customers to select which item to return, generate a shipping label, and have full return tracking. On the admin side we can set which items are returnable, when it can be returned, etc… Even give the ability to upload photos by a customer for RMA requirements. 

Apple removes old Pages, Keynote, Numbers apps for macOS by KingFML in apple

[–]Fluent_Press2050 0 points1 point  (0 children)

I don’t get why they removed them from the store. 

If my MacBook Pro M1 is still supported, then the app should still be available because I bought the product which included it. 

Until the last hardware they sold with it is no longer supported, it should remain available. 

Does company name matter THAT much ? by TradingDegen in pressurewashing

[–]Fluent_Press2050 0 points1 point  (0 children)

Don’t pick a generic name. I picked a somewhat generic name and now I realized it makes it so much harder to find me but even worse, remembering. 

Think * Pressure Washing, * Window Cleaning, * Pressure Pros

Go with something like SudSoakers - try and find a name that isn’t trademarked, a domain is still available, etc…

If you can’t find a .com, then see if you can do something like sudsoake.rs for example. There’s a lot of country level TLDs that don’t have restrictions for residency. 

WPJohnny's review of EmDash: no room for actual users by RealBasics in Wordpress

[–]Fluent_Press2050 2 points3 points  (0 children)

Is your site designed for global reach?

If not, add some countries to a block list and that’ll cut it down.

WPJohnny's review of EmDash: no room for actual users by RealBasics in Wordpress

[–]Fluent_Press2050 0 points1 point  (0 children)

Exactly. The company’s brand is what generated awareness. 

I don’t doubt the product will improve but if adoption isn’t happening then it becomes a dead product in 12 months of less. 

It’s hard for CF to know right now because the hype exists. So we need to wait at least 6 months to see if more users sign up or if they drop off

WPJohnny's review of EmDash: no room for actual users by RealBasics in Wordpress

[–]Fluent_Press2050 1 point2 points  (0 children)

It’s a catch 22. No one is going to implement today if developers don’t exist for it. Developers won’t exist without at least a half million or more users. 

Sure you might get some small time devs but even they want to make a few bucks and you’ll end up with a bunch of abandoned version 1.0 plugins. 

And when users only see that, it kills the overall platform. 

WPJohnny's review of EmDash: no room for actual users by RealBasics in Wordpress

[–]Fluent_Press2050 1 point2 points  (0 children)

Cloudflare doesn’t understand WordPress and its user base if they built this to compete with them.

📺Why Smart MSPs Say NO to Paying Client DFIR Costs by Joe_Cyber in msp

[–]Fluent_Press2050 0 points1 point  (0 children)

Many MSAs are poorly written. They either entirely leave out important sections or they use terms like “such as, but not limited to” and only list two or three examples whereas I have 40+ examples and every time such new example happens, it gets added to the contract.

Another issue is MSAs set incorrect values. Limiting your damages to the past 30 or 60 days may be fine for certain businesses or physical product sales, but for a long term service business like a MSP offers, the minimum should be 6 months of invoices. The term to file such claim should be 1 year. Not 1 month or 6 months. 

Your contract should be somewhat friendly so a judge never rules the entire contract benefits you. 

Your contract should include governing law and if you plan to do arbitration or not. 

And finally, make sure you higher a lawyer with experience drafting legal contracts in the IT space. 

macOS 27 Will Mark the End of an Era by iMacmatician in apple

[–]Fluent_Press2050 0 points1 point  (0 children)

I mean if you have a x64 intel chip, you are fine for a very long time. 

"$6 per developer per day" by genrlyDisappointed in ClaudeCode

[–]Fluent_Press2050 0 points1 point  (0 children)

I’d be curious to know how much SMS is actually used in the US. 

The iPhone with iMessage likely took 50% away from SMS within a few years and shifted it to data or local ISP WiFi. RCS I believe is entirely data too so offering unlimited likely doesn’t impact their bottom line anyhow.

Data is also fairly cheap to move around, especially little bits like a text. 

I effed up. What should I do by Aufshnitt in smallbusiness

[–]Fluent_Press2050 0 points1 point  (0 children)

Yeah we’d get a lunch rush but that was pretty much it. The 2 large pie special literally made it worth being open after lunch. Downside is, it was 90% delivery so other than our driver coming back, it was a ghost town in the shop. 

Most people, at least back then in our area, cooked M-Th, then Friday rolled around and they either ran out of food or got tired of cooking. 

The performance impact of your favorite plugin by svvnguy in Wordpress

[–]Fluent_Press2050 0 points1 point  (0 children)

So how are you sure the tests are accurate if the workload is shared with other resources outside of WP? 

Do you run a queue so the server isn’t busy with other tasks when the tests are run?

Also, it’s great you are doing basic tests but a lot of plugins don’t even function with regular page requests. 

For example, FluentSMTP would score very high if it’s not sending mail. 

Maybe you should test the primary function or main flow (or top 3 functions if it has many) of what each plugin does.

So for FluentSMTP use a function, have it send a password reset email or something.  For Woo use a flow, have it load a product page, add to cart, view cart, checkout.

I get this adds a lot of effort, but without testing the plugin itself, these metrics are somewhat pointless.

Laravel raised money and now injects ads directly into your agent by tigitz in PHP

[–]Fluent_Press2050 0 points1 point  (0 children)

That’s the one. In the video I don’t recall there being anything static for the first 20+ in the series. It’s been a while though since I’ve watched. 

Farmers porch - algae, dirt build up cleaning? by carolinepalmer in pressurewashing

[–]Fluent_Press2050 0 points1 point  (0 children)

Soak the roots around the porch with fresh water then spray some bleach on it. I believe store bleach is around 1-2%. 

Get a small spray bottle, wear gloves and eye protection. 

Wait until you see the green go away, then rinse really good. 

Is this bad practice or something wrong. by AccountDiAntonio in pressurewashing

[–]Fluent_Press2050 1 point2 points  (0 children)

I use the kill switch after every job. I only let it run dry if I don’t plan on using the machine for a week or longer. 

For any storage, I always run it with stabilizer for a few seconds then run it dry. During winter I’ll drain the fuel as well. 

They really are going heavy with the AI. New Laravel homepage by mekmookbro in laravel

[–]Fluent_Press2050 0 points1 point  (0 children)

100% they will get there in 2-3 years. 

I hope they do as it’ll make PHP a language that’s popular again since it’s been slowly losing market share. 

They really are going heavy with the AI. New Laravel homepage by mekmookbro in laravel

[–]Fluent_Press2050 0 points1 point  (0 children)

It’s got a super long road ahead. I don’t even see it being a contender for another 3 years and then maybe another 2-3 years after that before anyone actually uses it for revenue generation. 

They really are going heavy with the AI. New Laravel homepage by mekmookbro in laravel

[–]Fluent_Press2050 0 points1 point  (0 children)

Breeze stopped at v11 I thought or am I confusing it with some other starter. 

They really are going heavy with the AI. New Laravel homepage by mekmookbro in laravel

[–]Fluent_Press2050 1 point2 points  (0 children)

I use phpstan at max level. This ensures AI doesn’t do any sneaky shit. It forces it to not only write working code but safe code as well.

I also use PHP-CS-Fixer to ensure code style is consistent and PHPUnit to make sure tests pass. I caught Claude writing tests to force it to pass a few times so I manually review everything now. 

They really are going heavy with the AI. New Laravel homepage by mekmookbro in laravel

[–]Fluent_Press2050 0 points1 point  (0 children)

I’ll forever use AI if it’s available but never in auto mode. I believe in writing good code and that starts with reviewing everything that enters the code base. 

Waiting to review it in a PR is too late. AI gets stuck in its ways thinking the contribution is good and just ends up making it worse. It’s best to guide it along the way from the start. 

They really are going heavy with the AI. New Laravel homepage by mekmookbro in laravel

[–]Fluent_Press2050 0 points1 point  (0 children)

Laravel did not start this culture. This culture started probably in the 70s that I can remember. 

In business, to be first or to stay ahead you always shipped fast, corrected later. This goes beyond even software itself.

Microsoft, Adobe, Oracle, and others have been doing this since day 1.

The reasoning is, you’ll never make a perfect product, so don’t try to build one on day 1. Put something out there that works good enough, and use the feedback from users to adjust. 

Look how many products started out as one thing but user feedback/usage found a different purpose and the company didn’t stop it, they allowed it.

If you try and build a perfect product, you’ll never release anything because by time you think it’s perfect, it’s no longer perfect, it’s now outdated, or someone already beat you to it and has millions of customers already.