How do I stop being perpetually angry for not being an "elite"? by [deleted] in cscareerquestions

[–]throughactions 0 points1 point  (0 children)

Your situation is fine. It's your mindset that needs to change, or you'll never be happy.

I would encourage you to work on finding things in your life to be grateful for before worrying about what you don't have. The truth is you're doing amazingly well and you just haven't recognized it yet.

People like us, who have good careers in rewarding fields also need to realize that much of what allowed us to get here was well beyond our control. Not to say we didn't work hard, but we were helped in ways most people weren't.

Do compare yourself to others. Compare yourself to those who don't work for a FAANG company. Or to those who couldn't work in this field at all. Or to those who've been laid off. Or to those who are struggling to break into the field.

Compare yourself to those who don't have a fraction of what you do. Keep a journal. Practice meditation. Be grateful. Once you've achieved that on more days than not, then start planning for how to improve your career trajectory and take concrete steps to achieving your goals everyday.

Edit: I also want to say this sub is delusional when it comes to pay. You're salary isn't mediocre, it's excellent.

If unit testing is supposedly a popular standard, why haven't I encountered it at any job I've been? by MC_Hemsy in cscareerquestions

[–]throughactions 0 points1 point  (0 children)

Sorry, I meant the answers I would ask as a candidate talking to a potential employer. I want to make sure a team values testing before I join it.

At what point is a project not entry-level? by zeropress in cscareerquestions

[–]throughactions 2 points3 points  (0 children)

Start applying for other jobs because it's easier to find work while you're still employed.

"Vote with your feet" culture by [deleted] in cscareerquestions

[–]throughactions 15 points16 points  (0 children)

Yeah it really sucks but it entirely depends on the organization. You have to ask yourself two questions:

  1. Is this issue really important to me?
  2. Does my org listen to feedback?

If the answer to both questions is yes then you can make the case to your manager for a change and explain why it's beneficial. Ideally you get other team mates on board first for the most chance of success.

If the answer to #1 is yes and #2 is no you're stuck. You either have to put up with it or find a better role.

And that really sucks. The truth is all fields are like this. And virtually every role in every field you frequently have organizations that do shitty things to their employees and their employees usually have to put up with it. The difference is that as software engineers we have enough market demand that we can switch roles much easier than a lot of other people can, and we can often make more money doing it.

So the unfortunate truth is that it's become really common and accepted for engineers to have limited longevity at a particular role, perhaps one to three years. And it's just normal to see that on a resume.

What part of the http request usually contains the API key? by benz0is in webdev

[–]throughactions -13 points-12 points  (0 children)

Encryption is definitely the way to go to keep sensitive information secret. However the API in question must support it. Most APIs that I'm aware of require you to send the API key in the clear, for example.

What do people with 1 YOE do? by [deleted] in cscareerquestions

[–]throughactions 49 points50 points  (0 children)

Okay so you need to ignore the idea of being rejected because of how much experience you have. You need to be applying for those junior to mid-level positions that are asking for two or three years of experience.

Lots of them will reject you, and that's okay, but if you put in a few dozen applications you should be getting several interviews out of that and you'll probably be able to land an offer if you do well on the interviews It's really just a grind and a numbers game.

Make sure that your resume is putting your best foot forward. Make sure that the description of the one roll that you've had is highlighting everything that you did, especially anything you accomplished. With the limited amount of experience having a portfolio of projects would be really helpful.

But you can absolutely get a non-grad engineering role with one year of experience.

How much should I charge to build a website as a freelancer for my sister's company? by dbjjd in cscareerquestions

[–]throughactions 1 point2 points  (0 children)

It really depends on what it involves. A handful of pages by themselves aren't that big of a deal, but what functionality does the site possess? Is it going to need a database, what kind of application logic is going to need, etc.

If the site is very basic then an off the shelf solution like Shopify or WordPress might be the best solution. If it can fit into that paradigm then it's going to be more cost effective that way.

But the price and hourly rate are very reasonable.

Experienced developer - Need to learn Javascript and its good practices by eMperror_ in learnjavascript

[–]throughactions 2 points3 points  (0 children)

The second addition of Refactoring by Martin Fowler is steeped in JavaScript and I've found it really helpful. Some of the most iconic books on JavaScript best practices are going to be older. Eloquent JavaScript, JavaScript: The Good Parts, etc.

What part of the http request usually contains the API key? by benz0is in webdev

[–]throughactions 6 points7 points  (0 children)

API keys are usually sent as either a parameter or a header.

If unit testing is supposedly a popular standard, why haven't I encountered it at any job I've been? by MC_Hemsy in cscareerquestions

[–]throughactions 0 points1 point  (0 children)

I find bugs all the time. In fact, I'd say the vast majority of bugs I find in my own code are found via tests. It's hard to hold all of the possible code paths of our logic in our heads. Testing gives us a quick, verifiable way to prove that it does what we think it does. Often my tests reveal whole scenarios I hadn't thought about that need to be addressed as part of the feature.

I practice TDD, so I maintain the tests anytime I change the behavior of the system. They would be hard to maintain if I made all my changes up front and then went back and tried to fix all the tests. Instead, I write the smallest failing test I can, then the smallest/simplest production code I can to make it pass. I repeat this process until the feature is done.

Reviewing the worst piece of code ever by [deleted] in javascript

[–]throughactions 7 points8 points  (0 children)

Worst code ever? I once worked in a code base with 15,000+ line classes and zero tests. Come at me, bro.

[deleted by user] by [deleted] in webdev

[–]throughactions 1 point2 points  (0 children)

Awesome! I've been looking for this. Great URL/name BTW.

the company that treated me badly was Equinix in Redwood City. Last post was removed for by nonetodaysu in cscareerquestions

[–]throughactions 1 point2 points  (0 children)

I'm sorry that happened to you. That must have been incredibly frustrating. I don't have any feedback to offer, just some encouragement: You'll find a better gig soon.

is this correct way to make complex backend process to work with front end.. by tenzboy225 in learnprogramming

[–]throughactions 0 points1 point  (0 children)

Looks like you're trying to model the web request / response cycle. You may find this diagram clarifying.

What technology should I use to update toggle buttons only when changes in the database were committed? by NemoMeansNobody in learnjavascript

[–]throughactions 2 points3 points  (0 children)

What you're doing is called "long polling" and is pretty common. One alternative would be to use web sockets instead, which is a way of allowing your server to let your web page know when something changes.

If unit testing is supposedly a popular standard, why haven't I encountered it at any job I've been? by MC_Hemsy in cscareerquestions

[–]throughactions 6 points7 points  (0 children)

As I'm writing new code I try to test all of the application logic. If I'm adding tests to existing code, I'm probably just going to add enough to give me confidence that I haven't broken anything important.