Peter Park

Check out this treasure trove of resources By Arvind Telharkar! Perfect for leveling up skills.

2

1 Comment

Carta's data is ....off? Coastal Recruiting communicates with hundreds of engineers weekly, primarily in New York and San Francisco. We consistently encounter software engineers with 2-6 years of experience requesting base salaries between $180,000 and $250,000, plus equity. Perhaps "misleading" is a better term, as I frequently hear founders saying, "But Carta indicates we can hire this engineer for $140,000 to $160,000." We then observe Seed/Series A companies paying $200,000 to $300,000 for top talent. The disconnect may stem from the fact that companies raising funds from Sequoia, Khosla, Founders Fund, Lightspeed, a16z, KP, Greylock, Index, NEA, Lux, and others are not seeking what 95% of the companies providing data to Carta are seeking. These companies are looking for the top 0.01% of engineers. I say all this while also acknowledging my appreciation for Carta. I value the data and charts it provides, but it's important to remember: "There are three kinds of lies: lies, damned lies, and statistics."

26

9 Comments

So you think you can code? If you are a TRUE Full Stack developer who wants to see just how far they can take their Javascript (Node.js, Vue, Vuetify and AWS) skills and you're looking for a brotherhood of like-minded inventor/ ubergeek/ entrepreneurial table tennis champions...check out the first comment for the link to find out more and APPLY! 🤓 🔥 P.s. Salary is outstanding for outstanding humans 🔥 But for now...a short story by Nix Stephens, the late and lovely Robin Williams and ChatGPT about someone who called themselves a Full Stack developer, but wasn't really... Alright, folks, gather around for a tale of tech turmoil and code calamity! So, there's this full stack developer, right? Picture him, with his laptop adorned with stickers boasting JavaScript, Node.js, Vue, Vuetify, and AWS. He struts around the office like a digital demigod, proclaiming, "I can code anything your heart desires with these tools!" But here's the kicker—when it comes down to it, he's more lost than a penguin in the Sahara. He's like, "I'm gonna build a web app that's gonna revolutionize the internet!" And everyone's like, "Alright, let's see it, Picasso of Programming!" So, he fires up his laptop, cracks his knuckles like he's about to conduct a coding symphony, and then... nothing. The screen stares back at him blanker than a politician's promises. He starts typing away like a caffeinated monkey, hoping something magical will happen. Spoiler alert: it doesn't. He's sweating bullets, cursing under his breath, and suddenly, he's on the phone with tech support, begging for mercy like a knight facing a dragon. "Help me, oh mighty support wizard, for I have tangled myself in the webs of my own incompetence!" And that, my friends, is the tragicomic tale of the full stack developer who talked the talk but couldn't walk the walk. Remember, folks, in the world of coding, humility is the greatest debugging tool of them all! #ThinkYouCanCode #TrueFullStack

8

1 Comment

Want to get your hands on a copy of Async Rust? Solve the task below!

1

Automate the deployment process by ensuring that the state of a Kubernetes cluster matches the configurations stored in a Git repository. It facilitates version control, tracking, and auditing of Kubernetes manifests, making deployments more consistent, reliable, and auditable.

4

Wonderful Explanation of Spring and Spring Boot ... #softwaredevelopers #javadevelopers #javadeveloper #recruiterwings #learninganddevelopment #springbootframework #springframework

7

Your new hire might be on their way out sooner than you think: Wondering why? According to SHRM, 20% of new hires leave within the first 45 days. But why? Bonus: Sharing Editable Resume template to get dream jobs Meta Resume Template for Software Engineers Get it here: https://lnkd.in/gU6QZsBu 🍏 Apple Resume Template for Software Engineers Get it here: https://lnkd.in/gW-8ab9z 📦 Amazon Resume Template for Software Engineers Get it here: https://lnkd.in/gP-YZyfD 🍿 Netflix Resume Template for Software Engineers Get it here: https://lnkd.in/g6FWDNZF There are several reasons, including: ➜ Inadequate training ➜ Lack of feedback ➜ Poor integration into the team ➜ Job not meeting expectations You can change this trend. Employers with a well-structured onboarding program see a 69% higher retention rate over three years. (Source: LinkedIn) The secret? Support from day one. Here's a roadmap to take care of your new hires: Days 1-30: ➜ Meet the team. ➜ Complete necessary training. ➜ Set initial goals. ➜ Learn company values. Days 31-60: ➜ Grasp key performance indicators (KPIs). ➜ Discuss performance progress. ➜ Expand your internal network. ➜ Start small projects. Days 61-90: ➜ Propose solutions to problems. ➜ Continue skill development. ➜ Stay organized to meet deadlines. ➜ Keep building trust with the team. Days 91-120: ➜ Review overall performance. ➜ Optimize workflows. ➜ Seek continuous feedback. ➜ Plan for long-term objectives. Don’t just onboard—educate. Don’t just onboard—connect. Don’t just onboard—empower. Credit:- Justin Mecham and Want a PDF of his top infographics? 👇 ▶️ Go Here: https://lnkd.in/g2xbnwhp Please repost to help others! ♻️

78

30 Comments

Ever notice how the truly exceptional engineers rarely chase the latest frameworks? After 10 years of building software, the pattern is clear: the best engineers master fundamentals, not frameworks. Clean code. System design. Problem decomposition. When evaluating engineers for complex projects, I don't ask about Next.js or Svelte. I ask: - Can you architect for scale? - Can you write code others can understand? - Can you debug across the stack? - Can you make the right technical tradeoffs? These skills are timeless. Framework-agnostic. They'll outlast every trend. Master the basics. Everything else is just syntax.

20

Software engineers tend to be attached to their favorite tools. If you’re working with a dev agency, consider this: They’ll make tech choices that you'll live with long-term. When you eventually build your in-house team, you’ll inherit the impact of their decisions. - Is there a supportive tech community? - Is there up-to-date documentation on APIs and libraries? - Will you be able to hire developers who know or can quickly learn the stack? There are lots of factors in making tech choices. Even if you’re not technical, understand why the agency makes its decisions.

1

To be considered good, your code must communicate clearly to other developers. Writing code to meet a story, task or feature requirement is only the beginning. When interviewing developers I include a coding exercise. I don’t even bother running the code to see if it works. I’m not interested in that. Just having working code is the lowest level of skill you can achieve. I’m looking for exceptionally awesome developers, and those developers understand that others will read their code 100x over. They understand that it needs to be easy for their code to be extended in the future. The problem solved and the solution need to be clear. Complexity needs to be handled carefully, and code should be as simple as possible. Acceptance criteria, what your product person and stakeholders want, even what will satisfy your customer is only the beginning. You have a team of developers and software engineering leaders around you. Always be mindful of how others will understand and work with your code in the future. This is one reason why automated tests are a core requirement of the job. Tests are a great way to know what the code is supposed to do, what edge cases are being handled and what contract you’re fulfilling. Tests show your intent for the code. When I work on code I haven’t seen before, I look at the tests first. They give me the context of what was intended and tell me much more about the code than anything else. I once helped a startup in the very early days, we were building a payment system. The best solution I could come up with was an implementation of double entry accounting. This enabled money to move between accounts and provided built in reconciliations and audit trails. The challenge was, no one else in the team knew what double entry accounting was. I had to write code that others would need to understand, when they most likely didn’t know the concepts or foundations it was built on. I really enjoyed writing that code, as the tests, the API, the comments and the code itself all needed to communicate clearly how money was being moved through the system. It was difficult but satisfying to know others extended it beyond my time there. Other developers that interact with your code will judge your level of skill by how easy your code is to work with. Make life easy for them!

71

13 Comments

Clean Code: Principles for Better Software Development 🧑‍💻 Avoid Technical Debt: Learn how clean code helps prevent long-term maintenance challenges and boosts developer productivity. 📝 Clean Code Principles: Discover key concepts like the Boy Scout Rule, DRY, KISS, and meaningful naming conventions for better code quality. 🚀 Pragmatic Coding: Balance idealism and real-world constraints by writing code that's easy to read, understand, and maintain. 🧪 TDD and Testing: Follow the F.I.R.S.T. principles for fast, independent, and reliable tests to ensure quality from the start. 💡 Insights from Experts: Draw inspiration from Robert C. Martin, Martin Fowler, and Hernán Wilkinson on writing clean, effective software.

2

Software engineers, it’s time to reality-check your salary dreams. I’m tired of hearing inflated salary expectations from developers who do not know what the market pays. Do you think you deserve 3x more? I’ve got financial data that says otherwise. Advice: a) Listen to your recruiter. We’ve done our homework. b) Be humble. Market value is what companies are willing to pay, not what you think you deserve. c) Adjust your expectations or watch your opportunities disappear. Trust me, we want to get you the best deal. But when your numbers exceed the CEO’s, it’s time for a severe reality check. Keep arguing with the people who hold the data and see how far that gets you in this competitive market. PS: The more you earn, the more we make, so believe me, it is in our best interest for you to have more than Elon Musk. But reality is what we can't bypass. PPS: Always stick to market value. If it's too low for you, we can add 20% on top to sound reasonable. If even that's too low for you, you are too low for us to waste our time further. #SalaryRealityCheck #RecruiterTruths #SoftwareEngineerSalaries #MarketValueMatters #RealTalkRecruitment

4

Seriously, stop with the certificates. No one cares. If you are a dev ops engineer then by all means, get AWS certs or whatever your team requires. For the rest of you JavaScript developers out there - just stop. Learning how to deploy, roll back and automate code going from your machine out to the world is an actual skill. You can 𝗹𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 𝗯𝗮𝘀𝗶𝗰𝘀 𝗯𝘆 𝘂𝘀𝗶𝗻𝗴 𝘁𝗼𝗼𝗹𝘀 𝗹𝗶𝗸𝗲 𝗚𝗶𝘁𝗛𝘂𝗯 𝗮𝗰𝘁𝗶𝗼𝗻𝘀 𝘁𝗼 𝘁𝗿𝗶𝗴𝗴𝗲𝗿 𝗮 𝗯𝘂𝗶𝗹𝗱 𝗮𝗻𝗱 𝗱𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗼𝗳 𝘆𝗼𝘂𝗿 𝗰𝗼𝗱𝗲 𝘁𝗼 𝗮 𝗰𝗹𝗼𝘂𝗱 𝘀𝗲𝗿𝘃𝗶𝗰𝗲 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝗿 𝗹𝗶𝗸𝗲 𝗔𝗪𝗦. Think through how you would rollback the code if an error happened. - How will you monitor the deployment? - What the hell does a "rollback" even mean? - What git branching strategies make sense for your team? 𝗛𝗼𝘄 𝗮𝗯𝗼𝘂𝘁 𝗳𝗼𝗿 𝗮 𝘁𝗲𝗮𝗺 𝗼𝗳 𝟭 𝗶𝗳 𝘆𝗼𝘂'𝗿𝗲 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝘁𝗼 𝗰𝗼𝗱𝗲? Googling those 3 questions should lead you down some interesting rabbit holes.

312

43 Comments

Some tips if you are working in a startup (as a backend engineer): #1. Keep logic away from the DB -- Avoid triggers and stored procedures. -- Put all application logic in your server. Simple constraints like primary key, and NOT NULL are fine to have in the database. Complex validations (Users can comment once in three minutes) should be in the app. #2. Don't delete data -- How do you delete a user? Set the status as deleted. -- How do you update an invoice? Insert a fresh record. Keeping old records helps debug systems. Don't overwrite stuff that you will need later. A fresh insertion is better. #3. Logging is not a substitute for testing I see codebases where everything is logged. It's a symptom of poor testing. "Request {object} received" "Processing {object}" "Cache miss." "DB {query}" "DB {response}" "Response {object} cached." "Response sent {object}" You don't need to log so much. Engineers can see how their code behaves and infer what went wrong (as long as the request path is obvious). Instead, just log these lines: "Request {object} received" "Response sent {object}" It's enough to know what happened. If you get an exception, log that instead of the response. #4. Know (enough) about your libraries If you are using a framework or library, it's good to know a little about how it works internally. You needn't be an expert at it. Learn with a "Need-to-know-basis" :p ------- If you want to deep-dive into the internals of distributed systems, try the system design course at InterviewReady (Good for SDE-I to Staff Engg). All the best! #SoftwareEngineering #BestPractices #Startups

2,239

118 Comments

Kicking off the weekend by wrapping up my latest blog post on how to customize the Spring Boot banner with details from the pom.xml. This was a fun project for me. It's not common to see people customizing the Spring Boot banner, but it's a great way to add unique branding and include useful project information. Please check out my article, if this sounds interesting to you. #SpringBoot #Blog #Programing #SoftwareDevelopment #Java

26

1 Comment

The vast majority of candidates that I am speaking with are struggling to get multiple interviews booked in. In this market, it goes without saying that preparation is key to success. Here's 50 interview questions (from beginner to more advanced) that you may encounter when being interviewed for a TypeScript position: #typescript #interview #recruitment #hiring Uneek Global https://lnkd.in/enKjz-zz

4

These Nuget packages always find a way into my projects... Do you use any of the Nuget packages I mentioned? 👇 What are the Nugets that you can't live without? Let's hear! 👇 ♻️ Remember to reshare with your network! #SoftwareDevelopment #SoftwareEngineer #SoftwareEngineering

42

11 Comments

These Nuget packages always find a way into my projects... Do you use any of the Nuget packages I mentioned? 👇 What are the Nugets that you can't live without? Let's hear! 👇 ♻️ Remember to reshare with your network! #SoftwareDevelopment #SoftwareEngineer #SoftwareEngineering

32

7 Comments