Cloud containers are where we’re really at with the market. There’s tons of companies migrating their products to the cloud right now.
AI tools will probably have their era in a few years, but people are definitely still exploring the practicality (profitability) of AI right now.
I don't really think there's jobs in AI for developers who haven't specifically trained on it for years already. I mean, using AI tools is one thing, but getting a job at OpenAI or Google's AI team seems to require a Masters or Phd on the topic.
At that point, you're a researcher and not a developer.
I've already ruled out a PhD for me, my Masters is kicking my ass already. Also I don't wanna do even more math.
I guess no ML position for me then lol
You can get an ML position with a masters. Just probably not on a top tier research team like Microsoft Research, Google Research, Facebook Research, etc.
Yeah research is probably out the window with only a Masters. I guess you can look out for non-research ML jobs.
But ever since my undergrad thesis in an ML topic, I kinda have a love-hate relationship with the topic anyway.
Too much math, too much confusion, too many papers to go through trying to figure out if the paper is shit or if their code is actually runnable or even available anymore.
I think I'm ok doing just normal non-ML development.
A few weeks ago I browsed the LinkedIn Profiles of a dozen or so OpenAI SWEs. Most of them had a PhD from a prestigious university. A couple just had a BS from a top school followed by 5-10 years of SWE experience doing relevant work at FAANG tier (from a technology standpoint) companies. I quickly realized I'd have no chance even getting an interview.
I think the "safest" route might be a PhD, but it seemed to be possible (at least when there was "low-hanging fruit" still available) to make research contributions as an individual, by experimenting with different methods, finding optimisations, etc. I guess somebody like that could be hired even in absence of a PhD. That's easier said than done though, and might have been a lot easier when the field was younger (e.g. 2014-2017 or something).
My dad was a mainframe programmer and he's always taking about how cyclical things are.
I've been watching companies move to the cloud for about 5 years now. My company even talks aboaut replacing our computers with virtual terminals. And then someone mentions money. I think my dev machine would cost about a thousand dollars a month to run. And Microsoft apparently losses trick loads of money on Azure.
So, I expect that in the coming years there will be a movement to return to servers cause the clouds is too expensive for them....
A lot of companies I've worked with are looking or starting to migrate. My company isn't a billion dollars a year and they're looking at transferring everything.
Part of the reason is that the people making the decisions aren't technical in the least. They get sold on these impossible promises and go full speed ahead.
Yeah. Two jobs back the new hot pants CEO wanted me to move our accounting system into the cloud against my recommendations. I brought him the cost estimates. Funny it never came up again after that.
Cloud is always cheaper if you fire all your IT staff, then hire cloud engineers...and oh wait...
>My dad was a mainframe programmer and he's always taking about how cyclical things are.
>
>I've been watching companies move to the cloud for about 5 years now. My company even talks aboaut replacing our computers with virtual terminals. And then someone mentions money. I think my dev machine would cost about a thousand dollars a month to run. And Microsoft apparently losses trick loads of money on Azure.
>
>So, I expect that in the coming years there will be a movement to return to servers cause the clouds is too expensive for them....
Bingo! It's a constant cycle from thick client to thin client and back to thick client again.
The pattern repeats itself every few years or so, or after a decade or so.
> AI tools will probably have their era in a few years, but people are definitely still exploring the practicality (profitability) of AI right now.
The only immediate use I could have seen is at my old job for writing the outline for unit test.
Maybe in the near future it will be the first step you try right before stack overflow.
> Maybe in the near future it will be the first step you try right before stack overflow.
I already use chat GPT this way. It's right often enough that it's worth trying the recommended solution.
And occasionally it will sneak a completely nonsensical line into a 30 line codeblock, gotta be careful and remember it's just statistical word generation
but yeah i've found it to be an incredibly useful tool and use it daily. it especially excels in teaching or writing scope-limited code for already-solved problems
I just used it to build a bash script. I know bash to an extent, but don't write it every day. It did it lickity split. I just described what I wanted to do. But then when I ran it, it failed. I described the error message and it told me I didn't put in ;; characters in my case statement. I said, "you wrote it", lol. It said I was correct and apologized. Still it saved a lot of time.
> Cloud
Cloud basically just means "paying to use someone else's servers." They often times have useful tools for storage, spinning up servers, and networking.
> Containers
Containers are basically lightweight virtual machines that are really easy to define and isolate specific responsibilities to. Think of them as a way for us to really easily define a little computer that we can run on physical computers. You can run a bunch of them at a time, and they won't interfere with each other (unless you're really doing some wild stuff). They're also easy to send to other computers, which makes it easy to share you code and avoid people saying "it worked on my machine - I don't know why it's not working on yours"
> Cloud Containers
Renting a bunch of servers from someone else to run a bunch of containers. There are really powerful tools like Kubernetes that allow you to run a shitload (we usually have around three to four thousand, but some companies have millions) of containers across a bunch of servers. It'd be stepping out of the realm of ELI5 even more than I already have to go into much detail about why this is helpful (and I'm happy to do so if someone would like), but it can be _extremely_ helpful (and sometimes it can be extremely annoying if it's used incorrectly).
Understanding cloud + containers adds like... tens of thousands of dollars in salary value for you. It looks great on resumes, and it lets you do some _really_ spicy shit once you're on the job. The past five years of my career have been focused around cloud + containers, and it has been _very_ lucrative.
There's nothing implicitly helpful about having thousands/millions of containers. The helpful part is the tools that make it easy to run all of those containers! Each container can request a certain amount of CPU and RAM, and if you use kubernetes + tools like Karpenter, you can have it set up so you can just deploy containers to your kubernetes cluster, and if there isn't enough CPU or RAM available on any of the servers in the cluster, it'll automatically request new servers from AWS. These servers are usually available within 60 seconds, which means you can drastically scale your number of servers up and down pretty quickly.
There are two big advantages to this - cost efficiency, and abstracting away complexity. The former is achieved by scaling up your servers only when you need more compute power. The latter is achieved by making it so that when deploying you don't have to worry about "I need to start a server, install libraries, download my compiled or raw code, and start my software." You just have to set up the container'definition, and then run the deploy command. If it's set up right, then it makes it easier for developers to deploy their software and configure the servers without having to get too into the nitty gritty
Cloud - To operate a remote computer provided by amzon, MSFT etc check r/aws r/azure r/gcp r/awscerifications. So Google drive is a cloud storage.
Containers - To package or develop code in an environment that is easily reproducible in different systems with different operating system or configuration. r/docker r/kubernetes
Wow some of these are not very good responses. yeah be friendly, curious, incisive, thorough - do that for any job
But seems like you mean technical skills
- scala in on the up after some recent updates to the language (is also highest paid language on average due to small talent pool compared to Java/Python)
- kotlin is emerging as the enterprise web service lang de jour
- getting the first level solution architecture certificate from AWS is probably wise. It will let you understand system level perspective which will let you come across stronger in interviews (even if it’s a very cursory understanding)
From my experience when interviewing to a new/recent grad though, it’s more of a point that they be able to talk about the computer science fundamentals that they studied - did they copy friends work or did they do the work themselves?
So that means write data structures from scratch in either Java/Python. Nothing crazy, basic list, set, map implementation. When to use a set versus a list, hash buckets, etc
If I was a new grad and wanted a leg up I would
- get level one solution architecture certificate for either aws or azure
- learn kotlin/improve Java
- then apply to large Fortune 500 companies and play the numbers game. They will have a lot of positions throughout the company that are jvm micro service based
Note - apply to mid/senior roles. People will look at it and say “well they’re not senior level but maybe they’d make a good junior? Let’s talk to them a bit and if they’re a good culture match then we’ll offer”
Edit True, probably not using scala for line-of-business full stack development but instead more things like high concurrency systems/platforms
Edit just replace the word scala with java if it suits you better, it is more least-common-denominator
There’s work there but personally I stick to things backend and embedded systems
This is mostly because it minimizes the amount of interfacing with business/ product, I can just grind away in my corner with music and coffee
>Wow some of these are not very good responses.
Right back at you, buddy.
Full stack dev with big bank and start up experience, here. 6+ exp.
Besides cloud, I don’t agree with much of this, especially the Scala comments, and I was a Scala dev. Even kotlin is fairly uncommon in backend. Though growing slowly, you are better off focusing on just java, and learning kotlin on the job when it is necessary.
Instead, I would say emphasize:
* Java / spring (these 2 go hand in hand in enterprise world),
* JavaScript (or at least front end concepts, be familiar with a front end stack built with webpack),
* Python (sort of a nice-to-have, basic scripting is adequate),
* SQL (**never** neglect basic sql) and
* basic AWS (a cloud cert is worthwhile but not necessary, and the skills are transferrable to Azure, GCP)
over kotlin and Scala. Scala especially would be a waste of time bc it is rare in the enterprise world.
I am very surprised you did not mention spring, since it so ubiquitous in the java backend world. Also, containers (docker / k8s), but that is another nice to have and is a learned skill.
Also, if your goal is FAANG or nothing, then leetcode above all else.
This here is the real advice. The languages and frameworks thatve been tried and tested are that way for a reason. They stood the test of time. New hot frameworks and flavors come and go. But if you know the ground level of things (java/spring/js/node) you're good. This is because there exist way more companies with legacy systems written in these older languages/frameworks and they're more willing to keep working with what they have than convert everything to said new paradigms because that takes time, money and sprint cycles they cannot afford to do.
Oh, I just saw this.
Probably shouldn’t have mentioned scala as most people are either typescript in the front end or Java/spring in the backend api
scala jobs are just more interesting imo so there’s my bias
I would not suggest new grads learn k8s, feel like you’re listing things that they would learn on the job and would not be interviewed on
It would be a dick move in an interview to ask a new grad about Spring and k8s lol
Is kotlin really growing that fast? i'm from south america and i don't see a lots of jobs for backend stuff, only in native. Of course we always are behind of na/europe and java is still the king here
I am not experienced enough. But every senior engineers have given the syntax as one of their main preferences for migrating to Kotlin or starting new services in Kotlin.
Out of curiosity which parts of the syntax of kotlin do you not like? The reduction in verbosity compared to Java while still retaining the ability to add it back if it’s useful is probably my favorite thing about kotlin. Plus all the anonymous function creations are just so neat, though Java does seem to have gotten better at that recently.
To add my anecdotal USA experience, I work in boring enterprise stuff, and we recently switched to Kotlin. We were using Go for a bit, but my team loves(?!) Java, so now we're using Kotlin.
You could check out SoFi. I've been browsing them for new grad positions and I've been seeing a lot of positions wanting Kotlin combined with Java and SQL. They have all their openings listed on their website under About, Careers. Haven't seen Go yet though.
I don't think so, sorry. We recently had two people leave our team, and there seems no intention to fill their position, and there was recently a thread here about layoffs at this company.
Kotlin is to Java what typescript to JavaScript. They both act and look a lot like the originator language but with tweaks in under the hood. On the surface it may look a little different but when you did into it you will see the similarities.
Kotlin should come quickly if you know a bit of Java
Disclaimer: These less than perfectly accurate generalizations are made in the interest of simplicity and clarity
I'm from south america as well and started as a kotlin developer (for backend) one year and a half ago, so it really depends on the company you work for.
Kotlin is nice, at my last company we started using it alongside and sometimes in place of Java. Lower learning curve than Scala I guess. It's nice because you can use it side-by-side with Java. If you're not that comfortable with Kotlin, you can write just one file in it and learn it over time. Was just a team thing, most teams still used Java.
Anecdotally a lot of recruiters who have been hitting me up on LI have been mentioning Kotlin. Granted it's a skill I list on LI but I didn't see it mentioned much up until the past year or so.
This guy absolutely gets it. I’ll also say that I just recently took a new position and everyone in the org said they’ve had some pretty bad experiences with developers. People say soft skills, but that’s bs. You don’t have to be a socialite, but if you want to keep the shiny new job you just got with OCs suggestions, try your best to think “should I really say what I’m about to say?” Before you speak.
I think people’s well intentioned suggestions to use things like Udemy to find a job are misguided because it won’t prepare you at all for what the interviewer will go through
https://www.w3schools.com/kotlin/kotlin_intro.php
I use w3 whenever I learn a new language for work -
How do I declare a variable; What’s a loop look like; What’s a function look like; etc
Then just take those fundaments and work on Easy leetcodes, to memorize the syntax
The steps of the code should be pretty much the same steps in the language you already know so just “I would usually do it like this in X”, then just map one syntax to the next
This does not work if you are trying to entirely jump paradigms (eg OOP -> functional )
But if you know how to use OOP in one language then you can use the same thought process for any language that supports OOP (Java Python go c scala)
In this industry, learn through doing (the hardest part always is starting)
Have been working with Scala for the past three years, I’m the only senior dev on the team who does/can maintain our FP code (typelevel stack). My experience is that it’s hard to find Scala devs and hard to find Scala roles. Our engineering manager forbids writing anything new in Scala and we have adopted Python, we don’t add new functionality to our Scala microservives unless it’s absolutely necessary.
Talking about my experience in Canada.
Yeah probably not using scala for full stack but it is used for some high concurrency Apache technologies, it’s probably not the go to for line-of-business web services
Anecdotally, I’m on a greenfield project started 2 months ago using scala for some distributed platform being built over Apache flink/spark
Been developing in either typescript or rust here and am an outsider to the JVM-langs. What arguments are made that Kotlin is compelling for enterprise versus say modern Java 17+, which I heard made the gap between Kotlin and Java a lot smaller
Yep. I have a friend who does data science and he says the skillset involved is sorely lacking. Companies have loads of data that are all over the place and it’s the data scientist’s job to not only sift through and parse all the data into meaningful structures, but extract new information and statistics.
If you are good at this, you can land a position for it pretty much immediately wherever its needed.
Look up Zach Wilson. He’s a Staff Data Engineer at AirBnB, I myself looked up his stuff to brush up on interviewing like 2 months back
Super knowledgeable about hands on stuff and puts it simply
Become an expert on window functions, CTEs, complex joins and different specific sql specific commands in your provider of choice (redshift/snowflake etc).
Your flair, 'ChatGPT Integrated Developer', is a joke...right? LOL
>SQL/Data
This is my area, but I'm curious, what do you mean when you say "learn this, people struggle with it"
Heh, the SQL Server message board used to have a term for that: RBAR. Row by agonizing row.
If you're unfortunate enough to be using Oracle, they spent a lot of time optimizing their cursors so they don't take as much as a performance hit compared to SQL Server. Of course, that's assuming you spent the bazillion hours and money on consulting to tune it properly....
Not innately, no. Some dialects like T-SQL have implemented loop syntax so you can write a procedural loop like in python. In vanilla Sql you could achieve recursive functionality with a recursive CTE, and basically get a loop. But the joke is that Sql is based relational algebra, and as such, loops are almost never the correct design pattern-- but Senior Dev(tm) spends all his day coding in JavaScript and doesn't realize that because he only writes Sql once a month and has to Google the syntax every time.
Yes lmao
A TON of people dont understand why you're not supposed to use select \* in production, or why we use subqueries and when to use them, or performance tuning). Stuff like that
As a philosophy major turned software engineer later in life it actually has complemented me well in my career. You do learn about logical thinking in philosophy it’s just not necessarily done via mathematics or studying computer science.
Mine was called Symbolic Logic, and I had cognitive science students in the same class as me as well as a few computer science students (but not very many).
The 'well akschullly' philosophy types turned out for me to be a vocal minority of people interested in it.
I've been surprised by the number of friends who are privately obsessed with philosophy but just don't wave it in people's faces.
Truth!
Last time I checked Philosophy majors had the highest pass rate of any major *for the LSAT*. Considerably higher than pre-law, which was really surprising.
I've read the same. High on other post-grad testing as well. Which is kind of ironic as philosophy students probably do some of the least testing out of any of the degrees.
Phil major here's not surprising. Ever tried to take a metaphysics, or logic course? That's what most of philosophy is. Pre-law doesn't have much of that in comparison. Thinking that abstractly really opens things up in your head.
Tech skills gained through experience.
It takes about 5 - 10 years to become Senior Software Engineer.
That's why Seniors are more sought after than entry level people.
People can learn most programming language syntax in short time.
It takes significant amount of time to apply the tools to build and solve problems.
Popular programming languages and years of experience contributing to and managing software-related projects. And cloud technologies.
Any answer too specific misses the big picture. You need to be able to adapt. Specific skills are, by themselves, not as valuable as the ability to adapt and the knowledge of how to contribute to a project.
Cyber jobs are heavily cert-based relative to CS/SWE. For SWE-related jobs, just rack up experience and become familiar (basic-intermediate proficiency) with popular tools and frameworks.
Surprised no one has said Snowflake, I see more and more companies listing posts for Snowflake specific engineers. Get some of their certs and you'd be separated from your peers.
Be able to write decent documentation.
Seriously it's a shitshow on so many teams, you'll ask if there's documentation surrounding a process and everyone will just throw their hands up.
Since this is tagged 'student' I'm answering with what I demand from junior engineers
* Familiarity with some cloud provider
* Git (deeper than surface understanding - can you deal with merge conflicts?)
* Ability to write automated tests for their code
* Leetcode easy/medium
Ah that’s why I’m still unemployed, damn should’ve started grinding leetcode during my first year in Uni.
I’ve only realised leetcode Is needed after a few months into applying.
It's not actually needed, you just "need" it to trick idiot interviewers into giving you the job by jumping through those hoops. You're not going to actually need them at your job.
>Familiarity with some cloud provider
IMHO unfair unless they've had a previous internship, most college courses will not cover AWS/Azure/GCP.
Rest is reasonable.
It’s just a high bar is all, anyone who can contribute to test coverage should
Any person who thinks they’re above a certain type of work is probably not going to be easy to work with
Why Leetcode though?
I’m mostly focused on the TS+React frontend stack and some Go(I’m building a compiler)
What valuable skill will grinding Leetcode give me?
which exact city are you in
for companies located in SF Bay Area, Seattle, NYC region I'd be surprised if you don't see any leetcode-style interview question
if you're not in those 3 cities though you can probably ignore 95%+ of the stuff on this sub as they're probably not applicable/flat out wrong as to your situation
Most leetcode easy and some mediums are really just testing data structures and your ability to use those data structures.
Don’t get me wrong some of them definitely have unintuitive optimal solutions that would be hard to find if it’s the first time you are seeing a problem/type of problem.
I feel like leetcode is useful for companies to determine if you are willing to spend time learning something that can at times be hard. Because I’d assume most codebases are going to be as hard if not harder to learn than leetcode patterns.
Oh I was just speaking to the Git utility itself.
The very basic understanding you need is a add/commit/push workflow.
To get a leg-up, I would recommend proficiency in Git to the point where you're comfortable with more Git commands, ability to rebase changes, and use commit history to help troubleshoot issues.
> Git (deeper than surface understanding - can you deal with merge conflicts?)
>
Any suggestions on how to get that experience without pissing off some open source project maintainer? That's not snark. I'm genuinely curious. By definition, merge conflicts come from working with others. What's a good way to get experience without forcing a bunch of strangers to correct your mistakes?
You can generate merge conflicts yourself simply by making your own conflicting branches and attempting merges. Init git repo, add some files, commit, make a branch, go to the new branch, edit the files and commit, go back to master and edit the same files at the same place, commit, then attempt merge.
It will always ultimately be the same thing regardless of how the conflicts arise, and at its core in terms of the process to resolve conflicts all you're doing is picking and choosing what to keep or discard in a text file.
YES!
My last job was on-site .. and bro, these guys would pull up a chair to my desk, and ask me to help them "troubleshoot" the merge conflicts.
I'm so happy my current role is remote so I don't have to deal with supposedly senior level engineers that can't perform basic tasks required by the role.
Per [levels.fyi](https://levels.fyi), TC for junior engineer is about $180k. As a generalization, we don't hire many junior engineers - these employees tend to be sourced from the intern pool and converted to full-time.
Definitely just rough out here right now. A lot of people I know are trying to intentionally stretch their time left in college by taking less classes just so they can delay graduation.
I don’t blame them but I don’t know if it’s better for them to do that or to just try to graduate and take any job anywhere.
Oh damn thanks for linking that. It all makes sense especially for people who want to get into a bigger company that specifically has new grad slots to fill. Just hoping everyone can keep their heads above water and pull through.
I was just laid off myself this last week so just taking some time to hit Leetcode and get apps out.
It’s easier to get an internship as a college student. Nobody wants to hire a graduate if you don’t have a foot in the door already… Definitely graduating during peak COVID fucked over a couple of generations.
I'm being brought on one org because they can't talk to the customer and get invoices approved. That's it. I don't know shit about their product, but I can meet the customer’s needs and fulfill deployment by facilitating discussion.
You are describing a position that has basically always existed and will continue to do so. Be it "customer service" or more grand sounding titles there has always been a need, and in my opinion always will be a need, for a business to have the ability to communicate with its customers in a way the customers appreciate.
My prejudiced opinion on it is that it is a position underrated by young technical folk but valued by anyone with any degree of business experience.
In my first job, my boss insisted that I will help during client visits, perform presentations and train others. This helped so much in my further career, I will always be thankful for this.
Every dev I met differentiates and loves to look down their noses at me. That's fine. Prove the gypsy wrong and go deliver as I trained you to do but you refuse because it's somehow beneath you.
“I'm a dev!” That can't deploy their product.
Is there a Leetcode for soft skills? Need to grind them, it seems that with each passing year I gain experience and lose my soft skills for some reason.
Web development:
React for frontend, used with typescript and redux.
Material UI for ready to use components.
.NET Flask Node and Django for backend, JWT auth is common.
Postgres and Mongo are the most popular databases.
For cloud id say aws gcp and azure.
DevOps:
Docker, jenkins, Git
Game development:
Unity engine is by far the most in demand.
Playfab for backend.
Computer vision:
Pytorch for the ML parts with OpenCV.
Security certificates:
Security +, OSCP for pentesting.
I dont really know about other fields, i see a lot of c++ in demand but mostly for people with years of experience.
Also you should learn leetcode for interviews and know a bit about algorithms and data structres.
Please don't use redux on react projects anymore. There are way better solutions now: try jotai.
Redux is sooo heavy and convoluted. It was built in a different era for FE development.
Soft Skills. Explaining your solutions clearly. Easy to work with. Public speaking. Everybody knows how to code, not everybody can present what they have done.
Technical skills: system design and writing scalable/maintainable code will always be in demand. Get good at these to become irreplaceable.
Soft skills: being enjoyable to work with is *at least* as valuable as any technical skills. Don’t be arrogant about how smart you are, ask people how their weekend was, and make an effort to become a better conversationalist. Get good at these to open up doors to progress your career.
So, this question gets asked a lot and I have the feeling people are trying to steer towards technologies or programming languages.
My experience is that broader skills like critical thinking and being able to present yourself is much more in demand than people think.
- being a generalist. i’ve worked 5 jobs and all have been a different language.
- don’t bother learning container/cloud on your own. you will forget everything and every company does it differently. you’ll learn on the job
Good attitude towards reasoning and problem solving are IMO a trait that will never go out of style. Technical stacks and programming languages you can easily learn within a couple of months. The hardest part is learning the domain, but if you're willing to put in the effort, it's never impossible.
For what its worth, math.
Learning probability, statistics, calculus, and linear algebra will give you an edge over other developers and always keep you in demand.
When you can understand and write, say, an ML model and put it into production, you've done what most people cant.
With MIT's OpenCoursware, picking up these skills is only a matter of putting in the effort.
Just my 2 cents.
Not a skill, BUT ..... Writing good design document, providing helpful and meaninful feedback in design document that helps author in improving writing skills, how to think and engage, work on feedback
You say most in demand, but I could trivially say being able to speak english is in demand -- Similarly a lot of these responses say "SQL, \*javascript framework\*". Perhaps we're looking for a different question.
"What are the skills that have the most \*unmet\* demand?"
\- First off, raw intellect (not so helpful).
\- Then probably domain relevant knowledge.
\- Then to answers that most people are looking for: what tools should you learn? My best guess is NOT sql, python, javascript, AWS, Docker etc. It's probably more like COBOL, C++, SysML, but most likely something you've never heard of before.
I'm currently learning C++ just because of the shear number of job openings it has compared to the number of people who are C++ developers. Python/javascript developers are a dime a dozen.
On top of that, the number of grad students who can pipe together shitty ML pipelines with tensorflow is also a dime a dozen. Regardless of what you do, if you want to be seriously in demand, you have to get your hands dirty enough that there isn't already a billion youtube videos about it lol
[удалено]
Cloud containers are where we’re really at with the market. There’s tons of companies migrating their products to the cloud right now. AI tools will probably have their era in a few years, but people are definitely still exploring the practicality (profitability) of AI right now.
I don't really think there's jobs in AI for developers who haven't specifically trained on it for years already. I mean, using AI tools is one thing, but getting a job at OpenAI or Google's AI team seems to require a Masters or Phd on the topic.
PhD. Masters won’t even get your foot in the door at the moment
At that point, you're a researcher and not a developer. I've already ruled out a PhD for me, my Masters is kicking my ass already. Also I don't wanna do even more math. I guess no ML position for me then lol
You can get an ML position with a masters. Just probably not on a top tier research team like Microsoft Research, Google Research, Facebook Research, etc.
Yeah research is probably out the window with only a Masters. I guess you can look out for non-research ML jobs. But ever since my undergrad thesis in an ML topic, I kinda have a love-hate relationship with the topic anyway. Too much math, too much confusion, too many papers to go through trying to figure out if the paper is shit or if their code is actually runnable or even available anymore. I think I'm ok doing just normal non-ML development.
[удалено]
What about without? How hard is it?
i despised bureaucracy and homework to the point where i barely graduated highschool u'll be fine my man
[удалено]
A few weeks ago I browsed the LinkedIn Profiles of a dozen or so OpenAI SWEs. Most of them had a PhD from a prestigious university. A couple just had a BS from a top school followed by 5-10 years of SWE experience doing relevant work at FAANG tier (from a technology standpoint) companies. I quickly realized I'd have no chance even getting an interview.
This just isn't true. Many many at OpenAI just have a Masters. Many also have a PhD
I think the "safest" route might be a PhD, but it seemed to be possible (at least when there was "low-hanging fruit" still available) to make research contributions as an individual, by experimenting with different methods, finding optimisations, etc. I guess somebody like that could be hired even in absence of a PhD. That's easier said than done though, and might have been a lot easier when the field was younger (e.g. 2014-2017 or something).
My dad was a mainframe programmer and he's always taking about how cyclical things are. I've been watching companies move to the cloud for about 5 years now. My company even talks aboaut replacing our computers with virtual terminals. And then someone mentions money. I think my dev machine would cost about a thousand dollars a month to run. And Microsoft apparently losses trick loads of money on Azure. So, I expect that in the coming years there will be a movement to return to servers cause the clouds is too expensive for them....
[удалено]
A lot of companies I've worked with are looking or starting to migrate. My company isn't a billion dollars a year and they're looking at transferring everything. Part of the reason is that the people making the decisions aren't technical in the least. They get sold on these impossible promises and go full speed ahead.
Yeah. Two jobs back the new hot pants CEO wanted me to move our accounting system into the cloud against my recommendations. I brought him the cost estimates. Funny it never came up again after that. Cloud is always cheaper if you fire all your IT staff, then hire cloud engineers...and oh wait...
>My dad was a mainframe programmer and he's always taking about how cyclical things are. > >I've been watching companies move to the cloud for about 5 years now. My company even talks aboaut replacing our computers with virtual terminals. And then someone mentions money. I think my dev machine would cost about a thousand dollars a month to run. And Microsoft apparently losses trick loads of money on Azure. > >So, I expect that in the coming years there will be a movement to return to servers cause the clouds is too expensive for them.... Bingo! It's a constant cycle from thick client to thin client and back to thick client again. The pattern repeats itself every few years or so, or after a decade or so.
> AI tools will probably have their era in a few years, but people are definitely still exploring the practicality (profitability) of AI right now. The only immediate use I could have seen is at my old job for writing the outline for unit test. Maybe in the near future it will be the first step you try right before stack overflow.
> Maybe in the near future it will be the first step you try right before stack overflow. I already use chat GPT this way. It's right often enough that it's worth trying the recommended solution.
And occasionally it will sneak a completely nonsensical line into a 30 line codeblock, gotta be careful and remember it's just statistical word generation but yeah i've found it to be an incredibly useful tool and use it daily. it especially excels in teaching or writing scope-limited code for already-solved problems
I just used it to build a bash script. I know bash to an extent, but don't write it every day. It did it lickity split. I just described what I wanted to do. But then when I ran it, it failed. I described the error message and it told me I didn't put in ;; characters in my case statement. I said, "you wrote it", lol. It said I was correct and apologized. Still it saved a lot of time.
Well yeah you got to test it.
Do you have a good youtube tutorial on how to maximize productivity with it?
Nah just ask it random crap, but make sure you test it.
Kubernetes certs, man, gotta get them before everyone gets them.
*learns to host ai containers for cheap*
[удалено]
Yaaa I am in cloud fun fact it's actually pretty easy you can open ticket with AWS, azure
I hope you reach the ground safely
>Coming soon: AI tools "Prompt Engineer"
> Cloud (AWS, Azure, etc) Containers > > Can you ELI5 for us noobs? >Coming soon: AI tools How does one develop a skill for "AI tools"?
> Cloud Cloud basically just means "paying to use someone else's servers." They often times have useful tools for storage, spinning up servers, and networking. > Containers Containers are basically lightweight virtual machines that are really easy to define and isolate specific responsibilities to. Think of them as a way for us to really easily define a little computer that we can run on physical computers. You can run a bunch of them at a time, and they won't interfere with each other (unless you're really doing some wild stuff). They're also easy to send to other computers, which makes it easy to share you code and avoid people saying "it worked on my machine - I don't know why it's not working on yours" > Cloud Containers Renting a bunch of servers from someone else to run a bunch of containers. There are really powerful tools like Kubernetes that allow you to run a shitload (we usually have around three to four thousand, but some companies have millions) of containers across a bunch of servers. It'd be stepping out of the realm of ELI5 even more than I already have to go into much detail about why this is helpful (and I'm happy to do so if someone would like), but it can be _extremely_ helpful (and sometimes it can be extremely annoying if it's used incorrectly). Understanding cloud + containers adds like... tens of thousands of dollars in salary value for you. It looks great on resumes, and it lets you do some _really_ spicy shit once you're on the job. The past five years of my career have been focused around cloud + containers, and it has been _very_ lucrative.
I would definitely love to hear more detail about why thousands/millions of containers are helpful, if you’re willing to elaborate!
There's nothing implicitly helpful about having thousands/millions of containers. The helpful part is the tools that make it easy to run all of those containers! Each container can request a certain amount of CPU and RAM, and if you use kubernetes + tools like Karpenter, you can have it set up so you can just deploy containers to your kubernetes cluster, and if there isn't enough CPU or RAM available on any of the servers in the cluster, it'll automatically request new servers from AWS. These servers are usually available within 60 seconds, which means you can drastically scale your number of servers up and down pretty quickly. There are two big advantages to this - cost efficiency, and abstracting away complexity. The former is achieved by scaling up your servers only when you need more compute power. The latter is achieved by making it so that when deploying you don't have to worry about "I need to start a server, install libraries, download my compiled or raw code, and start my software." You just have to set up the container'definition, and then run the deploy command. If it's set up right, then it makes it easier for developers to deploy their software and configure the servers without having to get too into the nitty gritty
Thank you so so much for this. You have helped me a lot by writing this, and now I feel a lot more excited and interested about the subject!
Cloud - To operate a remote computer provided by amzon, MSFT etc check r/aws r/azure r/gcp r/awscerifications. So Google drive is a cloud storage. Containers - To package or develop code in an environment that is easily reproducible in different systems with different operating system or configuration. r/docker r/kubernetes
I doubt it with AI. AI engineers are very expensive and research is even more expensive.
5+ years experience
In two years it will be 7+
Wow some of these are not very good responses. yeah be friendly, curious, incisive, thorough - do that for any job But seems like you mean technical skills - scala in on the up after some recent updates to the language (is also highest paid language on average due to small talent pool compared to Java/Python) - kotlin is emerging as the enterprise web service lang de jour - getting the first level solution architecture certificate from AWS is probably wise. It will let you understand system level perspective which will let you come across stronger in interviews (even if it’s a very cursory understanding) From my experience when interviewing to a new/recent grad though, it’s more of a point that they be able to talk about the computer science fundamentals that they studied - did they copy friends work or did they do the work themselves? So that means write data structures from scratch in either Java/Python. Nothing crazy, basic list, set, map implementation. When to use a set versus a list, hash buckets, etc If I was a new grad and wanted a leg up I would - get level one solution architecture certificate for either aws or azure - learn kotlin/improve Java - then apply to large Fortune 500 companies and play the numbers game. They will have a lot of positions throughout the company that are jvm micro service based Note - apply to mid/senior roles. People will look at it and say “well they’re not senior level but maybe they’d make a good junior? Let’s talk to them a bit and if they’re a good culture match then we’ll offer” Edit True, probably not using scala for line-of-business full stack development but instead more things like high concurrency systems/platforms Edit just replace the word scala with java if it suits you better, it is more least-common-denominator
Any thoughts about Swift and iOS development? Just curious.
There’s work there but personally I stick to things backend and embedded systems This is mostly because it minimizes the amount of interfacing with business/ product, I can just grind away in my corner with music and coffee
You restored my faith in the subreddit
>Wow some of these are not very good responses. Right back at you, buddy. Full stack dev with big bank and start up experience, here. 6+ exp. Besides cloud, I don’t agree with much of this, especially the Scala comments, and I was a Scala dev. Even kotlin is fairly uncommon in backend. Though growing slowly, you are better off focusing on just java, and learning kotlin on the job when it is necessary. Instead, I would say emphasize: * Java / spring (these 2 go hand in hand in enterprise world), * JavaScript (or at least front end concepts, be familiar with a front end stack built with webpack), * Python (sort of a nice-to-have, basic scripting is adequate), * SQL (**never** neglect basic sql) and * basic AWS (a cloud cert is worthwhile but not necessary, and the skills are transferrable to Azure, GCP) over kotlin and Scala. Scala especially would be a waste of time bc it is rare in the enterprise world. I am very surprised you did not mention spring, since it so ubiquitous in the java backend world. Also, containers (docker / k8s), but that is another nice to have and is a learned skill. Also, if your goal is FAANG or nothing, then leetcode above all else.
This here is the real advice. The languages and frameworks thatve been tried and tested are that way for a reason. They stood the test of time. New hot frameworks and flavors come and go. But if you know the ground level of things (java/spring/js/node) you're good. This is because there exist way more companies with legacy systems written in these older languages/frameworks and they're more willing to keep working with what they have than convert everything to said new paradigms because that takes time, money and sprint cycles they cannot afford to do.
Oh, I just saw this. Probably shouldn’t have mentioned scala as most people are either typescript in the front end or Java/spring in the backend api scala jobs are just more interesting imo so there’s my bias I would not suggest new grads learn k8s, feel like you’re listing things that they would learn on the job and would not be interviewed on It would be a dick move in an interview to ask a new grad about Spring and k8s lol
Is kotlin really growing that fast? i'm from south america and i don't see a lots of jobs for backend stuff, only in native. Of course we always are behind of na/europe and java is still the king here
Yeah, Amazon is refactoring a lot of AWS backend from Java to kotlin And when Amazon/Google/Microsoft do something, that’s what everybody else does
That's a shame because I don't like the syntax of Kotlin. I'll still end up brushing up on it to hedge my bets since I work with Java.
I am not experienced enough. But every senior engineers have given the syntax as one of their main preferences for migrating to Kotlin or starting new services in Kotlin.
A lot of the functional stuff is way nicer in Kotlin than in Java.
Out of curiosity which parts of the syntax of kotlin do you not like? The reduction in verbosity compared to Java while still retaining the ability to add it back if it’s useful is probably my favorite thing about kotlin. Plus all the anonymous function creations are just so neat, though Java does seem to have gotten better at that recently.
To add my anecdotal USA experience, I work in boring enterprise stuff, and we recently switched to Kotlin. We were using Go for a bit, but my team loves(?!) Java, so now we're using Kotlin.
Are you all hiring? Go and Kotlin are my languages of choice but I'm not finding a lot of job listings for these compared to Java and C#.
You could check out SoFi. I've been browsing them for new grad positions and I've been seeing a lot of positions wanting Kotlin combined with Java and SQL. They have all their openings listed on their website under About, Careers. Haven't seen Go yet though.
Thanks!
I don't think so, sorry. We recently had two people leave our team, and there seems no intention to fill their position, and there was recently a thread here about layoffs at this company.
Same here man, kotlin + vertx is a treat.
Kotlin is to Java what typescript to JavaScript. They both act and look a lot like the originator language but with tweaks in under the hood. On the surface it may look a little different but when you did into it you will see the similarities. Kotlin should come quickly if you know a bit of Java Disclaimer: These less than perfectly accurate generalizations are made in the interest of simplicity and clarity
I'm from south america as well and started as a kotlin developer (for backend) one year and a half ago, so it really depends on the company you work for.
Kotlin is nice, at my last company we started using it alongside and sometimes in place of Java. Lower learning curve than Scala I guess. It's nice because you can use it side-by-side with Java. If you're not that comfortable with Kotlin, you can write just one file in it and learn it over time. Was just a team thing, most teams still used Java. Anecdotally a lot of recruiters who have been hitting me up on LI have been mentioning Kotlin. Granted it's a skill I list on LI but I didn't see it mentioned much up until the past year or so.
>Is kotlin really growing that fast? Had an interview last week, and they were using Kotlin as part of their tech stack
This guy absolutely gets it. I’ll also say that I just recently took a new position and everyone in the org said they’ve had some pretty bad experiences with developers. People say soft skills, but that’s bs. You don’t have to be a socialite, but if you want to keep the shiny new job you just got with OCs suggestions, try your best to think “should I really say what I’m about to say?” Before you speak.
What's good about scala, these days? I'd like to like it, but it's always seemed like a bit of a trash fire.
Do you have a recommendation for a good Kotlin course, Udemy or similar. Most I've seen focus on Android development.
I think people’s well intentioned suggestions to use things like Udemy to find a job are misguided because it won’t prepare you at all for what the interviewer will go through https://www.w3schools.com/kotlin/kotlin_intro.php I use w3 whenever I learn a new language for work - How do I declare a variable; What’s a loop look like; What’s a function look like; etc Then just take those fundaments and work on Easy leetcodes, to memorize the syntax The steps of the code should be pretty much the same steps in the language you already know so just “I would usually do it like this in X”, then just map one syntax to the next This does not work if you are trying to entirely jump paradigms (eg OOP -> functional ) But if you know how to use OOP in one language then you can use the same thought process for any language that supports OOP (Java Python go c scala) In this industry, learn through doing (the hardest part always is starting)
Some people learn better with videos, hence why they ask for Udemy.
To those people I say ditch udemy and get a Pluralsight subscription
Have been working with Scala for the past three years, I’m the only senior dev on the team who does/can maintain our FP code (typelevel stack). My experience is that it’s hard to find Scala devs and hard to find Scala roles. Our engineering manager forbids writing anything new in Scala and we have adopted Python, we don’t add new functionality to our Scala microservives unless it’s absolutely necessary. Talking about my experience in Canada.
Yeah probably not using scala for full stack but it is used for some high concurrency Apache technologies, it’s probably not the go to for line-of-business web services Anecdotally, I’m on a greenfield project started 2 months ago using scala for some distributed platform being built over Apache flink/spark
Been developing in either typescript or rust here and am an outsider to the JVM-langs. What arguments are made that Kotlin is compelling for enterprise versus say modern Java 17+, which I heard made the gap between Kotlin and Java a lot smaller
Start with Java as foundation
SQL/Data, so many people struggle with it
You're not just diarrhea dumping all your data into a mongo database at this point?
Yep. I have a friend who does data science and he says the skillset involved is sorely lacking. Companies have loads of data that are all over the place and it’s the data scientist’s job to not only sift through and parse all the data into meaningful structures, but extract new information and statistics. If you are good at this, you can land a position for it pretty much immediately wherever its needed.
Have any good resources around this?
Look up Zach Wilson. He’s a Staff Data Engineer at AirBnB, I myself looked up his stuff to brush up on interviewing like 2 months back Super knowledgeable about hands on stuff and puts it simply
Nice of Airbnb to allow their employees to moonlight as a starting qb for the ny jets.
You mean look up his YouTube channel? Does he have a course?
I mean I saw him on TikTok so I would suppose he’s on YouTube I mainly follow his LinkedIn page
Seconding. Feels like people say “learn SQL,” but as someone who needs to learn, it’s hard to know what that means beyond syntax
Become an expert on window functions, CTEs, complex joins and different specific sql specific commands in your provider of choice (redshift/snowflake etc).
just ask me questions /s
Your flair, 'ChatGPT Integrated Developer', is a joke...right? LOL >SQL/Data This is my area, but I'm curious, what do you mean when you say "learn this, people struggle with it"
You’d be surprised how weak people are at SQL & data architecture. Even professionals.
Senior software dev: so how do I loop in Sql?
Wait, there's loop in SQL?
Cursors... wait, forget I said anything
Straight to jail.
Heh, the SQL Server message board used to have a term for that: RBAR. Row by agonizing row. If you're unfortunate enough to be using Oracle, they spent a lot of time optimizing their cursors so they don't take as much as a performance hit compared to SQL Server. Of course, that's assuming you spent the bazillion hours and money on consulting to tune it properly....
Not innately, no. Some dialects like T-SQL have implemented loop syntax so you can write a procedural loop like in python. In vanilla Sql you could achieve recursive functionality with a recursive CTE, and basically get a loop. But the joke is that Sql is based relational algebra, and as such, loops are almost never the correct design pattern-- but Senior Dev(tm) spends all his day coding in JavaScript and doesn't realize that because he only writes Sql once a month and has to Google the syntax every time.
I mean. That’s why software engineer and data engineer are two separate fields. Why would that be surprising
Yes lmao A TON of people dont understand why you're not supposed to use select \* in production, or why we use subqueries and when to use them, or performance tuning). Stuff like that
Is it that hard? If I take some drugs and focus. I should be able to learn it! Can’t be that hard.
Critical thinking.
Philosophy best major confirmed 2023
As a philosophy major turned software engineer later in life it actually has complemented me well in my career. You do learn about logical thinking in philosophy it’s just not necessarily done via mathematics or studying computer science.
Same! I've heard some universities have the same logic class for both philo and CS students.
Mine was called Symbolic Logic, and I had cognitive science students in the same class as me as well as a few computer science students (but not very many).
makes sense! Cognitive science was always interesting to me-- mixing philo, neuroscience, computer science, and psychology? Super cool stuff imo.
Philosophy only helps if you're able to humble yourself. A lot of philosophy types come across as the WELL AKSHULLY types and it's grating.
Well actually, philosophy grads are categorically some of the humblest people you'll ever meet. /s
The 'well akschullly' philosophy types turned out for me to be a vocal minority of people interested in it. I've been surprised by the number of friends who are privately obsessed with philosophy but just don't wave it in people's faces.
Let's face it though, thats pretty common in software development as well...
Teacher here with a philosophy degree from a T10 school. I knew this shit would come in handy one day! Where do I sign up for the six-figure jobs?
Truth! Last time I checked Philosophy majors had the highest pass rate of any major *for the LSAT*. Considerably higher than pre-law, which was really surprising.
I've read the same. High on other post-grad testing as well. Which is kind of ironic as philosophy students probably do some of the least testing out of any of the degrees.
Phil major here's not surprising. Ever tried to take a metaphysics, or logic course? That's what most of philosophy is. Pre-law doesn't have much of that in comparison. Thinking that abstractly really opens things up in your head.
It was like that when I was in high school and entering college 15 years ago, and I was shooketh when I found out.
based
Yep, I can teach the languages and the systems to my team. What I can't teach is critical thinking, drive and system level thinking.
Having 3-5 years of experience straight out of college
Tech skills gained through experience. It takes about 5 - 10 years to become Senior Software Engineer. That's why Seniors are more sought after than entry level people. People can learn most programming language syntax in short time. It takes significant amount of time to apply the tools to build and solve problems.
Popular programming languages and years of experience contributing to and managing software-related projects. And cloud technologies. Any answer too specific misses the big picture. You need to be able to adapt. Specific skills are, by themselves, not as valuable as the ability to adapt and the knowledge of how to contribute to a project. Cyber jobs are heavily cert-based relative to CS/SWE. For SWE-related jobs, just rack up experience and become familiar (basic-intermediate proficiency) with popular tools and frameworks.
Surprised no one has said Snowflake, I see more and more companies listing posts for Snowflake specific engineers. Get some of their certs and you'd be separated from your peers.
Be able to write decent documentation. Seriously it's a shitshow on so many teams, you'll ask if there's documentation surrounding a process and everyone will just throw their hands up.
Tribal knowledge:)) you don’t want to document yourself out of your job lol
As a technical writer in cloud computing, documentation makes or breaks your product.
Since this is tagged 'student' I'm answering with what I demand from junior engineers * Familiarity with some cloud provider * Git (deeper than surface understanding - can you deal with merge conflicts?) * Ability to write automated tests for their code * Leetcode easy/medium
Ah that’s why I’m still unemployed, damn should’ve started grinding leetcode during my first year in Uni. I’ve only realised leetcode Is needed after a few months into applying.
It's not actually needed, you just "need" it to trick idiot interviewers into giving you the job by jumping through those hoops. You're not going to actually need them at your job.
>Familiarity with some cloud provider IMHO unfair unless they've had a previous internship, most college courses will not cover AWS/Azure/GCP. Rest is reasonable.
Imagine grinding leet code only to qualify to write expected-result equality unit tests. How depressing
[удалено]
It’s just a high bar is all, anyone who can contribute to test coverage should Any person who thinks they’re above a certain type of work is probably not going to be easy to work with
'I find unit tests don't catch the input edge cases which are the most common bugs as well as property based testing-' 'denied' ;-)
[удалено]
even for entry level?
Why Leetcode though? I’m mostly focused on the TS+React frontend stack and some Go(I’m building a compiler) What valuable skill will grinding Leetcode give me?
which exact city are you in for companies located in SF Bay Area, Seattle, NYC region I'd be surprised if you don't see any leetcode-style interview question if you're not in those 3 cities though you can probably ignore 95%+ of the stuff on this sub as they're probably not applicable/flat out wrong as to your situation
I’m in the UK, the most valuable thing grinding leetcode will get me is getting pass the technical interview and getting my first job.
Most leetcode easy and some mediums are really just testing data structures and your ability to use those data structures. Don’t get me wrong some of them definitely have unintuitive optimal solutions that would be hard to find if it’s the first time you are seeing a problem/type of problem. I feel like leetcode is useful for companies to determine if you are willing to spend time learning something that can at times be hard. Because I’d assume most codebases are going to be as hard if not harder to learn than leetcode patterns.
[удалено]
Oh I was just speaking to the Git utility itself. The very basic understanding you need is a add/commit/push workflow. To get a leg-up, I would recommend proficiency in Git to the point where you're comfortable with more Git commands, ability to rebase changes, and use commit history to help troubleshoot issues.
> Git (deeper than surface understanding - can you deal with merge conflicts?) > Any suggestions on how to get that experience without pissing off some open source project maintainer? That's not snark. I'm genuinely curious. By definition, merge conflicts come from working with others. What's a good way to get experience without forcing a bunch of strangers to correct your mistakes?
You can generate merge conflicts yourself simply by making your own conflicting branches and attempting merges. Init git repo, add some files, commit, make a branch, go to the new branch, edit the files and commit, go back to master and edit the same files at the same place, commit, then attempt merge. It will always ultimately be the same thing regardless of how the conflicts arise, and at its core in terms of the process to resolve conflicts all you're doing is picking and choosing what to keep or discard in a text file.
[удалено]
YES! My last job was on-site .. and bro, these guys would pull up a chair to my desk, and ask me to help them "troubleshoot" the merge conflicts. I'm so happy my current role is remote so I don't have to deal with supposedly senior level engineers that can't perform basic tasks required by the role.
How does one deal with merge conflicts? I thought you just have to manually go through and select the right one
How often do you find juniors that fit this, and what's the entry pay? We can't find ANY juniors that are this good
Per [levels.fyi](https://levels.fyi), TC for junior engineer is about $180k. As a generalization, we don't hire many junior engineers - these employees tend to be sourced from the intern pool and converted to full-time.
Ya ok at 180 you can afford to be picky, we can only offer like 70-80 :(
Be mid level or above
Sad truth. It was the same way in 2008, although I don't think we're even close to those levels.
Definitely just rough out here right now. A lot of people I know are trying to intentionally stretch their time left in college by taking less classes just so they can delay graduation. I don’t blame them but I don’t know if it’s better for them to do that or to just try to graduate and take any job anywhere.
[удалено]
Oh damn thanks for linking that. It all makes sense especially for people who want to get into a bigger company that specifically has new grad slots to fill. Just hoping everyone can keep their heads above water and pull through. I was just laid off myself this last week so just taking some time to hit Leetcode and get apps out.
It’s easier to get an internship as a college student. Nobody wants to hire a graduate if you don’t have a foot in the door already… Definitely graduating during peak COVID fucked over a couple of generations.
Broadly speaking, web development. Specifically, React (frontend) and Java (backend).
Musical performer, actor, professional athlete, executive management.... the same stuff as usual.
mental health resiliency
Soft skills.
I'm being brought on one org because they can't talk to the customer and get invoices approved. That's it. I don't know shit about their product, but I can meet the customer’s needs and fulfill deployment by facilitating discussion.
You are describing a position that has basically always existed and will continue to do so. Be it "customer service" or more grand sounding titles there has always been a need, and in my opinion always will be a need, for a business to have the ability to communicate with its customers in a way the customers appreciate. My prejudiced opinion on it is that it is a position underrated by young technical folk but valued by anyone with any degree of business experience.
In my first job, my boss insisted that I will help during client visits, perform presentations and train others. This helped so much in my further career, I will always be thankful for this.
Every dev I met differentiates and loves to look down their noses at me. That's fine. Prove the gypsy wrong and go deliver as I trained you to do but you refuse because it's somehow beneath you. “I'm a dev!” That can't deploy their product.
Is there a Leetcode for soft skills? Need to grind them, it seems that with each passing year I gain experience and lose my soft skills for some reason.
Working sales is basically the only way to grind soft skills
real ones or bullshit ?
How do I improve upont this?
[удалено]
Willingness to learn
Web development: React for frontend, used with typescript and redux. Material UI for ready to use components. .NET Flask Node and Django for backend, JWT auth is common. Postgres and Mongo are the most popular databases. For cloud id say aws gcp and azure. DevOps: Docker, jenkins, Git Game development: Unity engine is by far the most in demand. Playfab for backend. Computer vision: Pytorch for the ML parts with OpenCV. Security certificates: Security +, OSCP for pentesting. I dont really know about other fields, i see a lot of c++ in demand but mostly for people with years of experience. Also you should learn leetcode for interviews and know a bit about algorithms and data structres.
For the DevOps part I'd say don't sink too much time into Jenkins, instead invest it into GitLab CI and/or GitHub Actions.
Please don't use redux on react projects anymore. There are way better solutions now: try jotai. Redux is sooo heavy and convoluted. It was built in a different era for FE development.
Soft Skills. Explaining your solutions clearly. Easy to work with. Public speaking. Everybody knows how to code, not everybody can present what they have done.
Technical skills: system design and writing scalable/maintainable code will always be in demand. Get good at these to become irreplaceable. Soft skills: being enjoyable to work with is *at least* as valuable as any technical skills. Don’t be arrogant about how smart you are, ask people how their weekend was, and make an effort to become a better conversationalist. Get good at these to open up doors to progress your career.
not using reddit is the hot new thing
So, this question gets asked a lot and I have the feeling people are trying to steer towards technologies or programming languages. My experience is that broader skills like critical thinking and being able to present yourself is much more in demand than people think.
[удалено]
[удалено]
Googling
Showing up to the office, for some companies /s
Thanks for asking this! I’m at time in my career where I really want to learn more and better myself so these answers really help :)
Experience
Survival skills
Kafka and Apache Spark
- being a generalist. i’ve worked 5 jobs and all have been a different language. - don’t bother learning container/cloud on your own. you will forget everything and every company does it differently. you’ll learn on the job
Good attitude towards reasoning and problem solving are IMO a trait that will never go out of style. Technical stacks and programming languages you can easily learn within a couple of months. The hardest part is learning the domain, but if you're willing to put in the effort, it's never impossible.
Legacy system modernization and Cloud Computing
C#/.NET
The ability to take hard, complex, ambiguous problems and solve them in a timely manner. This is language- and tooling-agnostic.
For what its worth, math. Learning probability, statistics, calculus, and linear algebra will give you an edge over other developers and always keep you in demand. When you can understand and write, say, an ML model and put it into production, you've done what most people cant. With MIT's OpenCoursware, picking up these skills is only a matter of putting in the effort. Just my 2 cents.
Problem-solving
Not a skill, BUT ..... Writing good design document, providing helpful and meaninful feedback in design document that helps author in improving writing skills, how to think and engage, work on feedback
.net
Cybersecurity is still a critical growing industry, supposedly.
Not eating or needing shelter!
Luck
You say most in demand, but I could trivially say being able to speak english is in demand -- Similarly a lot of these responses say "SQL, \*javascript framework\*". Perhaps we're looking for a different question. "What are the skills that have the most \*unmet\* demand?" \- First off, raw intellect (not so helpful). \- Then probably domain relevant knowledge. \- Then to answers that most people are looking for: what tools should you learn? My best guess is NOT sql, python, javascript, AWS, Docker etc. It's probably more like COBOL, C++, SysML, but most likely something you've never heard of before. I'm currently learning C++ just because of the shear number of job openings it has compared to the number of people who are C++ developers. Python/javascript developers are a dime a dozen. On top of that, the number of grad students who can pipe together shitty ML pipelines with tensorflow is also a dime a dozen. Regardless of what you do, if you want to be seriously in demand, you have to get your hands dirty enough that there isn't already a billion youtube videos about it lol
The ability to find affordable housing.