S M Abu Taher

Firebase vs. Supabase: Why I ditched Firebase and moved my backend to Supabase I’m currently building a production-level app with Supabase, I was initially skeptical about moving away from Firebase, but my client's main requirement was to avoid using Firebase due to its cost and the risk of becoming too dependent on the Google ecosystem. Once you get dependent on it, there is no going back, So we decided to use Supabase and the experience has been phenomenal! Supabase offers everything I love about Firebase but with the added benefits of SQL. The migration process was straightforward, and now I have more flexibility and control over my backend. The real-time features and seamless authentication make it perfect for my projects. Additionally, the ability to write complex queries and use familiar SQL tools has significantly improved our data management. The performance improvements and scalability options have also been impressive. Supabase’s detailed documentation and active community support have made the transition smooth and enjoyable Have you used Supabase before? If yes, what was your experience?

7

2 ความคิดเห็น

Why I Would Choose C# over Golang If I Want to Create My Own Startup App 😅 As an experienced Go developer, if I were to write a startup application, I would definitely choose C#. While both C# and Golang have their strengths, I believe C# is more suitable for startup needs. Here are my reasons: 🍪 Robust Web API Development .NET WebApi are surprisingly easy to work with. They offer: ☕ Built-in Swagger support for API documentation ☕ Simple routing via attributes ☕ Integrated dependency injection These features allow developers to focus more on business logic rather than boilerplate code. 🍪 Powerful ORM with Entity Framework While I initially had reservations about Entity Framework (EF), I've come to appreciate its capabilities for simple web apps. EF's syntax is more intuitive and powerful compared to Golang ORMs like Ent and GORM. For those who prefer alternatives, Dapper is always an option. 🍪 Excellent IDE Support C# benefits from two outstanding IDEs: Visual Studio and Rider. These powerful development environments offer advanced features like intelligent code completion, debugging tools, and integrated testing, which can significantly boost productivity and code quality. 🍪 Stable and Mature Ecosystem C# and .NET have a more stable and mature ecosystem compared to Go. This stability is crucial for a startup, as it means: ☕ More reliable third-party libraries and frameworks ☕ Better long-term support and maintenance ☕ A larger pool of experienced developers ☕ More established best practices and design patterns This stability can be a significant advantage when building and scaling a startup application. 🍪 Balanced Performance and Productivity While Go excels in simplicity and is great for smaller, lighter cross-platform utilities and serverless applications, C# offers a good balance of performance and productivity for a wide range of applications. That said, Go still has its advantages: ☕ Simpler syntax and concepts ☕ Excellent for building small, efficient utilities ☕ Superior in serverless environments However, for a startup app, the robust features and maturity of C# outweigh these benefits. 🧋 Conclusion Choosing between C# and Go isn't about finding a "magical productivity potion." Both languages have their strengths. For a startup app, C#'s combination of easy-to-use WebApis, powerful ORM options, and a stable, mature ecosystem make it the better choice. The final decision depends on your specific needs and preferences. Remember, the best language is often the one you and your team are most comfortable with and can be most productive in. For me, right now, that language is C#. #dotnet #csharp #go #golang #benchmark

10

Supabase is important for me. As a frontend developer, I do not have much time to explore Backend stuff. So, I depend a lot on backend-as-a-service services like Supabase. If anyone would also like to learn about Supabase, this book might be a good start. Book Link: https://supa.guide/ #supabase

31

5 ความคิดเห็น

Week 4 🍃 (✨New topic) ✨ We're doing QA DevAssure Community Hours on Discord ✨ 5 PM(IST) tomorrow and every Thursday 🚀 Join us tomorrow ✨ https://lnkd.in/gFQkDmDi Agenda - Mobile App Automation (Appium Setup and Challenges)✨ - Recent news in QA and Test Automation Space - Sharing your experiences and stories with your favorite open source tools - Share useful resources with the community, and discussion on them #devassure #mobiletestautomation #qa #appium #community

8

🚀 Just Learned About Testing in Golang! 🛠️ I’ve been diving into unit testing in Go, and it’s really helping me write more reliable and maintainable code. Here's what I explored: Manual tests: Set up basic tests to check for errors in functions like division. Table-driven tests: This method made it super easy to test multiple scenarios using a single function by looping through various inputs and expected outcomes. By running tests for both valid and invalid data, I can now easily catch potential issues before they become problems in production! If you’re working with Go, testing is definitely something you should get into early on—it’ll save you a lot of headaches later. Would love to hear about how others handle testing in Go or any other languages! Let’s connect and share ideas. #GoLang #TestingInGo #CodingJourney #UnitTesting #SoftwareDevelopment #Programming #LearningInPublic Golang Golang Jobs Golang Dev Golang Development golang.dk #tests

2

Mocking backend API with React - Using mirage.js https://lnkd.in/g-VhEiAA

14

1 ความคิดเห็น

I recently switched from Jest to Vitest for testing my Next.js backend API routes, and here’s why: - Breaking Packages: I kept encountering issues with packages like query-string breaking when using Jest. Switching to Vitest solved these problems and handled those packages smoothly. - Modern JavaScript & TypeScript Support: Vitest natively supports ES6+ syntax and integrates seamlessly with TypeScript, allowing me to write modern, type-safe tests without additional setup. - Fast but…: Vitest is fasr, but I encountered an issue with how my buildup and teardown processes communicated with the database, which caused interference between test files. To fix this, I disabled running files in parallel. - Smooth Migration: Despite the adjustments, migrating from Jest was still simple. Vitest’s API is very similar to Jest’s, making the transition quick and painless. If you’re dealing with package conflicts in Jest or need TypeScript support out of the box, Vitest might be the solution for your testing setup! #Nextjs #Vitest #Testing #TypeScript #APITesting #WebDevelopment #DeveloperTools

5

Apple : QA Role interview questions Round 1: 1. Tell me about yourself 2. More about e-commerce domain 3. Scenarios to test music player application 4. Non-functional test cases for Pencil 5. Http and Https protocols? 6. What is the 500,400 status codes? 7. What is Cache and Cookies in web application? 8. How to review and back track if the 100th build gets failed? 9. Test scenarios for PDP page 10. Explain your framework 11. What will be the test data for testing music player application? 12. What tech stack used in your organisation? 13. What do you do in performance testing? Which tool you have used and how the load is decided for testing? 14. What is SDLC? 15. WAP to find the third largest number in the given array? Round 2: TestNG question: @Test test1(){ String text="sdds"; } @Test(dependsOnMethod="test1",priority=1) test2(){ //Second test method } 1. What's the execution order? Will there be any runtime or compile errors thrown? 2. How to get dynamic data from test1 method and pass it to test2 method as test data? Java: Int amount = 596 Denominations: output: 1 note of 500 1 note of 50 2 note of 20 1 note of 5 1 note of 1 29

4

1 ความคิดเห็น

5 Kotlin Interview Questions with Answers: Questions: 1. lateinit vs lazy in Kotlin 2. Difference between == and === in Kotlin 3. What is a JvmStatic Annotation in Kotlin? 4. What is a reified keyword in Kotlin? 5. Suspending vs Blocking in Kotlin Coroutines 1. lateinit vs lazy: `lateinit` is used for non-null, late-initialized vars, ideal for dependencies that cannot be initialized in the constructor. `lazy` is for vals, initializing them upon first access, useful for resource-intensive objects.   2. Difference between == and ===: `==` checks structural equality (via the equals method), while `===` checks referential equality, seeing if two references point to the same object. 3. JvmStatic annotation: This Kotlin annotation makes a member function of an object or companion object accessible as a static method from Java code, facilitating smoother Java-Kotlin interoperability. 4. Reified keyword: Used with inline functions, it allows type parameters to be accessed at runtime, which is normally not possible due to type erasure in generics. 5. Suspending vs Blocking: Suspending functions in coroutines free up the thread to do other tasks, unlike blocking, which keeps the thread occupied until the operation completes, leading to potential performance issues. #kotlin #android

51

1 ความคิดเห็น

PHP 8.4 Officially Released ->Property Hooks ->Asymmetric Property Visibility ->Lazy Objects ->PDO driver-specific subclasses ->BCMath object type and more

12

1 ความคิดเห็น

A modern FE stack that I would recommend for any new project: - Package Manager: BunJS - Linter: ESLint, StyleLint - Bundler: Vite - Server state: ReactQuery - API calls: Axios - UI state: Zustand, Jotai - Forms, tables: Tanstack - CSS framework: TailwindCSS - Validations: Zod #frontend #techstack #webdevelopment #architecture

24

好久沒來寫筆記了 如何使用 GitHub Actions 將 React TypeScript 項目部署到 GitHub Pages https://lnkd.in/gfJDNE4Z How to Deploy a React TypeScript Project to GitHub Pages using GitHub Actions https://lnkd.in/gVrcirkr #devops #React #Typescript #GitHub

1

Java EE vs. Spring Framework: Choosing the Right Enterprise Development Platform During my whole career as a Senior Software Engineer, I've mainly been involved with Java EE, later known as Jakarta EE, which has been the backbone of my activity within enterprise development. Thanks to its robust and standardized platform, Java EE has enabled the creation of scalable, maintainable, and secure applications for large-scale environments. Dependency Injection, Transactions, Messaging, and Web Services-Great set of APIs. Meanwhile, I have studied the Spring Framework and got a good grasp of its strong points. Spring is pretty flexible and modular, hence exciting for many developers. The innovative approach, especially regarding Spring Boot and microservices, allows for an agile development experience that contrasts with the more structured and standardized nature of Java EE. Though my expertise lies in Java EE, I see the additional value brought in by Spring: Standardization vs. Flexibility: While standardization promotes consistency and therefore compatibility, Java EE is ideal for large organizations where standardization is a factor. Spring, with its flexible architecture, supports adaptability and thereby fosters innovation more easily. Learning Curve: While Java EE has an initial gradual learning curve with comprehensive specifications, Spring is easier to pick up but takes longer to learn about the full-depth features of its ecosystem. Community and Support: Both Java EE and Spring possess strong communities, but the fast-paced rate of new technology adoption into Spring and the community-driven nature of development usually leads to quicker innovations. This is my personal experience: where enterprise projects deal with stability and compliance to industry standards, Java EE comes first among my preferred frameworks. At the same time, having some knowledge of Spring allows me to appreciate its benefits in environments where agility and microservices are key. Each one of these has its merits, and knowing when to use which is key to doing successful projects. #JavaEE #SpringFramework #EnterpriseSoftware #Java #SoftwareEngineering #BackendDevelopment

23

8 ความคิดเห็น

🌟 Day 3: Operators in Kotlin 🌟 Understanding Operators in Kotlin 🔢 Operators in Kotlin are special symbols that perform operations on variables and values. Kotlin supports several types of operators: • Arithmetic Operators: Perform basic math operations: +, -, *, /, % val sum = 5 + 3 // Result: 8 • Relational Operators: Compare two values: ==, !=, <, >, <=, >= val isEqual = (5 == 3) // Result: false • Logical Operators: Combine multiple conditions: && (AND), || (OR), ! (NOT) val isTrue = (5 > 3) && (3 > 1) // Result: true Combining Operators for Complex Expressions 🔗 You can combine multiple operators to create more complex expressions: val a = 10 val b = 5 val result = (a + b) * 2 // Result: 30 Did You Know? 🤩 Kotlin operators are intuitive and follow the same rules as mathematical operations, making your code clean and easy to read! 🧮 Question: What's your favorite operator in Kotlin, and how do you use it in your projects? Share below! ✍️ Stay tuned for Day 4: Control Flow with if and when in Kotlin! 🔄

43

3 ความคิดเห็น

Hi everyone, This month, I have created some repositories that might be helpful, especially for Golang programming. I developed a Go utility and a clean architecture template. I hope these repositories can assist you in your projects. Here are the repositories: 1. Go Utility: https://lnkd.in/g6sXhUpS (latest tag v0.0.7) 2. Template Service Go: https://lnkd.in/g96GZ2FT Feel free to integrate these repositories into your projects. If you have any suggestions, you can message me directly on LinkedIn. What Next ? I will write a detailed description on how to use these repositories and publish it on Medium. I will share it as soon as it’s ready. Let me know in the comments if you're interested in this project.

98

How does Swift memory management work for structures In Swift, memory management for structs works differently from classes due to the value type semantics of structs. Here's an overview of how Swift manages memory with structs: Value Type - Structs are value types in Swift. When you assign a struct to a new variable or pass it to a function, a copy of the struct is created. This means each instance of a struct is independent of others. Stack vs. Heap Allocation - Stack Allocation: In many cases, structs are allocated on the stack, making memory access faster. When a function or a scope ends, the stack memory is automatically deallocated. - Heap Allocation: If a struct contains reference types (e.g., classes, closures, or objects), those will be allocated on the heap, and reference counting (ARC) will manage their memory. However, the struct itself is still passed by value. Copy-on-Write (CoW) Optimization Swift uses a copy-on-write (CoW) mechanism to optimize memory usage for certain types like `Array`, `Dictionary`, and `Set`. For example, if two variables refer to the same data, a copy of that data is not made until one of the variables is modified. This optimization minimizes unnecessary copying. - When a struct is copied, Swift only makes a copy when you attempt to modify the data. Until then, both variables will reference the same underlying data. - If either variable modifies the data, Swift creates a new copy for that variable (hence the term "copy-on-write"). Memory Efficiency - Swift's memory management for structs is generally more efficient than classes because of the absence of ARC (automatic reference counting) for the struct itself. Structs don't need to keep track of references like classes do, so they avoid the overhead associated with reference counting unless they hold reference types. Summary: - Structs are passed by value, so copies are made when assigned to new variables or passed to functions. - Memory for structs is typically allocated on the stack, except when they contain reference types. - Copy-on-write (CoW) optimization helps avoid unnecessary memory duplication. - Structs containing reference types are managed via ARC for those specific reference types. #arc #ios #interview #apple #swift #developer #memorymanagement #structure #stack #heap

5

How to upgrade an Astro JS project from Tailwind CSS v3 to Tailwind CSS v4 ( Alpha ) With the recent release of Tailwind CSS v4 by the Tailwind Labs team, it’s time to explore how to upgrade an Astro JS project to Tailwind CSS v4 (Alpha), based on the information available. https://lnkd.in/dGduzptu

1

🚀 Automate Your Mobile Testing with Appium! 🚀  Excited to share this visual representation of Appium, a leading open-source tool for automating mobile applications. Whether you're working on Android or iOS, Appium provides a robust framework to ensure your apps are tested thoroughly and efficiently.  🔍 Key Features Highlighted:  Cross-Platform: Supports both Android and iOS, allowing you to write tests for multiple platforms using the same API.  Open Source: Free to use and backed by a strong community of developers.  Versatile: Compatible with various programming languages like Java, Python, and JavaScript.  No Need for App Modifications: Test your apps without needing to recompile or modify them.  Why Choose Appium?  Flexibility: Write tests in your preferred language and framework.  Scalability: Easily integrate with CI/CD pipelines for continuous testing.  Community Support: Benefit from a wealth of resources and community-driven improvements.  How Appium Can Benefit Your Projects:  Efficiency: Automate repetitive testing tasks, saving time and resources.  Reliability: Ensure your app performs well across different devices and operating systems.  Quality Assurance: Detect and fix issues early in the development cycle, improving overall app quality.  This tool is a game-changer for anyone involved in mobile app development and testing. By integrating Appium into your workflow, you can deliver high-quality, reliable mobile applications that meet user expectations.  #Appium #MobileTesting #Automation #SoftwareDevelopment #QualityAssurance #OpenSource #TechTools 😊 

5