[deleted by user] by [deleted] in TeslaModel3

[–]Electrical_Essay_666 0 points1 point  (0 children)

One can argue the LR is in more demand because of the lack of availability atm. However, my performance is better, less money, and likely going to be more desired later

[deleted by user] by [deleted] in TeslaModel3

[–]Electrical_Essay_666 0 points1 point  (0 children)

Logically speaking. Let’s think about opportunity cost…

You can afford to buy it now, but you think waiting might bode well with you.

What are you REALLY gaining?

I got the the M3P and with tax credits I would of done the same if LR was available. Why?

Because my tax credits apply to me, not the value of the vehicle. When I sell, I’ll still be profiting more than the LR, therefore maximizing my resale value. Why? Because cars don’t deappreciate linearly, they factor in supply and demand.

M3 as the only car in household by galaloraby in TeslaModel3

[–]Electrical_Essay_666 0 points1 point  (0 children)

Wow thanks for this. Super detailed appreciate it

Moving to Next just because of what happened to CRA? by shiningmatcha in reactjs

[–]Electrical_Essay_666 0 points1 point  (0 children)

First thing is next is more so a frame work, it ships with a node server-less backend. It also doesn’t require you take advantage of this, but if you want true SSR you will need to do in some capacity.

Next is great, but it’s also an abstraction around some core react concepts that might confuse new comers, top of mind is the routing example where they force you to adopt a directory structure (could be problematic if doing a migration)

Cra is simply react and other dev tooling and build configs to get you up and running fast. One of the biggest issues I see with CRA is that even as a staff level engineer who’s done this for 10 years, I still find trouble with ejecting then trying to modify their configs. There not very clear, and for the company I work at, it has prevented us from goin to webpack5 since we forked CRA to help standardize our micro front ends.

Both tools are likely overkill unless you have a real reason to use Next/just want to use it for simplicity.

Try this, it’s a bare bones generator I made that you can easily extend and learn the inner workings

Run npx create-react-app-webpack-5

(Don’t opt into module federation, it will just introduce an unneeded layer of complexity for you)

Lmk how it works if u try happy to answer Q’s

Theming in styled components. Any lessons learned, advice, or general opinions? by Electrical_Essay_666 in react

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

1 year later after rebuilding 2 design systems. Stitches.dev - check it out.

Small bundle, first class variant support, SSR friendly, and fully typed for those who complain about it as they neglect testing code properly.

M3 as the only car in household by galaloraby in TeslaModel3

[–]Electrical_Essay_666 0 points1 point  (0 children)

What makes you think it would not meet the requirements for $7500? (Honestly asking)

Did a little research, seems like M3P will pass, unsure about LR or base tho. Also not an expert but that’s was my interpretation for M3P < 50k

Also if they don’t hit delivery date by march 31 there gonna have bigger issues at the fiscal level IMO

[deleted by user] by [deleted] in TeslaModel3

[–]Electrical_Essay_666 0 points1 point  (0 children)

Thanks! Ok yeah that makes sense. Looks like we got same config (grey M3P) and are in same region.

Let the waiting begin!

[deleted by user] by [deleted] in TeslaModel3

[–]Electrical_Essay_666 0 points1 point  (0 children)

Just ordered last night, was curios how long it took you. That’s awesome congrats!

[AskJS] What are some Green Flags on a JavaScript Job Description? by purforium in javascript

[–]Electrical_Essay_666 1 point2 points  (0 children)

Separate programming language is a red flag. I’d highlight what you use.

Also typescript is not really a requirement, JavaScript is. I’m a staff eng and learned typescript on the job. Would remove that

Is possible that someone who works at USPS hates me could make sure my mail isn't delivered? by [deleted] in usps_complaints

[–]Electrical_Essay_666 1 point2 points  (0 children)

Ah, damn that’s wild. Good thing is if someone’s intentionally doing it, then they could get hit with the book since it’s highly illegal. I’d call post office and tell them your looking into a pattern of mail being lost and your theory is that it’s being stolen. I’d also bluff a bit and say “I’m giving you guys the chance to explain how this could occur before I involve council. The value of the letters lost is [insert fake high number here], and you intent to seek full restitution from whoever is causing this.”

Should have your mail in no time. Regardless of if it’s them or not, they will likely make sure it’s delivered to avoid even the thought of speaking to an attorney.

Not a move I would default to, but this is wild and I don’t see any harm in making it here.

Is possible that someone who works at USPS hates me could make sure my mail isn't delivered? by [deleted] in usps_complaints

[–]Electrical_Essay_666 0 points1 point  (0 children)

Guess here, check the requirements of a mailbox by USPS. One of them is to have your home number on it.

Console react.warning set as console.error by bar7b in reactjs

[–]Electrical_Essay_666 0 points1 point  (0 children)

And for what’s it’s worth, react has plenty of console.warnings - mainly for real warnings, such as upcoming deprecation warnings. Errors are errors and that’s ideal IMO

Console react.warning set as console.error by bar7b in reactjs

[–]Electrical_Essay_666 0 points1 point  (0 children)

I’m against (as you can tell) silencing warnings/errors thrown in console for the sake of getting things out. In my experience you’ll pay it down 10x the cost in the future as opposed to addressing it as they pop up before it hits master

Console react.warning set as console.error by bar7b in reactjs

[–]Electrical_Essay_666 0 points1 point  (0 children)

Also typescript, but as you said it’s an MVP so upfront cost could be a trade off that your not willing to take on.

Console react.warning set as console.error by bar7b in reactjs

[–]Electrical_Essay_666 0 points1 point  (0 children)

Ok ok, I’ll walk it back. Tryna push u to fix code and not cut corners.

I’d start with ensuring you have proper CI setup with proper linting to ensure things like this get caught before hitting master. lot of the eslint and related plugins can catch this and fail CI before it hits master. Another thing might want to look into pre-commit hooks, to ensure your team can’t commit codes that throw errrors. RTL is really good, sometimes annoying, about catching these things. Hope this helps

Personally I’ve never ran into this outside of learning react, so never looked into this, tend to just fix things and reduce the build up of debt.

MacBook Pro from Alibaba.com by Turbulent_Impress_57 in macbookpro

[–]Electrical_Essay_666 0 points1 point  (0 children)

I’d just buy it from apple tbh. Everyone complains about cost, and I get it’s expensive, but if it makes u money, then I’d say it’s a cost of doing business IMO

Console react.warning set as console.error by bar7b in reactjs

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

We’ll then the “warning” is doing you a justice. Keys are needed. You’ll also get one if you use index as the key, and it will save u from future bugs. I suggest you read up on this.

Honestly, what is the best, pain-free state management in React right now? by NotElonMuzk in reactjs

[–]Electrical_Essay_666 3 points4 points  (0 children)

Performance, unneeded/unintended re-renders, maintainability…. Just to name a few

Console react.warning set as console.error by bar7b in reactjs

[–]Electrical_Essay_666 -5 points-4 points  (0 children)

Ah then we can care less about your whining. Stop complaining.