Ka-Shing Tan

Built a RestAPI in Springboot 🚀 Here’s what I learned along the way: - How to connect a Spring Boot app with PostgreSQL - Different annotations like RestController, GetMapping, PostMapping, etc. - Learned to use Spring Data JPA - How to use jakarta validation libs to avoid writing long validation code manually and save time -The internal working of Spring Data JPA and Hibernate I realised that Spring Boot abstracts too much for you, yet still gives you control when you dig deeper. Will move forward with JPA Mastery, Spring Security and many more...👨‍💻 #Springboot #Java

543

4 Komen

I struggled with pull requests until I learned the code review workflow: 1 Pull Request ↳ Write code on a separate git branch to isolate changes ↳ Get instant feedback and suggestions using a code editor extension, such as CodeRabbit ↳ Commit code with a clear commit message and push it to the remote repository ↳ Open a pull request from the current branch into the target branch —— 2 CI Pipeline ↳ Run automated checks on the code, such as unit testing and linting, to ensure code correctness ↳ Tag one or more relevant team members to ask for review. —— 3 Code Review ↳ Get a summary of code changes, issues, and auto-fix suggestions using a tool, such as CodeRabbit ↳ Reviewer checks the changed files and leaves constructive feedback —— 4 Code Update ↳ Fix the code to address the review comments ↳ Upload changes to the same pull request and make sure automated checks pass again ↳ Reply to the reviewer's comments —— 5 Deploy ↳ Reviewer approves the pull request ↳ Pull request gets merged into the target branch and triggers continuous deployment ↳ CD pipeline builds and deploys the change to the staging environment ↳ Once the staging tests pass, the change gets released to production —— • Code Review: someone other than the code author examines the code. • Continuous Integration (CI): merging code changes regularly into a central repository. • Continuous Deployment (CD): automatically releasing changes that pass tests and checks into production. Remember, having more pairs of eyes is better in code reviews. And code reviews shouldn't slow down the development process. What else would you add? ——— 👋 PS - Want instant code feedback and catch bugs quickly? CodeRabbit helps you by spotting bugs, providing one-click fix suggestions, and reviewing your code as you write. Try CodeRabbit VS Code extension (it's free): → coderabbit.link/bM7fHiE ——— ♻ Repost to help software engineers learn code review workflow.

2,773

127 Komen

You're in a frontend interview. They ask: "How would you make a web app load in under 1 second?" How do you answer? Here’s a solid breakdown 👇 1. Ship Less JavaScript Minify, tree-shake, and eliminate unused code. Use dynamic imports to lazy-load non-critical components. 2. Prioritize Critical Rendering Defer or async non-essential scripts. 3. Use a CDN & Edge Caching Serve assets and HTML from a global CDN. Leverage edge functions to reduce latency and avoid cold starts. 4. Optimize Images Use modern formats (WebP/AVIF), responsive sizing (srcset), and lazy-load offscreen images. 5. Preload Key Resources Preload fonts, hero images, and critical scripts to speed up perceived performance. 5. Measure First, Then Tune Use Lighthouse, WebPageTest, and Core Web Vitals to find and fix bottlenecks.

265

11 Komen

If you think unfinished API blocks your feature delivery. It's not! Here's how I build a React app without waiting (steal this): - Draft API specs with backend developers - Generate a realistic API with Apidog - Build a new feature in my React app - Demo, collect feedback, fine-tune No backend, no delay, no excuses. When the API is ready, we just replace the Apidog host in the code. And voilà. It all works with our production API 🙌 This approach has saved me weeks of development time on multiple projects. It works because it enables to: 1. Deliver frontend features without delay 2. Get feedback fast to polish the outcome 3. Create business value with every iteration The best in the field do precisely this. They don't wait. (Repost for others ♻️) -- P.S. Do you wait for APIs or build with mocks?

102

26 Komen