221–230 of 316 posts
Earlier quoted context omitted.
High level IC at big tech can get you around that neighborhood
For the guy that asked, IC means integrated circuit. No fucking way they would give that money to a meatsack.
Earlier quoted context omitted.
I briefly worked with a software engineer who was making about a million dollars a year. I mentioned that an approach would be a lot of work. His response: “It’s just typing. Typey typey type (makes fingers on keyboard gesture).” Absolute lightbulb moment for me. To become a senior engineer is to realize that the code writing part is inconsequential as long as there are no technical unknowns in the work. It’s freed m…
I have to ask: how do you work as an eng who pulls in $1m/yr?
I know it's unbelievable for those not in one of these companies, but this data is accurate: https://www.levels.fyi
Earlier quoted context omitted.
I briefly worked with a software engineer who was making about a million dollars a year. I mentioned that an approach would be a lot of work. His response: “It’s just typing. Typey typey type (makes fingers on keyboard gesture).” Absolute lightbulb moment for me. To become a senior engineer is to realize that the code writing part is inconsequential as long as there are no technical unknowns in the work. It’s freed m…
I have to ask: how do you work as an eng who pulls in $1m/yr?
I make over $1m as a SWE. “Senior Staff” or “Level 7” role at a big tech company everyone knows.
I mostly write code! I am way faster than most others here, and I have encouraged and mentored the people on my team to be similarly efficient.
I also help decide technical direction but it’s far from the “architecture astronaut” stereotype that writes no code.
It’s an infra team so no significant influence on product direction, other than considering our frameworks and tools products. I do consider them in that way, but it’s still a big difference from being involved in the direction of the external product.
Writing code is the basic 101 of our industry. Anyone can write a loop or an if statement. With todays computing power, for most applications even poorly written code will run and will execute quite fast. What makes someone a 10x (and i hate that term) is the ability to take requirements, or better yet, a vague idea given to them by the business and turn that into software that benefits the end user and makes the com…
RE>> Anyone can write a loop or an if statement. I had an intern a few years ago -- recent college grad in CompSci. I tried my best to lightly mentor him. One day I was talking about the diff between a compiled language and scripting, mentioned REPL. To demonstrate REPL, I opened up both the windows CMD prompt and the Chrome Developer tools. I mentioned that with a REPL like the Chrome Tools, it's trivial to do FizzB…
How did this person pass a technical interview?
Earlier quoted context omitted.
I'm aware that I'm in the minority here, but I find that investing heavily in being able to type fast and handle the tools well actually changes what code I write and not just how quickly. The faster I've gotten at moving code around, the more subconsciously willing I've been to try something with a modest probability of working out, and more importantly the easier it's gotten to throw away a draft that isn't working…
a good programmer is almost certainly a fast typer of course a fast typer does necessarily make a good programmer
Earlier quoted context omitted.
I briefly worked with a software engineer who was making about a million dollars a year. I mentioned that an approach would be a lot of work. His response: “It’s just typing. Typey typey type (makes fingers on keyboard gesture).” Absolute lightbulb moment for me. To become a senior engineer is to realize that the code writing part is inconsequential as long as there are no technical unknowns in the work. It’s freed m…
I have to ask: how do you work as an eng who pulls in $1m/yr?
(yes, I've read them all because I can't believe almost everyone missed the point)
The point of the article is actually neat: a small shell (Fish) script to send query to ChatGPT or DALL-E and get response back in the terminal. As a terminal user myself, this is really nice! (I rewrote it for myself in bash which I use, but used the curl command virtually as is)
The post itself is hilariously over the top (1000x c'mon), quoting 50 Cent and including statements like:
> Unfortunately, due to inflation — real and imagined, 10X just won’t cut it anymore. We need bigger gains, bigger wins, more code, more PRs, more lines, less linting, etc...
Either people really need to be pointed out the sarcasm these days, or everyone's just philosophising about the title (I'm willing to bet it's the latter).
Earlier quoted context omitted.
Unfortunately people thinking they are overall worth 10 to 1000 times their co-workers exists.
I have had coworkers that were 10x more valuable than the other coworkers. If you haven't then your company probably only employs people that are incredibly talented or incredibly mundane
Putting an actual individual factor on it and especially on engineer productivity, like we were at a line factory producing everything in a repeatable and measurable way is more questionable. 1x, 10x, 1000x? People here are discussing 10x becoming 2x, it sounds very mathematical. Now if there is an actual scale with an industry baseline and an individual measurement, I'm more than interested to learn about it and I think employers should fairly compensate engineer based on the scale factor you would put on your CV.
Being efficient at writing code can barely make someone a 5x engineer. A team of people who write code effectively is easy to do. Hyperproductivity in software is all about deciding what problems to tackle. Richard Hipp isn't worried about chipotle restaurant orders in golang, he's worried about how to store data reliably. That isn't a coding puzzle that ChatGTP is likely to help with. Either ChatGTP can do the whole…
I think code-generation is a red herring. I'm more interested in things like: - Explanation/research ("how does this work?") - Code analysis ("tell me if you think you see any bugs, refactoring suggestions, etc in this sprawling legacy codebase") Things that feed into the developer's thought process instead of crudely trying to execute on what it wants
Being efficient at writing code can barely make someone a 5x engineer. A team of people who write code effectively is easy to do. Hyperproductivity in software is all about deciding what problems to tackle. Richard Hipp isn't worried about chipotle restaurant orders in golang, he's worried about how to store data reliably. That isn't a coding puzzle that ChatGTP is likely to help with. Either ChatGTP can do the whole…
Define “efficient at writing code”. I find that for many people this means something primitive and absurd like typing faster or remembering things better. Being efficient in the perspective of writing new automation so you don’t have to do the same manual things again can easily make someone a 10x (or greater) engineer. This typically means writing your own tools and not hoping some third party package or framework w…