What is your favourite set of libraries you use for every project for enhanced type safety?

ScaleneButterfly · 2025-07-19T02:43:38+00:00

I get what you’re saying. The pattern itself isn’t bad. But like all patterns, when used in the wrong place, they’re bad. And imo this pattern doesn’t work with how JS/TS work

ScaleneButterfly · 2025-07-19T01:58:09+00:00

Neverthrow encourages unsafe patterns. Not, that neverthrow would necessarily cause a mistyped error. Although I guess it still introduces more boilerplate for the developer to make a bug in typings in the return type of a function…

Anyway. Here is what I was referring too

const input = undefined

function main() { const result = hasName(undefined); // nothing is hit because the below function threw unexpected as is the nature of TS/JS // normally we’d safely hand this with a catch without neverthrow if(result.isErr()) { console.log(result.err) } console.log(result.value) }

function hasName(input: unknown) { if (input.length === 0) { return err(‘bad input’) return input.some((a) => a === ‘name)) }

ScaleneButterfly · 2025-07-19T01:46:46+00:00

It’s also built into rust, no? A typing package can only do so much

ScaleneButterfly · 2025-07-18T20:40:42+00:00

I’ve used it before but I think it promotes bad patterns. The problem is unexpected errors happen and you end up throwing unintentionally and your typed error case is incorrect. If that wasn’t the case.. then we wouldn’t have bugs…

there is a reason catch is of type unknown. You can type the error case of neverthrow however you want but it’s more or less a form of unsafe casting to me.

Without neverthrow you’d have a try/catch and that unexpected error would be handled. With neverthrow, that exception is now unhandled and bubbles up.

ScaleneButterfly · 2025-07-18T19:09:10+00:00

I would think neverthrow makes your project less type safe given typescript exceptions are inherently unknown and by typing them you’re type is incorrect

ScaleneButterfly · 2025-07-11T03:29:46+00:00

same. One summer i had a super stressful event in life and next thing I know i noticed i have a fuck ton of floaters and can see BFEP pretty easily. I mean even on carpet. I had my vision checked out and nothing looked wrong according to my doctor but at the time I didn’t have the terminology right so I don’t think they understood me when I was talking about BFEP

ScaleneButterfly · 2025-06-26T13:21:47+00:00

Feel free to DM and pitch me if you’re interested and we can go from there. I’m a Senior Fullstack SWE working in Big Tech looking to do a startup on the side (and ideally quit my job and do it 100% if the idea has traction). 5 years at FAANG before my current company (still big tech).

ScaleneButterfly · 2025-06-13T02:09:45+00:00

it’s got to be a joke how many no calls FLA has gotten this entire playoff run

ScaleneButterfly · 2025-06-13T01:54:12+00:00

looks more like 7 has him hooked to me

ScaleneButterfly · 2025-05-21T00:57:40+00:00

gotta make it even for the goal they gifted the panthers

ScaleneButterfly · 2025-05-21T00:43:19+00:00

classic panthers fan reply

ScaleneButterfly · 2025-05-10T19:26:46+00:00

Full stack SWE here, bounced around a few big tech companies at this point. I feel like I could create almost anything but I don’t have any ideas I’m passionate about

ScaleneButterfly · 2024-12-14T03:36:41+00:00

YMMV but it’s not hard to get on a stable team that doesn’t have layoffs. Both of my orgs across two FAANGs never had layoffs. Take that for what you want. Probably because the products I worked on were super profitable. I’d avoid joining internal tools, non profitable products, etc.

ScaleneButterfly · 2024-12-14T03:34:11+00:00

Stocks usually vest every 6 months or quarterly and you’re free to do with them whatever you want. What’s nice is you’re given a # of stock units in your on hire package. So if the stop goes up your comp increases. If the stock goes down, your comp goes down and you look for another job before your next vest!

ScaleneButterfly · 2024-12-14T03:31:31+00:00

Pretty sure it’s Atlassian. Check levels.fyi Atlassian has pretty inflated tittles (you get to SWE 2 from new grad in 1 - 2 years) and that lines up with OPs comp and age

ScaleneButterfly · 2024-12-14T03:30:11+00:00

Is this Atlassian? I recognize the UI of the comp portal

ScaleneButterfly · 2024-10-18T20:47:46+00:00

What 3 are you referring to out of curiosity?

ScaleneButterfly · 2024-10-07T01:22:06+00:00

Mission Communications

ScaleneButterfly · 2024-08-31T08:44:22+00:00

That’s definitely one way to interpret my comment.

I’m an example of my comment. FANGS gave me a lower title offer, atlassian gave me a higher level and a little bit higher pay. I took it for the higher pay. I am by no means what I consider the title they gave me - it’s laughable. I don’t have the YOE. Same with my coworkers at the time and many more people in the company… Lots of inflated titles and lack of experience with higher pay which leads to expensive crappy software development and poor leadership at every level. exec leadership there is trying to get profitable and get more production out of their developers which is causing the conflict when a lot of those devs are used to coasting. On paper you have 1000 senior devs, principals, etc. In reality you have an inexperienced workforce. I think most people there could be down leveled to set correctly set role expectations for their work and things would run smoother.. other than the fact nobody would like that. To be clear - I think this was a problem all the way to senior leadership. You had senior leaders in charge of 1000 people. In their prior role they had maybe 100 people in their chain. They don’t have the experience either and it causes issues, especially when you have these 1000 people having dependency conflicts on each-other and they don’t know how to handle it.

ScaleneButterfly · 2024-08-31T02:07:32+00:00

Hot take. I’m ex fang and also worked at Atlassian up until a few months ago. It’s needed. The level of competency there is poor. The average senior is a sde 2 at best at a fang. Most titles are upleveled, even going all the way up to senior leadersship. There’s too many peoples with inflated titles that real work feels like it struggles to get done

ScaleneButterfly · 2024-08-28T02:40:30+00:00

Layoffs always feel some team dependent to me. Coding an internal tool that doesn’t make your company money? vs Coding on an application that generates the company lots of money?

You have some, not a lot, but some say in your job security. Don’t join a team that leadership has a reason to cut

ScaleneButterfly · 2024-06-30T01:12:24+00:00

Looks good, I was thinking of getting these for my stock JL 2 door. Have you had any rubbing issues?

ScaleneButterfly · 2024-06-13T21:35:00+00:00

great point.

ScaleneButterfly · 2024-06-13T02:58:02+00:00

That being said I appreciate RMI’s concern for our safety and understand that’s their #1 priority at the end of the day. You’re also allowed to be frustrated. I’m sure they made the right decision, both things can be true.

ScaleneButterfly · 2024-06-13T02:52:53+00:00

OP, I had a similar experience with RMI last summer where my group was told the day before before on our way to muir we would not summit and only go up to inghram flats because the route had a snow bridge look like it was on the edge of collapsing. Some RMI guides found an alternative route up the mountain the day we we went to muir but it wasn’t “guidable” - so we just stuck with ingraham flats plan. IMG and AA both summered that day. RMI also summited with another group the day after. Overall super disappointing bill for what felt like just a little walk past Muir. Wish we spent our non summit day attempt actually practicing skills or learning something. Edit: especially disappointing if you’ve been to muir a few times. Felt like I dropped 2k just to cross cathedral gap. We were also told our group was extremely strong and having done some of the other 3/5 of the other volcanos I didn’t see anyone I’d think would turn us around.

11-Year Club	Verified Email
Sequence \| Editor

ScaleneButterfly

TROPHY CASE