I started in 2003, learned C++, then did the majority of my courses in C++ with a class in Java with self-taught Python, C#, and PHP along the way for coursework.
Can someone fill me in, but is there still the derogatory "Java school"? I find that silly because most jobs in programming use some sort of managed memory programming language so teaching everyone in Java makes a lot of sense.
I'll indications point to this GitHub user [1], Alexis Sellier [2], as the engineer behind this. Good luck with such an ambitious goal. I'd love to see it.
I’ve been using devenv for about 6 months now. I’ve started new projects with it and migrated old ones to use it as well. I’ve also set up my org’s repositories with it. Onboarding devs to projects is simple. All everyone needs on their local machine is git, nix, and devenv. Bonus points for using it with direnv for automatic shell activation when you enter a directory. Direnv allows for IDE integrations as well for project dependencies.
Secret? It’s the obvious trajectory. The ad industry already monetized our browsing history for its insights into user behavior. Prompt history is even more valuable. It’s a window into someone’s thoughts. When the AI bubble bursts and investors want their money back, selling prompt data to advertisers will be the easy play.
Definitely. And it's not going to be read-only access, the advertisers will be able to have have their messaging delivered conversationally and without disclosure
They only have to do so because it's nearly impossible for a new grad to stand out from the foam of AI applications. This is part of the trend that created the need—it's a toxic feedback loop.
Undergrads have tons of opportunities to gain experience and make connections, both on and off campus: internships, research, TA jobs, sports, Greek life, volunteering, clubs, etc.
When I review resumes from new grads, it's that kind of extracurricular stuff that stands out. It shows they had the initiative and commitment to pursue things that matter to them. If a resume is only coursework, then sure, that won't stand out.
This still doesn’t answer the second part - why hire a new grad over someone with two or three years of experience? There are plenty of those hungry for a job that would work for the same compensation.
My team has to be in-person, and new grads are far more likely to be open to relocating. I'd rather spend valuable time recruiting and interviewing people who are likier to accept an offer over those who'd balk at moving.
Students have way more advantages in hiring than they realize. Openness to moving is a big one. So is getting experience and connections via extracurriculars. If you're a university student and you take the small steps to build up these advantages over time, you won't need to resort to resume-spamming.
And if they “have to be in person” is that because you are doing programming with specialized equipment?
I can’t imagine hiring a bunch of new grads can actually end up being productive. Back in the day you would open an office in a place where you can get relatively cheap experienced devs like the suburbs of Atlanta (where I use to live).
Yes, specialized equipment, and also restrictions on what systems we can do some of our work on.
My organization isn't a run-of-the-mill software shop. We're an FFRDC (https://en.wikipedia.org/wiki/Federally_funded_research_and_...) that does applied research for the US government. As such, our culture is to bring people in who we can develop and retain for a long time. A junior staff member's tasking and skill set may be limited to software development. But eventually they grow into technical experts on whole systems and use-cases, or team leads with established relationships with external stakeholders.
I'm in the latter position, and I'm pretty good at identifying, recruiting, and developing people right out of school. To go back to the original topic, resume-spamming isn't the way you end up in an organization like mine.
But then we get into the whole “salary compression and inversion” where because of HR dynamics vs market dynamics, you’re almost always better jumping ship after the first 2-3 years.
As a hiring manager, that’s out of your control. So you know that you usually can’t get more than 2-3 years out of an employee. If they are spending the first year doing “negative work”, is ur worth it?
How is this different than any other job? Experience is experience I don’t see how that justifies pissing off your potential employers with mountains of AI slop resumes.
What I was trying saying is that a lack of experience isn't some kind of unfair disadvantage that justifies making all our lives worse by using tools like this. Instead one could spend their time, I dunno, acquiring experience? There's plenty of OSS projects out there that could use help, and personal projects are always a great differentiator.
Let me tell you about a story behind the advice of “personal projects” and contribution to open source.
Last year after leaving AWS, I had quite a good open source portfolio. When I was working for AWS Professional Services, it was quite easy to put everything we did after we sanitized it through the internal open source approval process and get it published to AWS Samples
I’ve done plenty of hiring and I definitely do look at personal profiles and websites. In fact it’s the first thing I look at after experience. I can also say that a personal project of mine was a huge factor in landing a previous job. Showing competency and interest in the industry you are applying for goes a long way.
Sorry your “open source” contributions didn’t get you far. I looked at your examples and it appears to be niche documentation for AWS services, so basically all in the service of amazon? Cool.
The “AWS Solution” that I was one of the top 3 contributor to has at least 2700 people/organizations who downloaded it and I know it’s used by at least 8 state agencies - I implemented it for four agencies when I was at AWS.
Every single one of my other projects were used as part of real world six and seven figure implementations.
You think in today’s market where every req has hundreds of applications they are going to take the time to look at open source projects?
I didn’t need to nor do I have any desire to work on open source work or any other projects related to computers when I get off of work. I haven’t written a line of code that I didn’t get paid for since graduating from college in 1996.
I’m only a few years in the industry, and in my CS program, we were constantly told something along the lines of “any time you have to copy paste, look for an opportunity to abstract”. I’ve been running into problems lately where my attempts at abstractions have made things significantly more complicated. Only when I hit the limits of the abstraction I realize the cost of maintaining similar functionality in multiple places was less. I’m going to try your approach in future.
I think the reasoning for DRY was kind of lost in translation.
“any time you have to copy paste, look for an opportunity to abstract” assumes that having an abstraction is always better, but I don't think that is the case.
In my opinion the reasoning as to why "code duplication is a code smell" is that if you have to copy and paste code around you are probably missing an useful abstraction for your code. And I think "useful" is the most important thing to keep in mind.
Sure, every time I copy and paste code I know that exist an abstraction I could create to eliminate this duplication. Generally this is pretty easy. The hard part is to understand when this new abstraction will help you to deliver the features the business need.
Surely there is a parallel with standardized testing asking the most needlessly ornate prose of its students and then most writing having more value the plainer it is written.
Surely there is a parallel with standardized testing asking the most needlessly ornate prose of its students and then most writing having more value the pialner it is written.
I found setting up nix shells to be more time consuming than docker setups. Nixpkgs can require additional digging to find the correct dependencies that just work on other distributions. That being said, I’m a huge fan of NixOS, but I haven’t seen it as a replacement for docker for reproducible dev environments yet.
I agree with this. For multi-OS dev teams, I’ve set up separate compose files or Dockerfiles for dev and prod. I kept them as similar as possible while optimizing the images for prod and including the niceties for dev.
reply