Please stop calling yourselves Engineers. You're not. The worst devs I know are the same ones who insist on calling themselves engineers. How many times have you heard "move fast and break things" at your job? I've heard it a million times. That's literally the opposite of what an actual engineer does. When a real engineer builds a bridge, he doesn't just take out his hammer and start building the damn thing. He doesn't just start building and hope the thing stands up by itself someday. He doesn't say "some guy online told me about a new framework (Plastik, current version: 0.3.1-Alpha) for making the beams out of plastic and I want to try it out on this bridge to see how it works" and then just casually start using it halfway through construction. He doesn't say "I don't have time to test this" or "following a consistent architecture isn't important." He sure as hell doesn't say "let's just release it and see if it breaks, we can always fix it in the next sprint." But you spent hundreds or thousands of hours on leetcode learning about architecture! Well the cook at McDonald's has spent hundreds or thousands of hours flipping burgers, but that doesn't make him a Burger Retroversion Engineer. It makes him a burger flipper. To be called an engineer in a traditional field in most states you need to get a degree, pass a licensing exam, and work under an experienced engineer for several (4+) years. To be called a software engineer... You don't need anything. You just start calling yourself one. Like a janitor who just decides to start calling himself a Contaminant Removal Engineer. You're that guy. Good job. Are you happier with yourself now that you're a fake engineer? Are you confident that in the unlikely scenario that someone's life depended on your code, it would work as expected? If not, you aren't an engineer. So stop calling yourself one. You sound like an idiot. There are plenty of other words you can use. Software developer. Programmer. Hacker. Pick whichever one you like best, or make up your own. Edit: I'm getting a lot of hate for this so far, so i want to say, yeah, I know it's aggressive but I just reviewed my coworker's code from Friday. It was: 1. A switch statement with only one case 2. Wrapped in a for loop with a break statement at the end so it only looped once 3. No edge case handling 4. The meat of the code was obviously copied directly from stack overflow And THEN when I commented on it he insisted he was an engineer, and knew what he was doing. For fuck's sake. I never facepalmed so hard in my life.
having a bad start to a week ese huh..
Someone has a case of the Mondays.
People tend to be angry before breakfast. A donut usually makes it go away
If you are in SF you can also try an avocado toast. Works great for me. Just like my software.
OK. I don’t usually ask for TC YoE but you are asking for it. Large corps pay good money to most of the people here even if they are some sort of containment removal specialists. I guess thats all that counts. I mean sculptors do impressive stuff too
~12 yoe, tc varies as I'm freelance but between $100-200/hr depending on the client.
Read about hacker ethics and you will understand this mentality. “Move fast and break things” is a fundamental trait of how to iterate quickly in a modern internet company and the field of engineering is evolving to be more software centric which by nature complements “moving fast and failing fast” mentalities. You’re a dumb fuck who seems to be struggling to adapt to your surroundings
I hope when the algorithm you're working on for the brakes in that car fails fast it's not the car I'm driving.
@OP Automotive software development is completely different than consumer application development. It’s like comparing Mars and Jupiter. Two completely different planets development wise with hugely different QC requirements. Nobody is releasing untested software controlling your brakes. That’s a good way to go out of business and/or go to jail.
Title is just what the companies use. I personally don't care at all.
I've heard this silly argument a million times. We are engineers. However our constraints and assumptions are different. Imagine how bridge construction would be if small changes in user experience increased your revenue by X %? Or if the bridge client demanded X features to be added to the bridge in 2 weeks? Or if the bridge suddenly experienced 1000x traffic during one weekend because it went viral? In an environment where the cost/time of changing the bridge structure is low, it doesn't make sense to waste engineering time/resources to "overengineer" the bridge.
imagine a bridge in a constituency which seeks income. toll booths appear, then fadtrack booths, then bypass lanes...sure sounds like posr delivery features for revenue generation
That's actually exactly what happened to our interstates in metro Atlanta. And you know what? The UX was much better. If you are late for the airport, you can pay $6 to be in the fast lane. Dynamic pricing based on supply and demand yo.
Ok
Yea
Tech Industry
4h
440
Ever wonder how a few of your coworkers got hired in the first place?
Tech Industry
13h
3423
11 offers to laid off[UPDATE]: 5 offers
Ask Blinders
Yesterday
1493
Top red flags in guy to see before saying yes to marriage (arranged)
India
Yesterday
660
Duniya me Vishwaguru ka Danka
Personal Finance
Yesterday
1393
Are we ready to buy our forever home?
Wow, get some coffee and chill
Yeah it's aggressive but I just reviewed my coworker's code from Friday. It was: 1. A switch statement with only one case 2. Wrapped in a for loop with a break statement at the end so it only looped once 3. No edge case handling 4. The meat of the code was obviously copied directly from stack overflow And THEN when I commented on it he insisted he was an engineer, and knew what he was doing. For fuck's sake. I never facepalmed so hard in my life.
lol that's just bad engineering...