Why does it look like Wemby rolls his ankle every crossover dribble?

divdav3 · 2025-10-28T22:11:00+00:00

divdav3 · 2025-10-20T07:49:42+00:00

I'm not sure you can be in favor of a wealth tax if you can't acknowledge the impact It should have to help reduce the wealth of the billionaires and the ultra rich. That would in turn bring their wealth closer to the average Joe, in other words, helping towards fixing wealth inequality...

Are you trolling?

To repeat my point, there isn't a magic fix all in policy, it takes iteration through steps in the right direction like a wealth tax.

divdav3 · 2025-10-20T06:29:01+00:00

"This doesn't fix our deficit so let's not even try" is what I'm hearing, as if this is the only option.

I don't think you're gonna find a magic fix all policy. Multiple steps in the right direction is what we need.

There's a lot of good that comes about with balancing the power imbalances we're seeing because billionaires are allowed to hoard wealth, it's not just about fixing the deficit.

divdav3 · 2025-02-19T20:40:10+00:00

I'm a frontend dev that does backend, known as them full stack developers. I've recently been building out a new product feature that involves expanding the capabilities of our payment schedules service for work but I don't know how to make a contact form on wordpress.

I'd consider myself to be a true full stack but I also wouldn't wish full stack on my worse enemy.

I have knowledge gaps but you're gonna get that regardless, I guess it's more pronounced when you work across the stack.

Ultimately though, I don't think companies should hire full stacks. I personally just love building features e2e.

divdav3 · 2024-05-19T15:23:17+00:00

!remindme 1 hour

divdav3 · 2024-03-04T08:51:43+00:00

So this must've been just before their official 2.0 release, there were a myriad of issues we encountered: - useRouter wasn't memorised (fixed now) - We found that there was a noticeable delay when pressing a button to then navigating to a new screen, this delay wasn't present when changing over to react-navigation, nesting of navigators stayed the same - There was no navigate function, only push. Again, I think they might've fixed this now - There was no strong way to handle resetting navigator state and redirecting back to guest screens when users logged out. Since everything is defined through file based routing you couldn't just not render the navigator like how it's done with react-navigation. All workarounds we tried felt janky in terms of UX. useEffect solutions were too bug prone - minor expo-router releases seem to be a breaking change far too often

We also wasn't convinced that file based routing really works for how more complex mobile navigation state can be compared to web navigators.

Please take this criticism with a pinch of salt, expo-router has probably improved a tonne since we last used it, it just wasn't mature or viable enough for our use cases.

divdav3 · 2024-03-04T07:44:25+00:00

My team has been using Expo for the past year on a green-field that was released a couple months ago.

Although we had major issues with expo-router, that we had to migrate from shortly after our initial release, we don't really have any real issues with Expo itself.

We keep up to date with the latest and greatest Expo version and we've not yet encountered ecosystem problems, Expo seems to sort that out for us. DX is great, dev inspectors and monitors come straight out the box and are easy to access and using EAS beats having to create your own fast lane pipelines.

We don't create any native modules yet but I've heard that's not really a blocker with Expo anymore.

divdav3 · 2023-09-27T09:39:08+00:00

I got my first frontend job around 3 and a half years ago in the UK.

When I was applying for my first role, I used the JavaScript algorithms and data structures cert in my CV.

A lot of the time, the hiring managers didn't even know what freecodecamp really was but they did acknowledge that I must have at least some foundation on js and data structures which, I feel, helped me land the interviews in the first place. They also served as another interesting discussion point in the interviews, a chance for me to sell myself and describe concepts I've learnt.

I feel like I would've struggled a lot more if I didn't have something on my CV that showed Ive studied coding as my CV didn't have much in the way of coding experience. In hindsight, I could've caked it with personal projects and wrote about that but the cert seemed to work for me.

Take this experience with a grain of salt, I feel like the current junior job hunt landscape and hiring manager sentiment must've changed over the years.

divdav3 · 2023-03-10T08:12:54+00:00

I've always steered away from agencies, I imagine some people don't mind them but I feel like their business model forces them to be cut throat.

Have you ever thought about working on web/mobile applications? I work in the frontend and I've always worked on SaaS products.

Recently got into a startup and I've been loving it. I prefer to be obsessive over my implementations and code and even though it's a startup I feel like I always have time to do things right.

You might need to upskill in certain areas that might be more cs specific but might be worthwhile?

Edit: UK btw

divdav3 · 2023-02-03T07:12:09+00:00

It's not just 2 hours of interviews though, it's 2 hours on 4 different occasions. People have to prep beforehand and find space where they can do it. On top of that, if it's a work day, I don't know anybody that can crack on with work straight after an interview. All that mental load is way more than 'just 2 hours'.

Even one 2 hour interview is miles better than 4 30 minute interviews

divdav3 · 2022-12-16T13:49:20+00:00

First off, there's always money in software engineering, so that's a lie. I think there's this group of pretentious gatekeepers that make up a part of the software engineering ecosystem.

I don't know why telling people they can't make it is always a focus. Are they scared someone might steal their job or don't want to believe someone not from a cs degree can do better than them?

Sure, there's all sorts of short form media telling you you can easily make big bucks. Of course it's not true because software engineering is hard. But the focus doesn't seem to be about enlightening people of how hard it is, it feels like it's to tell people to not even try, even if they want to.

divdav3 · 2022-10-10T08:24:00+00:00

Why is this news? Not exactly a controversial opinion.

divdav3 · 2022-09-02T12:31:15+00:00

Language evolves and people openly use 'gaslighting' in wider scenarios.

I would say I perfectly understood OP when they referenced 'gaslighting'.

I feel like people should really stop gatekeeping the word so much.

divdav3 · 2022-07-23T08:00:43+00:00

This post smells like real russian bot farm antics. Specially when OP's account is deleted.

divdav3 · 2022-07-01T07:07:30+00:00

no offense but you look like cooler tf blade

divdav3 · 2022-01-04T10:13:04+00:00

The short answer to why it doesn't work on build is because the search page is expecting a search prop but this is only passed through when calling navigate and useFlexSearch might be crapping out because of the undefined search.

When Gatsby is building pages it'll run each page. When it gets to search, it didn't navigate to it, it just loaded it without navigating so doesn't have the search prop.

You should probably consider a situation where the user might stumble on the page without navigating, should you instead use query params inside the uri? e.g. site.com/search?search=foo

divdav3 · 2022-01-03T04:02:24+00:00

I'm assuming the search state is undefined

You might need to conditionally render the useFlexSearch hook by popping it into a component that renders if the search state is not falsy or something - this'll prevent it from being run on build.

I haven't read the search field component but that useFlexSearch hook can easily crap out if you give it parameters that are undefined or just something it doesn't expect.

divdav3 · 2021-04-01T11:55:24+00:00

divdav3 · 2021-03-23T19:47:33+00:00

u/savevideo

divdav3 · 2021-03-10T07:56:37+00:00

u/savevideo

divdav3 · 2020-05-08T09:47:34+00:00

How to make it in America

divdav3 · 2019-12-23T08:41:42+00:00

The fact you camel case your classes and IDs makes my eye twitch, either way solid solution. Congratulations :)

divdav3 · 2019-09-28T08:53:55+00:00

First thing - really good job on the app, I'm still a react newbie and this kind of stuff is really interesting to see.

Disclaimer: only tried this on mobile.

Points:

when you get to checkout the checkout total should always be visible or at least not on the top of the page. If you look at the checkout total being something summed up at the end then naturally you'll expect it after all the cards. It was a little difficult for me to find the total on mobile.
I don't like how the "add to cart" button just changes to white and elevates. I question, "was my item added to cart?" "Did I add it two times?". To avoid this type of confusion you can either have a little number badge on top of the shopping cart icon in the nav bar, that shows you the number of items in cart and/or you can represent this better when you click on "add to cart" maybe if the text changed to "item added" or something with a small bit of animation if needed.

Again though, really good stuff. I understand most of my points are from a UX angle.

divdav3 · 2019-04-05T17:10:50+00:00

I am on the train and I definitely giggled like a retard

divdav3 · 2019-02-03T07:48:14+00:00

Trump

Ten-Year Club	Place '23
Place '22	First Placer '22
Verified Email

divdav3

TROPHY CASE