I know because I know? Not sure how to answer that, but I'll take a stab. Based on your asking the question, it would seem that if you see indented code of your own you know you are either in a loop or a conditional. When I see indented code of my own I know that I'm in a loop, a conditional, or file I/O.

I don't believe it's FPS at all, and I believe it stems from the fact that, around 25 years ago, I had a teacher that very forcefully ingrained on us students that, when we're dealing with file I/O, we get in, and we get the hell out of the file as soon as is absolutely possible. So the indentation is a reminder that, hey, we're working with a file right now, so every line of indented code here better need to be done while the file is still open, if not, move it up to before the file is open, or down to after the file is closed.

I was thinking something else, what jj showed looks standard.

I was just sort of kidding to be honest (Python humour is the best humour).

I'm not really sure I like the general approach of indenting when the file is open. But I guess the idea is reasonable. If you're dealing with something where it really matters it might make more sense to structure your code in a way that makes it clear what to do.
Something like you open the file, pass it to a method that does whatever its suppose to do, and then immediately close the file after.

Code "showing a file is open" sounds to me like it should be it's own function. If for any reason you don't want to do this, privately scope it within the method is what I'd do if it's not naturally done already (eg with a using(){} block)

How do you guys feel about else if's on the same vs next line as the previous ending curly.

As in this:
vs

I've always been a staunch proponent out of the latter, but I think I get the argument for the former.

For me, the latter, since I want to see the if and corresponding else words to be vertically aligned.

Former. Definitely the former.

Obv.

also: remove the damn braces

Sometimes I feel like a ******. Spent 3 hours trying to figure out why my local DynamoDB instance wasnt working, I was giving it dummy access tokens in 2 spots, with 1 character different, which apparently means it was writing to one spot and reading from another... Sigh

NYC bans employers from asking interviewees about previous salary

I was surprised to see that Philadelphia and the entirety of Massachusetts already have laws against that, didn't know it was a thing.

Also, Slack switched to TypeScript and they love it!

Contract and contract to hire salaries should be higher than the corresponding positions salary to compensate for no benefits shouldn't they? Had a place offer 3k a month for a 3 month contract to hire position, for someone with 7 years experience in the role how ridiculous is that?

Dude I got offered 65/hr by charter. And they stink. Def keep looking

uh $36,000/year are you serious? "I'm not a good fit for this role sorry".

Yeah, I thought it might have been a typo or something but they doubled down on it and then gave a cap for the position that indicates they are looking to pay Tier 1.5 support money for a senior support/operations role. What's got me confused is that I was referred for the position by a member of their board, so I don't know if they aren't interested but want to tell the board member I said no or are just clueless in hiring.

Gonna go totally out on a limb and guess whoever is involved in hiring/budgeting that role has experience using offshore support and is using that as a basis for their target.

I could almost convince myself someone competent could be paying 1/4 that a month for offshore and is trying to do a conversion.

But I think you should obv tell your friend on their board that they made a lol lowball offer and it seems like they don't get it. He should know that if he's referring people to the position and gives a **** about the company.

yeah, I have an email set for when it's finalized that I'm going to send him. I'm of two minds sending him something while negotiations are still going on, seems like snitching and a bad way to start off in a <20 person team to go over their head to the board, but no way they're going to get quality devs doing this ****.

We pay our good interns more than that.
Hell, at my last company we paid our data entry people more than that.

Yeah, I sent an email to their CEO and my Board member friend to point out their processes are flawed and hopefully restart the conversation above this guy who was doing the hiring. Doubt it will do much for me but maybe they'll fix their process before they are trying to hire developers.

First project was due yesterday at the bootcamp. Had to build a basic crud tic-tac-toe app.

Ended up helping a lot of people with theirs, figuring out how to build required features with various unique implementations of simple concepts really helped my understanding immensely.

We have to use spaces at a big company with a lot of churn and outsourcing. Otherwise someone will pollute the tab-based indentation with spaces. You have to become the space police. Well this was pre-CI/CD w/linter days. I guess we could do it now but it's too late.

did you build an AI for it? I actually just did that as an exercise for fun.

I didn't build an AI for it, because I had limited time, but I did read into some potential strategies for building one.

Going to keep improving the code and also try and add one. Seems like it would be pretty fun.

i may clean up the code and start a thread about it, with the aim of golfing it, conceptually if not in strict lines, and using it as platform for exploring various js paradigms. would there be any interest in that?

I'd be interested in seeing that