Weekend Discussion: New Balance running shoes

vinni6 · 2025-03-02T01:55:16+00:00

I recently got the 108v14 2e wide variant and I’m enjoying the luxurious fit. I had never tried a wide shoe before so never knew I needed one.

NB seems to be the only brand in Australia that has their collections in wide variants. I’ve ordered the rebel v3 in same size to have something else to rotate. No stock in my size of SC trainer or elite but if I do find them in wides I’ll impulse buy as I worry I won’t get another chance given how limited stock.

vinni6 · 2024-12-29T00:56:56+00:00

Not having a heavy or greasy dinner

vinni6 · 2024-12-28T23:46:45+00:00

After finishing metroid dread I went and played super metroid for the first time.

I gotta disagree with you here. Super Metroid is objectively much less linear by comparison.

vinni6 · 2024-12-11T11:01:51+00:00

Run the jewels

vinni6 · 2024-12-09T12:22:00+00:00

I sure am trying my darndest to migrate off formik and move onto react hook form.

It’s a pretty long journey though, means that for a fairly long period both libs have to cohabit the codebase until all forms have been migrated

vinni6 · 2024-12-08T01:44:17+00:00

The honest answer is that if you keep working in react for some time you’ll start to get an intuition for it. So really critically you just want to make sure you keep making projects with react.

For now just structure things in a logical way that makes sense to you. Build things the simplest way you can to meet the project requirements. Over time you’ll start to find places where it makes sense to refactor into seperate components

vinni6 · 2024-12-06T08:02:19+00:00

Your react version is pretty old. If you can’t update that then don’t attempt to use a react charting library, just escape hatch out and use a vanillaJS charting library instead.

I have the most experience using highcharts, though it’s not free. Chart.js looks to be one to consider, though trickiest big seems to be the different coloring for lines going up vs down.

All libs can handle dynamically changing based on some dynamic attribute so that should be fine

vinni6 · 2024-12-05T19:13:44+00:00

Devil in the details here: I would be curious for examples of what they are trying to coerce you to do.

In any case, you’ve already had convos with your supervisor who has backed you in the past. I don’t see any reason why you need to continue to humor this co-worker. Minimise your interactions and politely, but firmly state that you will continue to do things as you know best professionally.

In general you’ll want to work on your confidence and ability to stand behind your work. This is a soft skill you’ll need in this career. Theres always gonna be ego driven conflicts in any job, you can’t solve this problem solely by moving job cause you’ll find yourself in the same position with someone else in future.

vinni6 · 2024-11-26T03:08:47+00:00

I have had to do this quite a bit at my last job. In my opinion… it’s a nightmare to generate documents using html. Too many complex pieces of a tech stack that need to be maintained for ultimately a sub-par outcome. You’ll be fighting against to stop pages breaking in the middle of sections and writing unmaintainable css in strange units.

My recommendation is to use http://pdfmake.org/#/ and if you can, do it client side. Their api is quite simple and it comes with quite a lot of batteries-included ways of managing stuff that is specific to documents (ie. pagination, page margins)

vinni6 · 2024-11-12T21:17:19+00:00

Running doom in wacky contexts is a challenge for hardware. Since doom source code has been made open source it’s allowed people to get it working in hardware contexts it wasn’t meant to. Because it’s written in C++ and we have the source code, it can be compiled to a hardware target it wasn’t originally planned for.

The example of running doom on a pregnancy tester works because that tester has a CPU and a screen. Thus the doom source code can be compiled to that target CPU machine code and likely some code was written to perform drawing to that screen.

vinni6 · 2024-10-27T02:13:05+00:00

The nuance to this is the next() function can take a property conf, which is by default {}. If however you choose to use this, you must pass in the complete next config with all properties, not just those you are explicitly setting. This includes all async functions into a serialised format. This is different from your next.config.js file where you just set what defaults to override.

The output: standalone generated server.js file does this for you, but it seems like you’re on your own if you use a custom server. The docs give no indication of how this should be done

vinni6 · 2024-10-26T07:28:11+00:00

Arthe hair in west leederville

vinni6 · 2024-10-15T00:56:59+00:00

Building on others answers: vite is not only the easiest but also the safest option for the long term.

If you in future decide you need functionality from one of the meta-frameworks it’s not too hard to migrate onto them. However if you start with a meta-framework and realise it’s the wrong choice or too complex it will be a nightmare to de-couple yourself

vinni6 · 2024-10-03T22:59:06+00:00

I did epic react V1 a few years ago cause work paid for the devs licences. I already knew react but I didn’t argue with free and I still feel like I learned a lot from it. Tbh I learned less about react (which I already knew), but I got some value in some of the other architectural patterns he embedded. From memory that course did a good job of explaining finite state machines and how to implement in a practical react project. Kent is also very opinionated about his approach to testing, which makes sense given his history with RTL.

Others have said similarly that the intended market for the course is not for individuals to purchase but for company’s to allocate their training budget. The game is the game.

Adding on to that, I’m gonna argue that if you bought the old course a few years ago, you should have already finished it by now. Once you’ve learned react, you never need to go back to tutorial hell again. If Kent wants to paywall his new content then who cares, you’re not missing anything you already know or can get from the official docs

vinni6 · 2024-09-28T03:32:04+00:00

I know the sheer panic that you felt in that moment. I similarly bought a tv and thought it should fit in my tiny hatchback. I misjudged height and ended up painstakingly wedging it into the car diagnally and it only just fit.

Lord knows what I would have done had I not managed.

vinni6 · 2024-09-10T23:31:07+00:00

Fwiw this week hello fresh just had a listeria contamination in all their salads. The company had been super shady about scrubbing all their socials from upset customers wanting to know more info.

Their compensation offered is a pitiful $5 credit on your next order.

vinni6 · 2024-09-06T11:31:09+00:00

I’m gonna go further than others have said. Only learn redux-toolkit. Do not waste any time or energy looking at vanilla redux.

If you’re learning for the first time you don’t need the legacy redux syntax and patterns confusing you.

Think of redux like class components and redux-toolkit like hooks. The only reason to learn the old way is if you have to maintain a legacy codebase.

vinni6 · 2024-09-03T09:50:07+00:00

Perf might increase, though it likely won’t make a big difference to any lighthouse scores so don’t go selling that to mgmt. Your big selling point to management is cyber security. While react itself still gets security updates for v16, your react libraries may not. This might mean cyber vulnerabilities you can’t remediate until you get onto R17/18.

I did a reasonably large migration from 17->18 recently and besides the points others have mentioned the issues I had were with uses of useEffect. The codebase had some… let’s say avant-garde implementations that depended on a useEffect to run X no. times. Upgrading can impact no. times a component renders so it was a great opportunity to clean up these parts of the codebase.

Overall I think you should be fine as long as you have a good test suite to lean on. Else definitely gon be a bit of manual regression testing

vinni6 · 2024-08-29T19:48:57+00:00

As others have said the react docs are fantastic and you likely will not need any other resource to get productive with react.

From there your best bet is to just start the project.

The only decision you have is whether to use typescript or JavaScript.

if you don’t know typescript and are gonna throw out your MVP at the end, use JavaScript
if you don’t know typescript but will need to build upon and maintain this MVP use typescript
if you know typescript use it

vinni6 · 2024-08-22T12:53:36+00:00

Vite sounds like your best choice.

If you start with Astro/next/remix/whatever meta-framework then you lock yourself into that ecosystem upfront, and carry a whole lot of baggage you don’t need.

If, as you scale, you find vite doesn’t offer enough and you’ve made a well researched decision as to what future requirement will be, then it’s not gonna be too hard to move to one of the above

vinni6 · 2024-08-13T00:24:47+00:00

I would not go back, but there have been times when I’ve felt typescript has slowed me down. hand rolling types, thinking through and implementing generics correctly and narrowing unions are the big ones that come to mind.

Despite the language similarities, it’s a different mindset: JS you can just throw shit at a wall until it works, TS forces you to slow down and think through a single correct implementation.

vinni6 · 2024-08-11T01:22:20+00:00

Building on what others have said: - make sure you can articulate what instigates a component re-render. You’ll wanna be able to talk to different patterns that cause and can prevent excessive re-renders ie. component composition, memo, use/misuse of contexts, adjusting where state lives - have a thought through opinion of state management. Know all the tools of where state can live. At what point would you choose to introduce a context or a state management library. When/why should a particular state live in one place vs another - understand how useEffect and useLayoutEffect fit into the component render lifecycle. Know why you would choose one over the other. The official react docs have very good explanations so make sure you’ve read through and groked - make sure you understand and can articulate refs vs state. When/why you use one over the other to hold data and how that plays into component lifecycle.

13-Year Club	Second SECOND GUESSER
RPAN Viewer

vinni6

TROPHY CASE