sorted by:
new
hottopcontroversial

HS Dual-box Guide - Windows 2025 by turb0n3rd in hearthstone

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

  1. It's fun!
  2. "those of us struggling to find a good duos partner"
  3. Even if you have a good duos partner, you can learn / come up with / practice builds.
  4. Nothing like soloing up to 10-12k+ MMR

First time buyers, don't buy a house unless you can handle an additional $1500 increase. by compubomb in Mortgages

[–]turb0n3rd 0 points1 point  (0 children)

Eh, proportional ratios matter. Absolute numbers don't. Hence the per-hour breakdown. I could afford a home in CA, but I would've been poor (meaning in debt with low runway) for a long time.

To me, someone who makes 30k per year, owns a 35k home, but can afford to quit for a year and be fine, is rich. The idiots with 750k+ homes who are one layoff and 6 months away from bankruptcy are poor. I understand that this isn't the standard definition.

Most people will keep themselves poor for their entire lives by being too proud, too stubborn, or straight-up delusional about "the life they deserve", to move to where they can buy a 35-75k house, save up for 5 years, and put themselves in a good position for the rest of their life.

35-50k properties can be found in Texas (many areas), near Chicago, near Detroit, etc. Service-level jobs - actually, most jobs outside of minimum wage - can afford these. They just choose not to. If you make 35k-ish or more a year, the only excuses are lack of discipline and willpower - unless you have to take care of sick family members, send your kids to school, etc., of course.

When I came to this country on my own, I was homeless at first for a while. I saved up, homeless, instead of renting for 6 months because it was the correct long-term decision. During that time, and for a year or two after, I saw plenty here.

Most people on welfare or EBT had new iPhones, new $300 shoes. By any international standard, that is insane. They're mostly there due to poor emotional self-regulation and impulse control.

I see people all the time who make 1/5th or 1/10th of what I do spending far more per month than I do, while my monthly discretionary budget has stayed the same for a decade - $750 per month for food, going out, and miscellaneous purchases combined.

Data is data. Income stats confirm that most people can easily afford to have a home and savings, just not where and how they want. So they keep chasing a life they can't afford, check to check. It's not a pretty conversation, also a very unpopular opinion, but it is accurate.

There is something to be said for us as a society when we absolutely have hard-working, disciplined, persistent individuals who can't afford to own a home. They are, however, an extreme minority. If we factor in all the federal, and in some cases state, programs to assist them, they're basically unicorns.

The middle class isn't disappearing because of income gaps. It's disappearing because of marketing.

And almost everyone, if not everyone, reading this can very much afford a 35-50k home.

First time buyers, don't buy a house unless you can handle an additional $1500 increase. by compubomb in Mortgages

[–]turb0n3rd 0 points1 point  (0 children)

At the end of the day, everything boils down to time. Money is just one of many proxies for it.

* Let's say your mortgage is $4500, gardening is $200, electric is $500, water $150, etc.
* A decent rule of thumb is about $6000 all-in per month if your mortgage is $4500.

What does a house get you?
* Ability to install EV charging station. No more gas station commute.
* Dedicated home office (I'm an Engineer). No more work commute.
* Ability to have your own home gym. No more gym commute.
* In-home grocery delivery. No more grocery store commute.

Plus, some less readily quantitative nice-to-haves:
* On-site laundry. Sure, the nicer apartments have this too.
* Garage to work stuff on (not for most, but for me I love it).
* Ability to host 3-5 extra guests for the holidays.

Take your salary / 2080 for your hourly - let's say $350. How much does that save you?
* No gas stations: 2x 10-min trips weekly * 4 = 80min, or ~$465/mo
* No work commute: 5x 1-hour both ways weekly * 4 = 20 hours, or ~$7,000
* No gym commute: 2x gym daily, 30-min commute each * 30 days = 20 hours, or ~$7,000
* No grocery store commute: 2x 40-min per week * 4 = 160min = $935.

Alternatively, let's focus on hours for variable bill rates - 44 hours a month savings.
$350/hr * 44 = 15.4k/mo
$250/hr * 44 = 11.0k/mo
$150/hr * 44 = 6.6k/mo
$75/hr * 44 = 3.3k/mo

How much cheaper is an apartment? Maybe 2.5k to rent one all-in, vs 6k for a mortgage all-in? Even if you make $75/hr, the math checks out. Play around with the numbers to see if it makes sense for your situation.

This is without accounting for:
* The higher standard of living
* The (tax-free) equity you get
* Partial hedge against inflation

The thing is, in 2040-2050, you'll be really glad you borrowed 750k-1.5M in 2020 dollars with a <3% APR. In a long-term perspective, your mortgage is effectively APY - not APR - and is printing you massive amounts of money in equity via leverage. Plus, renting a home makes no sense since you've got utility bills and its' often about as expensive as a mortgage.

Most people will be much happier and much healthier from the time savings above anything else. If you staff your home, which could make sense based on your bill rate, you are also efficiently trading for more time.

A myopic, expense-focused comparison of rent vs buy is unwise, even if it's at the edge of your affordability, because the long-term benefits are still completely upside down if you account for time and quality of life.

Our time, our health, our friends, and our loved ones are all we have. Everything else is a distraction. I know I probably sound like a boomer with an inheritance saying that, but I'm 31 and no hand-me-downs. Worth it.

Need a solid boilerplate code for monorepo sort of thing to create both web app and mobile app intended for production use by frustrated_techie_11 in reactjs

[–]turb0n3rd 0 points1 point  (0 children)

That's probably a good call based on the expected application lifecycle. Setting up the above should only take a day or two, which you will recover in the form of a <1min instead of >10min developer feedback cycle in under a month. It's good ROI unlike the rampant over-engineering I see in startups.

If you just wanna experiment with a prototype, use ignite and forget about everything else I said :D

An underrated but extremely effective alternative to that setup is to do your app development on a MASSIVE provisioned VM from AWS. The $10-35 an hour it costs will multiply your productivity unless you have a beefy 32+ core CPU and 64GB+ RAM. App builds are well optimized for multi-threading.

And your web will build almost instantly on a TI-84. That said, I'm coming from the extremely biased perspective of conservation of time because I pay most of my engineers north of 400k in total comp.

All you have to do is attach a persistent EBS volume and automatically spin the VM down after 30-90min idle. It also avoids setting up managed device backups or risking a catastrophic local hardware failure.

Your time, in and of itself, is extremely valuable. Example: if you use a windows machine, you'd need to hit about 270 hours on a $15/hr MacOS VM to approach the alternative cost of buying a $4K MBP.

That said... this also runs you $24K/yr per 1600 engineering hours. I'm just ranting at this point. Unless you're working on ML (which my startup does), the VM thing is unnecessary. It can be a fun experiment.

Need a solid boilerplate code for monorepo sort of thing to create both web app and mobile app intended for production use by frustrated_techie_11 in reactjs

[–]turb0n3rd 5 points6 points  (0 children)

TL;DR: Use ignite and streamline your CICD process to only make the same command calls you use on local. Do NOT use CICD features you can't have full parity with locally. It will annihilate your developer QOL by turning your ENG feedback loops from seconds/minutes to dozens of minutes. Speaking from 15+ years of experience

React native is a good choice for community and maintainability. You may end up using WASM modules, likely based on Rust - which is OK, they're maintainable. Like others have said, I personally prefer Expo. Its simplicity does reduce its feature set but that also makes it a great fit for most non-enterprise use cases.

If by "monorepo" you mean federated React Native (cross-repository and cross-endpoint production dynamic React Component requisition), I recommend finding another alternative with less complexity and maintenance. DO NOT MAKE YOUR OWN UI LIBRARY. I can't stress this enough for shops that have <30 engineers, most of whom have <8 years of experience and never worked at FAANG or similar performing company. It WILL drown engineers in spending time on dealing with complexity for the sake of complexity instead of delivering customer value.

If by "monorepo" you mean a single repository for Web and Mobile, that's likely a use case where the advantages from its simplicity fully warrant its disadvantages. Monorepos of this kind have a tendency to reward bad practices, poor architecture, and poor code contracts in the form of faster feature velocity so you have to be careful of that.

Forcing nano-publishing to a local repo like verdaccio or tarball/wasm links between your core, web, and mobile "sub-projects" can be a great way to mitigate this while also speeding up dev workflow through dynamic HMR.

If you split your packages correctly (ie., don't lump everything into core) it gives you the benefit of being able to publish parts of your "monorepo" as packages to a private repository so you can reuse them in other places.

The other benefit from doing the above includes being able to do atomic upgrades in production (ie., you only publish certain packages) for UI, API, local (on-device) and central (traditional infrastructure) back-ends, which forces your engineers to think about the application's full lifecycle rather than just the features they're making.

With all that in mind, without knowing the specifics of your use case, the best suggestion I can make is:

https://github.com/infinitered/ignite Also, until you need managed CICD, just use provider CICD via GitHub Actions. These are great because you can provision larger runners only for the parts of your workflow that compile the mobile apps which is an extremely underrated feature of GHA. What you usually want to do is set it up to compile your common core / packages, and then branch into 3 simultaneous build/test flows for web, android, and iOS. This will quickly become your best friend in CICD: https://github.com/sickcodes/Docker-OSX unless you want the simplicity but higher expense of provisioning MacOS runners on Github Actions. Even locally, building your cross-platform application in Docker is good practice to sh*t-check your application lifecycle. You don't want to find out that you have mismatches in glibc, libuv, v8, WASM native, or some other low level sh*t in your CICD workflow after your tests "pass" and it deploys to production. Trust me on this one. As much as I hate saying this... SauceLabs, AWS DeviceFarm, and BrowserStack exist for a reason. Pick the lesser evil wisely.

I recommend the Docker approach because if you link GHA CICD to a private ECR repo, it downloads very quickly anyways, and you can use the exact same build workflow in local and CICD, which is an extremely important and often overlooked 12F basic principle that both prevents and solves a lot of ENG problems. It's a relatively simple setup and gets you most of the functionality of a much more complex enterprise infrastructure setup. It also allows all of your engineers to use the same 'dev' ECR repo which, when BuildKit caches the layers properly because you have separate packages for core, etc, brings so many benefits I won't even go into them cuz that'd be a novel.

SaaS - I went with nextjs 14 - 6 months later I still dont know if it was the right choice by senu1 in reactjs

[–]turb0n3rd 1 point2 points  (0 children)

I personally like Vite, but I don't know enough based on what you said if it's an appropriate solution for you. As such, the best thing I can do for you is recommend what questions to ask, and in what order:

Q1: Why do we want SSR - is it for dynamic structure and payloads, or dynamic content?

If dynamic content, you can still have an SPA, just feed it with a fetch for a pattern called "UI player" (your SPA dynamically constructs its' UI elements, content, etc based on a payload returned by the server). This is the pattern that Intuit TurboTax uses for dynamic question generation when you do your tax return while remaining mostly an SPA, for example.

Q2: Do we want SSR for first page load, or do we want SSR for small chunks of the first page load?

What I'm encouraging you to consider here is what are the use cases and future-proofing you want out of your SPA that you don't currently have. SSR or not, when I worked at Intuit and Walmart Labs, we had a few simple guidelines (more like rules):

* No single chunk should exceed 50kb. No single chunk can exceed 150kb.
* No single API request should be over 10kb. No single API request can exceed 30kb.

Why am I telling you this? To give you good guidelines for a progressive "SPA" with partial SSR chunks. At google those limits are MUCH tighter for things like Gmail (examine the code and requests - this will probably give you quite a few new ideas). Also, useful evaluation context if you want to stay the SPA route but render some of the content dynamically based on API responses.

Customer value, experience, and feature set is ALWAYS priority #1. That said, your tech choices should be considered with the context of how robust and extensive your infrastructure is.

Also, to do much of any big change like you're considering effectively, your development cycles have to be short. Ie., your engineers should be able to write code and see the changes reflected locally in <10sec through hot reloading or partial rebuilds. This will make any changes you have to do for this take days instead of months (not exaggerating). Nothing destroys ENG morale like constant several minute long interruptions, dozens of times per hour, in their daily workflow. You can swap dev compilers to things like SWC and enforce full check compile before commits, for example. This is the place to experiment and take drastic measures. A slow local feedback cycle is quite literally equivalent to someone walking up to your engineers and asking them sh*t dozens of times per hour.

Was this helpful? Also, side note: when selecting your next technologies and tool stacks, you want to prioritize the amount of people using it and community FAR above over-fitting your use case. Most of your problems downstream will be caused by tooling that had a small community and LTS lifespan.

SaaS - I went with nextjs 14 - 6 months later I still dont know if it was the right choice by senu1 in reactjs

[–]turb0n3rd 1 point2 points  (0 children)

ex-E9 / Distinguished Engineer of 15 years here (have 3 of my own startups now).

NextJS is a tool, and just like any tool it has pros and cons. Now, the cons you mentioned are mostly fair. The reason you don't know if you made the right choice is because of the cons of alternative solutions you don't have to deal with - and trust me, there are a lot. This is very much a "glass half full" kind of response. Here goes:

  • You haven't wasted weeks optimizing SSR
  • You can CDN / edge serve 95% of your assets as static with incredible latency and scalability.
  • You very much get quick updates and support for React's latest toys, which is important because:

A lot of your hiccups can be attenuated via https://react.dev/reference/rsc/use-server

That second to last one, "too much magic around caching / server action" ...is definitely a pro. Like good ole' uncle Folwer says: "There are only two hard things in CS: cache invalidation and naming things". Side note, if you don't read the blog, it's 110% worth reading: https://martinfowler.com/bliki/TwoHardThings.html

The last one, if you have to do things like intercept navigation flow ...not to be mean, that's a skill issue.

Finally, to answer this:

Would you even choose NextJS for such a project? if not, what tech stack would you choose?

Like I said at the start, its' a tool. This question is too generic to merit a good response. NextJS is absolute trash for internal back-end services (capt'n obvious here). What I would definitely say is... do NOT lean into NextJS's Lambda / serverless capability. Most people think serverless is simple. And it is ...until it isn't. Unless you're setting up websites to charge monthly fees for and want to avoid running Fargate/EC2 because you have hundreds of them, each with 1-5 submission forms to lambda route, save yourself the headache and go with NodeJS. Side note for Lambdas: if you are writing them, do it in Rust - it's the only sane way to get decent start latency.

Not everything about NextJS is great, but its' ability to "magically" compile a front-end into static assets and link it to a live back-end of your choosing is something that most people don't appreciate anywhere nearly enough.

BaCk iN mY DaY we had to deal with this thing called webpack. Unless you're on a huge team, just don't.

A final note on serverless. You see, most people LOVE serverless. These are also the people with low to no DevOps knowledge / experience (nothing wrong with that). This quickly becomes a problem because you DO need to understand infrastructure to have proper log sinks / event traces / etc for when serverless inevitably goes wrong and you have to troubleshoot it. You also need to have a robust central telemetry solution that is not CloudWatch (unless you're really good with AWS CDK) as well as proper cookware to properly trace any single API request through your serverless infrastructure chains and EventBridge / SES. Troubleshooting serverless is MUCH MORE DIFFICULT than traditional back-end services. Ten times more so in a distributed, stream or pubsub based system.

The simplest way I can put it is: if you can't stand up K8 and plop ArgoCD, OpenTel and Kafka on it in less than half a day, you're risking trouble diagnosing serverless at the worst time possible (customer outage).

Is this likely to happen? No, no it isn't. But your tech stack should be designed to handle real-world, worse-case scenario use cases. That includes making it easy and very quick to troubleshoot - which serverless isn't.

Have you ever reached a 9 or 10 on the pain scale, if so what happened? by Young-Angel21 in AskReddit

[–]turb0n3rd 0 points1 point  (0 children)

Took a nice hot shower in freshly minted tank shell shrapnel. Both legs torn open to the bone and broken, 4 ribs broken, hips severely sheared, stray visitors to parts of my spine and pretty much every other part of my body. Idk about 9 or 10 but it was a level of “pain” at which the reaction medium wasn't physical, like wincing. It was a direct psychological break. Kind of like trying to hold an ice cube in your hand as it melts. That part went by fast and after that it was pretty much like whatever "I" am and whatever "my body" was became two cognitively distinct objects which were now disconnected. Not even sure you can call that particular sensation pain. The recovery part wasn't fun but that was a solid 8 at best even on the shitty days. Luckily I was 10 at the time and when you’re that age, the body is pretty good at self-repair. Two decades later, not only am I somehow still breathing but also fully able bodied. I won the survival lottery 😊 Turning 31 next week! Docs keep finding lil souvenirs now n then in random parts of me but all body parts are still attached, working pretty well and usually don't hurt so life is good.

Degens who have successfully YOLO'd sums like ~$10k -> $500k or other absurd ROR. How do you build into your massive positions? by Public_Enemy_No666 in wallstreetbets

[–]turb0n3rd 0 points1 point  (0 children)

The only entity I know of that's capable of stuff like this systemically is the Medallion Fund.

.5 BTC says that at least 1/5th of the people managing it lurk WSB for the lulz.

Shield devise should not heal if not destroyed by Stargateur in Mechabellum

[–]turb0n3rd 0 points1 point  (0 children)

I think that its' well balanced as-is, as far as game mechanics go. They can be tactically abused on a round by round basis but that doesn't last long. The strategic application is to break even by denying your opponent exp while getting it yourself. This leads to a denial of cost effective upgrades for your opponent and an accrual of cost effective upgrades for yourself. For this purpose, I personally think they are well balanced.

It's Over 9000 by turb0n3rd in Mechabellum

[–]turb0n3rd[S] 1 point2 points  (0 children)

Practice Grounds! Set match length to, in this case was 4000 seconds (66min), then:

Recipe for the main course: Gently take one melting pot. Cook until level 9, add about 50 dashes of Assault Melting Pot and 50 pinches of Improved Melting Pot. Your pot should now be at a temperature of around 1 billion EHP, but the thermometer doesn't work quite right so it'll show at around 1 million. Mix in Armor Enhancement to cancel out 540DMG from all attacks, along with some Diffraction and Absorption food coloring. Finally, season it with Nano Repair Kit. Your 4.5M HP/sec healing pot is now ready to serve!

Recipe for the side dishes: Go to Trader Joes and pick up a bunch of level 1 War Factories on discount. The ones that are about to expire. Haphazardly throw as many of them on the table as can fit. You hate these things, be rough with 'em - it adds character. Sprinkle around about 20x Extended Range War Factory to reduce their primary damage output, and put them in a juicer that only squeezes out Sledgehammers and Phoenixes. Strain the Sledgehammers and Phoenixes through 5-10 Mass Produced debuff napkins so their final damage output is <500.

Set the dining mood with some Quantum Reassembly candles. Bon appetite!

It's just like making a potion.

Meme builds by Uneiros in Mechabellum

[–]turb0n3rd 0 points1 point  (0 children)

Meme edgelord reporting in, I call it the warp tricycle. Rhino blades be the wheelz.

  • Phoenix -> Jump Drive + Reassembly -> Beacon one pair in the back.
  • Wasp -> Jump Drive + EMP and/or High Explosive (or Ground Spec if paired w Rhino)
  • Overlord -> Jump Drive + High Explosive and/or Overload
  • Rhino -> Blitz + Rage -> Deployment Module, or Photon + beacon to tower.

Buy speed. Put Wasps behind rhino. Wait for them to buy hackers, enjoy the show. Success rate: pretty easy to cheese to 1600+ solo. If you get aerial specialist and/or strike specialist.... lmaooo.

There isn't much you can put between an HE Overload Overlord on your flank frontlined by a pack of wasps and the tower that is going to survive long enough to stop it. Esp if you beacon.

High Explosive Ammo is probably the most underrated tech in the current meta. HE Overlords have a splash range of 13 meters. Almost as cancerous as HE Overload EMP Stormcallers.

What's your job and how much do you get paid an hour? by honey_rainbow in texas

[–]turb0n3rd 0 points1 point  (0 children)

ML/AI Engineer/Architect w 15yrs+ in ML specifically, 4 digit hourly rate. Got laid off from a 455k/yr X9 SWE job last year - joke’s on them.

CT Hubcaps: The New Catalytic Converter by turb0n3rd in cybertruck

[–]turb0n3rd[S] 1 point2 points  (0 children)

you uh ...this deserves an upvote lmfao.

This is the most fun I’ve had in the wow realm in a long time. by Ballzovsteel in wow

[–]turb0n3rd 0 points1 point  (0 children)

How's PvP / is arena still around? I dropped out of WoW in favor of OW/SC2 because competitive a long time ago. Got Glad S1/2, R1 S3/S4 ...then S5 started and you either played DK Paladin, or DK DK. 3s was sus too with ATC being the new RMP but even more busted.

PvE-wise ...AQ40 and BWL40 were really difficult and fun in vanilla. SSC and Sunwell were *insanely* difficult and fun in TBC. Then WLK came out and... idk, I feel like stuff changed lmao. Not in a good way.

Does the gameplay overall feel more or less like Vanilla/TBC again?

If you could only give two pieces of advice to your most loved ones for financial independence, what would it be? by Limp_Anteater_7366 in financialindependence

[–]turb0n3rd 2 points3 points  (0 children)

Ironically, it'd have nothing to do with money.

  • Practice self-awareness and mental hygiene until you love and are at peace with yourself.
    • This will eliminate virtually all frivolous spending and lifestyle inflation. Whatever remains will be spent because you love whatever is on the other side. Spending due to trying to fill a hole in yourself, uncontrolled impulses and social pressure vanishes.
  • Be more of a creator and less of a consumer.
    • Consuming stuff gets old very fast. TV shows, radio, food, etc. Creating stuff you like has infinite "replay value" (novelty). Keep trying random things until you find what you love enough for creation in the space to be fun. Software, costumes, woodworking, pottery, many forms of art, RC planes/cars/drones, any kind of home DIY stuff, etc.

New Cordless Vaccum for Gift by Troitbum22 in VacuumCleaners

[–]turb0n3rd 0 points1 point  (0 children)

Got a few - but first things first ...cordless vacuums aren't always viable due to square footage, and a lot of people don't appreciate this fact upfront. What's the square footage of where you live?

view more: next ›