bedroom_jabroni

  Location: Ukraine
  Remote: Yes
  Willing to relocate: No
  Technologies: JavaScript, Node.js, Vue.js, MySQL, PHP, WordPress
  Résumé/CV: On request
  Email: berdoom_jabroni at proton.me

I'm a full-stack guy with experience contributing to whatever was available at the time I was job hunting. This includes: CPQ/ERP interfaces, branching out an ad tech business into a SaaS, a live help desk dashboard, a high-load betting backend & analytics system. I also maintained a few premium WordPress themes until that income stream ran out -- this means I can talk to customers, process customer feedback and iterate on it. Though as far as talking to customers goes I'd rather not to.

Looking for something that aligns with my stack or something to branch out into Rust/Go. EU or US hours are ok. I can vibe code in familiar product domains if that's your cup of tea. I also have experience leading a small team. Part-time or full-time is fine by me, so are short-term and long-term projects.

Product domains I am particularly interested in are: Crypto / Blockchain, Gambling, Fintech, Entertainment. Not that I'd pass on opportunities in different areas but these are what I'm familiar with.

Given my experience posting last month, "entrepreneurs" with LinkedIn job scrappers offering to subscribe to their shabby job lists for "only" $20/mo and other kinds of promotions please do not engage.

Yes I wrote it myself, no I am not affiliated with the CCP or DPRK, good luck to y'all with y'all's job search!

Why is it empty? /s

Damn it hasn't even been a week.

I wasn't correcting the parent post. I was being sceptical regarding them contributing by owning ACF because they just bought the plugin with the intention to squeeze its userbase for more money for a product that was more or less complete at the moment of acquisition. Or, to paraphrase it, they hijacked and repurposed the original ACF pricing :)

The supply chain attack was shitty and uncalled for but still very tame. I think launching a fork as a separate entry would have been sufficient and less drama.

Surprisingly two wrongs made a right and the average customer got a little bit unfucked by not having to pay for the ACF PRO subscription if they don't want to.

I agree, introducing it into the core should have and could have been a constructive move way before given how important the plugin is in the WP ecosystem.

When and how it happened was a hilarious plot twist nobody expected.

WP Engine didn't make ACF, they acquired the company that acquired the OG creator of the plugin.

Their contribution to the plugin was a switch to a subscription-based model and they also started reaching out privately to theme authors with ambiguously-worded emails that could be interpreted as them forcing you to stop bundling the plugin with your theme (we had a lifetime license) and directing customers to their sales. Personally I chose not to engage with that communication.

The fight between Matt and WP Engine was messy and I agree with most of your points but I also do think that forking ACF into SCF was a net positive for the community.

Quick, somebody back up the WP Plugins repository.

A relatively popular WordPress theme on ThemeForest could bring in $30k on a good month in the market's prime. Nowadays the number is much more humble.

The .value comparison is not fair because it's a single value vs an object property. A better comparison would be against something like Vue's reactive() where it doesn't require you to add this "boilerplate".

I wasn't referring to the ergonomics - the weirdness was from the way it was worded like "Here's one trick Big Framework doesn't want YOU to know" as if React, Vue and such were gatekeeping their reactivity while they're actively maintaining and sharing standalone versions of it.

preact/signals-core has 0 dependencies, your project could also benefit from mentioning what primitive is being implemented for the reader's information. The size difference is negligible. The readme creates a false dilemma where there's either Mador or "having to use a framework" but it hasn't been the case for ages - as I mentioned above the major frameworks have decoupled versions of their reactivity available. This makes the other reply where "the frontend community deserves tools like this" sound weird because it ignores the great tools that have been available for a while.

Good learning experience but a very weird presentation.

There are many standalone plug-n-play implementations of the signal primitive in JS. To name a few: preact/signals, vue reactivity, etc, there's even a TC39 proposal for a lang feature. Is this meant to stand out by doing things differently or reinvent them?

  Location: Ukraine
  Remote: Yes
  Willing to relocate: Not at the moment, maybe in the future
  Technologies: JavaScript, Node.js, Vue.js, MySQL, PHP, WordPress
  Résumé/CV: On request
  Email: berdoom_jabroni at proton.me

I am a fullstack engineer with 9+ yoe mostly dealing with Node and Vue. I've contributed to a vast range of projects such as launching an existing service as a SAAS, iterating an existing real-time support dashboard for a launch with a major player in the US automotive industry, high-load backends, CRM and CPQ systems, etc. As a secondary skill I'm also a WordPress expert with more than 6 yoe leading the support & development of premium themes for a ThemeForest author.

Happy to work in a team or independently. I am comfortable working in teams with members in different timezones.

Let me just join in into the most relatable thread I've seen.

The real business ideas were the friends we made along the way.

This topic is the perpetual motion machine of journalism: every few months I see an article about how artificial sweeteners are bad and then another article that states the opposite.

Makes me want to make sure my body is donated to science as a data point to help settle this.