General Physics was like that. Probably my favorite course ever. It completely changed the way I look at the world.

One other thing to keep in mind, I think the claim that University courses are being watered down is a timeless complaint made by past students and professors since the beginning of time.

It use to be that removing low-level programming (assembly/hand assembly) or pointers from the early CS curriculum was going to lead to all these dumb unprepared students. I don't know if that's still a thing, but I haven't heard about it as much lately. Material that should be covered evolved and I'm sure it almost always involves removing some 'hard' material that some people think really needs to be covered.

Haven't read through the thread, but this seems interesting to a bunch of people.



https://twitter.com/jackiehluo/statu...80060096401408

hmm, those salaries seem pretty low to me. guess I am about in line.

I was a little surprised that the bay area salaries were so low, I expected them to be much higher than mine, but most similar ones seemed the same or lower.

As I've learned more I've come to realize TypeScript is awesome and while at first i found the hype around it kinda confusing I'm seeing now why it's so good.

Can you elaborate on what you like?

Yeah I thought a 5 year big 4 engineer was making more than that. Makes me feel better.

I just found out I can see my Mac's saved wifi passwords in the keychain app. Yay!

So annoying when your mac still connects to some previous network, but you don't know the pword anymore and you can't get your phone or another device on it.

Those 2 statements don't really go with each other, and have never experienced the latter due to the former.

I see a buddy of mine in KC once or twice a year. My mac remembered his network, but my new phone didn't know the wifi. He couldn't remember his pword and didn't know where it was stored. Actually he thought he remembered it as 92FordTempo. But after a ton of trial and error we figured out it was 1992FordTempo.

I didn't know I could actually view the remembered wifi passwords somewhere on my Mac.



It's tip #10 @8:25.

Part of software engineering is the constant struggle to be as efficient as possible and provide as much value as possible. This is one of the reasons for the rise of devops, containers, etc. Have your devs building product and providing value for customers and not fighting with their tools. It's also why no one would ever use vanilla JS and manually deal with browser specifics.

TypeScript may require some extra work up front, but it removes an entire category of potentially time consuming and tough to debug errors. It also makes it way easier to understand APIs between functions, and internal code when you are coming into an existing project cold.

Imagine getting up to speed on two legacy JS codebases. One is in TS and one is in vanilla JS. Its gonna be way easier and you're gonna feel more confident making changes in the TS codebase. To extend this, imagine if test coverage is bad/ non existent in each.

Nothing is stopping you from not using TS and just hacking in vanilla JS at first and then adding TS later when you wanna make what you are doing more robust.

Getting up to speed on a new codebase or 3rd party API makes a lot of sense to me.

As far as catching errors that are hard to debug - I've yet to run into a run time error in practice that typescript would have caught, which wouldn't also be caught by a good linter. I am sure they exist. But personally that's not a big selling point for me because it's never come up on apps I've worked on.

So for me it's:

Positives - auto-complete, getting up to speed quicker, and stuff like being able to quickly see all the properties in a default properties object that's been extended from a framework and added to

Negatives: hate the compile step, harder to debug w/o a good source map - which apparently is tricky with node, weirdness with 3rd parties where you have to hack up an object - I saw this with Angular 2 HttpProperties object

I think it might be worth it but it's far from a slam dunk for me. I worked with it for a while with Angular 2 and a node app - the light bulb never went on for me that this is better. Usually even if I resist at first, if something is clearly better I feel like I eventually get it. Maybe I just need to work with TS more.

Things I like about typescript (some of which are not unique to typescript, to be clear)

- Targeting ES5 while writing ES6
- decorators
- the flexibility of types and their optional use
- tslint is very configurable
- Feels very natural with webpack

Things that are sometimes a bummer:
- out of date declarations files for third-party libs
- I've had a few hard to figure out issues with source maps not working, at this point the solution to which is just "use Chrome"

At first I suspected that the fact that typings are bolted on would lead to a bunch of goofy workarounds or problems. And it does take a hot minute to get used to some of the ambiguities of compile-time vs run-time typing. But in the end I feel like the flexibility allowed by the underlying language being untyped is actually pretty useful. It lets you choose where you want to be very specific and also where you want to avoid painful overhead when writing code if it's not valuable.

With decorators I've been able to fairly simply build an extensible data model layer that serializes/deserializes JSON from an API endpoint into class instances where stuff like inflating local DateTime objects, skewing to the user's timezone, handling metadata, and other assorted goodness is really easy, so I'm enjoying decorators mostly as a way to do mixins, but there are some useful traits of property decorators that goes beyond some other simpler types of mixins. There are a few things about decorator metadata that I wish they would do slightly differently but it's been very useful, and we have to use that feature for angular anyway.

Some of the things I'm enjoying for front-end dev specifically probably rely on the confluence of webpack+typescript, more than typescript by itself, also.

What are some examples of this? I struggle to find the value in TS but tbh I've never really have given it a try. Its just that I don't have type problems in javascript. If I eff up something it gives ye olde "foo is not a function on line bar" and off I go to fix it. I know what types are because I know what I'm calling and with what, and if I don't, I use JSDoc on the more complicated functions. I don't get TS at all.

Salaries are interesting, but they're not apples to apples. No one mentioned how many hours they're expected to work, which can vary from 40 to 65.

Also, is she trying prove/disprove gender equality? If so, this seems very unscientific.

She should also store this in a database. Most people are only going to read a subset of the topmost tweets.

I think the goal is to provide information so women have targets for their own negotiations. Of course it's useful to men for that also.

I haven't come across the bugs either but my friend (who is a great dev with ~10 years exp) has run into a couple.

One was in a legacy codebase where they were doing a typeof and then checking for truthiness. Well in very rare circumstances this typeof was being passed null.

Another was someone typod or somehow removed an essential property on an object and merged the code into prod. In this circumstance he figured there must be a circumstance in runtime that caused it so he spent an entire day tracing everything before realizing a senior engineer had removed it in a PR the days before when hmy friend was on vacation. He felt dumb he had only read the PR descriptions to see if they touched this area of code and didn't look line by line, but that this was a purely destructive move with no explanation unrelated to the PR (perhaps a debugging artifact, etc.).

But both of those saw code go into prod that would have been caught by a type system and from that (and knowing he works with generally considered great developers) I imagine in the wild there is a whole lot of time being wasted on similar stuff.

This right here is great.

You can say "alright this code here is going to be rock solid" and other places you can be like "this is a work in progress/ there may be dragons, etc."

The rock solid part is very helpful for building robust products.

...And what fraction of the day you actually work lol.

software engineer, six months of experience (bootcamp grad), new york city: $160,000, plus $55,000 bonus
----
senior software engineer, seven years of experience, startup in san francisco: $150,000

lol

Top one could be Netflix.

Where do you go for code reviews? Is there some site that charges to have code reviewed for a small fee, think "take home assignments". Stack Overflow has a place that you can post code reviews but it's not very active/busy.

I know of no system other worth a crap other than leads reviewing all pull requests.

That includes the old pre-git days of wandering though code on a shared screen - trying to figure out what changed.

Right now anyone on my team can review and approve and merge PRs.. think I need to change that. I'm only lead of 10 though and don't really want to do review all day but uh its better than some of the crap that's been getting through lately. How hard is it to not use the ****ing return keyword in javascript arrow functions?