Tyler Haun

Scalability is an overused word in startups (often uttered by software engineers). Startups go through big changes. These changes come with code rewrites (refactoring more than 40% codebase is a nightmare you shouldn't wish on anyone). Writing scalable, extensible, high-test coverage code isn't worth the trouble here. You'll start seeing ghosts where none exist. Favoring iteration speed and adaptability is a better bet. Outsource, simplify and hack your way through! Cheers! P.S. In large organisations, the investment in extensible code makes sense. Hence the emphasis on low-level design. If you want to know how scalable systems are built in the real-word, try the system design course at InterviewReady. #Scalability #Startups

191

11 Comments

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

It’s official: landing a software engineering job is tougher now than it was just a few years ago. With many startups shutting down and big companies laying off employees, candidates with 0-5 years of experience are feeling the pinch. What can you do? Shift your storytelling from tools and languages to the impact you've made. Highlight who your users were, how you improved their lives, and any recognition you received. Remember, outcomes matter more than just the technologies you used!

2

I built a basic web scraper on Replit using Claude 3.5 Sonnet as my guide. When I started experimenting, I tried to build a web scraper using Puppeteer, but I struggled to configure it in Replit. After a few tries, Claude helped me build a web scraper that didn't use Puppeteer. Currently, the tool scrapes a site for its title and all H1, H2, and H3 elements, returning them to the console. #webscraper #learninpublic #lowcode #webdev

27

3 Comments

How Do Engineers Feel About LeetCode? Favorable Opinion: - Many engineers appreciate LeetCode for its extensive library of problems, which helps them improve their problem-solving skills and learn new algorithms and data structures. - LeetCode offers a structured way to practice coding, allowing users to track their progress and focus on areas where they need improvement. - The platform is popular among those who enjoy competitive programming and coding contests. Unfavorable Opinion: - Some engineers feel that LeetCode problems can be overly theoretical and not reflective of real-world software engineering tasks. - The pressure to perform well in LeetCode-style interviews can add stress, leading some engineers to feel that the focus on algorithmic challenges is excessive. - Preparing for interviews using LeetCode can be very time-consuming, which might be difficult for engineers with busy schedules. - Critics argue that LeetCode-style interviews place too much emphasis on algorithmic skills, potentially overlooking other important aspects of software engineering like system design, practical coding experience, and soft skills.

7

5 Comments

Everyone: please keep your variable names self-explanatory CockroachDB: hold my beer 🙃 While I was skimming the Pebble codebase, I stumbled on an oddly long variable name that was quite verbose. Look at the attached snippet. By the way, the code snippet is from a database called Pebble, which is a KV store by CockroachDB, and it acts as their primary storage engine. It has a very similar API as RocksDB, but instead of going for absolute drop-in replacement, Pebble took a different part and diverged. They documented the differences between RocksDB and Pebble, and it is a must-read document if you find database internals amusing. If not the entire document just read how they implement Range Deletions; pretty fascinating stuff. ref: https://lnkd.in/dWMG9G53 ref: https://lnkd.in/g64YgNnH ⚡ I keep writing and sharing these engineering nuggets, so if you are keen on learning them, follow along. youtube.com/c/ArpitBhayani #AsliEngineering #DatabaseInternals

448

10 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,238

118 Comments

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

9

Wanna grow faster in your career as a software engineer? 🌱 My #1 piece of advice to junior or mid-level devs working under a senior engineer is you should do everything you can to save your senior’s time. Senior devs are typically extremely busy, often needing to provide support for many other devs. Your job while working under them is to enable them to be a “force multiplier” across the team by having them unblock you and your teammates only when necessary. You should be spending 3-4x more of your own time to save the senior one unit of their time. You will learn so much more by doing this and increase your velocity towards becoming a senior yourself. For example, during code reviews, take extra time to carefully go over your PRs line-by-line 1 final time before asking for a review from your senior. This has many benefits: 1. Increased code quality: You will often spot many improvements to code quality & readability, or discover edge cases you did not previously consider. 2. Faster development cycle: The fewer comments your senior needs to leave per review will decrease the number of total iterations. Counterintuitively, if you spend twice as much time carefully reviewing your PRs, you may find it actually significantly increases the amount of features you are able to ship. 3. Get your PRs prioritized for review more quickly: Writing comments about basic mistakes & improvements is extremely tedious for seniors, but if your PRs consistently have very few of these mistakes, the senior will notice and will be more likely to review your code instead of pushing it to the back of their todo list. If you consistently find ways to save your senior’s time, you can quickly become their “right hand person” they turn to for future high-impact tasks; and if you are consistently demonstrating impact within your organization, a promotion is likely soon to follow. If you found this helpful, repost, comment & send me a connection request! 🤝

81

5 Comments

🚀 **Exciting News!** 🚀 I just launched a new project on GitHub: **Finance Job Scraper**! 🎉 🔍 **Finance Job Scraper** is a Node.js application designed to extract job listings from various finance-related job portals. Whether you're looking for opportunities at Taishin Bank, Cathay United Bank, E.SUN FHC, or SinoPac Holdings, this tool has got you covered! 🔗 Check out the project here: [Finance Job Scraper on GitHub](https://lnkd.in/gzQM4Pjy) ### Key Features: - 🌐 Scrapes job listings from multiple financial institutions - ⚡ Fast and efficient data extraction - 📊 Detailed logging with Winston - 🔧 Easy to configure and extend ### API Endpoints: - `/taishin/jobs` - Retrieve job listings from Taishin Bank - `/cathaybk/jobs` - Retrieve job listings from Cathay United Bank - `/esunfhc/jobs` - Retrieve job listings from E.SUN FHC ### How to Use: 1. Clone the repository 2. Install dependencies with `npm install` 3. Start the application with `npm start` ### Contributions Welcome! If you're interested in contributing, feel free to fork the repository and submit a pull request. Let's make this tool even better together! 💪 #NodeJS #WebScraping #Finance #JobListings #OpenSource

8

These new S3 conditional writes are super useful (https://lnkd.in/etbu6dRr), and now also available in Ampt!

12

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

1- The best software engineers don't work for the government 2- Software is increasingly embedded in our lives Given 1 and 2: our lives are increasingly operated by bad software I have a radical proposal. Allow top software engineers to pay taxes by coding better government software instead of paying money.

63

19 Comments

Would you hire a software engineer with 10+ years of experience, or someone with 10 years less but with raw intelligence? Mark Zuckerberg prefers the latter. Technical skills ARE important. But here are 2 key factors to account for when hiring: → 𝗥𝗮𝘄 𝗶𝗻𝘁𝗲𝗹𝗹𝗶𝗴𝗲𝗻𝗰𝗲 Someone with raw intelligence can learn faster and adapt in ways a more experienced person might not. It’s about curiosity, problem-solving, and adaptability. You don’t always need the person who’s done it all—you need someone who can figure it out. → 𝗔𝗹𝗶𝗴𝗻𝗺𝗲𝗻𝘁 𝘄𝗶𝘁𝗵 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 𝗴𝗼𝗮𝗹𝘀: Shared values and goals keep the ship moving in the right direction. With everyone rowing towards the same vision, the impact is exponential. The end goal: A ship that keeps on sailing when you jump off (read: exit). What do you prioritize more when hiring—experience or potential? __ Interested in productivity frameworks, insights about entrepreneurship, and success stories? Subscribe to my newsletter: https://t2m.io/OUvcJ5gL #entrepreneurship #venturecapital #startup #mergers #acquisitions Serial Entrepreneur & Investor Helping Startups Become Unstoppable – David Hauser

97

12 Comments

Don’t just build software. Do what the most productive engineers do: Sh*t yourself. Create powerful abstractions and reusable components with your P**. Look for patterns where you can standardize to ramp up your productivity. ✨✨✨ Hi I'm James, a senior software engineer sharing his absolute hatred for this industry one post at a time. 💥 Follow me for more tech tips 💥

42

8 Comments

Things for every developer to consider... Why do we lump data structures and algorithms together? How will learning another algorithm help if you're not getting interviews? Most people with 5 years of experience know zero agorithms Years later, someone (me) will tell you this is NOT a smart way to go about getting a job! Reading the next point won't help I told you! As you're still here, take my careers course and then you won't have to read posts like this any more! #softwaredevelopment #jobsintech #careeradvice

17

3 Comments

Which has more audience ? 1.) How to get into Big Tech as a SWE OR 2.) How to grow to senior/staff roles from new grad. I see a lot of folks on Youtube teaching DSA, System Design and selling courses online which caters to 1 But don’t find enough channels focused on 2 Does that mean there is more audience for 1 ? #softwareengineering

53

22 Comments

The State of the Software Engineering Job Market in 2024 The job market for software engineers is shifting yet again. After a challenging 2023—the first market contraction since 2000—we’re seeing cautious growth in 2024. But it’s not business as usual. Here’s what you need to know: Key Trends: 1️⃣ Tech Giants Hiring Less: Companies like Amazon, Google, and Microsoft have slowed hiring. Meanwhile, Apple and Meta are maintaining steadier recruitment levels. 2️⃣ Emerging Tech Hubs: While SF, Seattle, and NYC remain strong, cities like Austin and Miami are becoming serious contenders. 3️⃣ Hot Skills in Demand: Cloud computing, AI, and cybersecurity are top priorities. Proficiency in Python and JavaScript? Still 🔥. 4️⃣ Remote Work Evolves: Remote opportunities are stabilizing. Hybrid models—combining in-office and remote—are now the norm. What This Means for You: • Stay Ahead of the Curve: Upskill in emerging tech areas. • Network Strategically: Build connections in high-growth regions and industries. • Be Flexible: Consider hybrid roles and opportunities beyond traditional tech hubs. The market may be cautious, but opportunity still exists for those who adapt quickly. Let’s keep learning, evolving, and landing those dream roles! 💼 #SoftwareEngineering #CareerGrowth #TechJobs #ThePlacementCode

46

David Wheeler: PGConf.dev 2024 Just wrapped up an intense week at PGConf.dev 2024 in Vancouver. David Wheeler’s [@theory] extensive recap [link to post] just reignited my PostgreSQL fandom. Spoiler: It's hard not to be excited. Álvaro Herrera took us on an exciting SQL/JSON journey that culminates in Postgres 17, wrapping up a decade-long saga of development. JSON aficionados, our time is now. Abigale Kim's "Anarchy in the Database" resonated. Pairing extensions revealed 17% failure rates, and a call for managing extension compatibility made perfect sense. Extension authors, let’s talk ABI stability and load order. Collations from A to Z? Jeff Davis and Jeremy Schneider ensured none of us would ever again take collation set-up lightly. PostgresSQL 17's unchanging Unicode collation provider? Genius. Margo Seltzer asked, “Can PostgreSQL scale to a virtually infinite memory pool?” Still pondering, but massive in-memory DBs sound like sci-fi turning real. Andrey Borodin's tricks? Over my head but intriguing. Speed matters, people. Lastly, inclusivity got its due with Amit Langote, Masahiko Sawada, and Melanie Plageman discussing how diversity fuels innovation. Bonus: Robert Haas's mentoring program is on the horizon. For those who missed it – PGConf.dev's a wild ride of camaraderie, deep dives, and fresh ideas. Looking forward to next year! #PostgreSQL #PGConfDev #DatabaseNerdery #PostgresExtensions #SQLJSON 🏷️ Tags: #ÁlvaroHerrera #AbigaleKim #JeffDavis #JeremySchneider #MargoSeltzer #AndreyBorodin #AmitLangote #MasahikoSawada #MelaniePlageman You can find the full article here: https://postgr.es/p/6yG

1