63 Matching Annotations
  1. Mar 2025
    1. The goal of Lucia v3 was to be the easiest and cleanest way to implement database-backed sessions in your projects. It didn't have to be a library. I just assumed that a library will be the answer. But I ultimately came to conclusion that my assumption was wrong. I don't see this change as me abandoning the project. In fact, I think it's a step forward. If implementing sessions wasn't easy, I wouldn't be deprecating the package. But why wouldn't a library be the answer? It seems like a such an obvious answer. One word - database. I talked about how database adapters were a significant complexity tax to the library. I think a lot of people interpreted that as maintenance burden on myself. That's not wrong, but the bigger issue is how the adapters limit the API. Adapters always felt like a black box to me as both an end user and a maintainer. It's very hard to design something clean around it and makes everything clunky and fragile, especially when you need to deal with TypeScript shenanigans.
  2. Sep 2024
    1. This can be incredibly frustrating for developers. In my own experience, the person in the worst position is the developer brought in to clean up another developer’s mess. It’s now your responsibility not only to convince management that they need to slow down to give you time to fix things (which will stall sales), but also to architect everything, orchestrate the rollout, and coordinate with sales goals and marketing. Oh, and let’s not forget actually producing the code to resolve the underlying issues. It can, at times, be an insurmountable problem. A developer in that situation has to wear a lot of hats. They need to be:● An advocate to management and by extension the C-suite.● A project manager.● A marketer to understand the features and desired functionality both now and down the road, to make selling the product more simple with defined pipelines and marketable features.● A decision maker, willing to make tough calls with regards to future compatibility of the services, how they interact, and what third-party tools they might need to integrate with to ensure the rectified code will be usable for the foreseeable future.Last but not least, they need to be a good developer to fix the mess. If you employ a developer who can manage all those responsibilities as well as their day job, I guarantee you aren’t paying them enough, or they’re already looking somewhere else.

      developer solving a bug

  3. Dec 2023
  4. Oct 2023
    1. Hypercard 1992

      An introduction to Apple's Hypercard. Guests include Apple Fellow and Hypercard creator Bill Atkinson, Hypercard senior engineer Dan Winkler, author of "The Complete Hypercard Handbook" Danny Goodman, and Robert Stein, Publisher of Voyager Company. Demonstrations include Hypercard 1.0, Complete Car Cost Guide, Focal Point, Laserstacks, and National Galllery of Art. Originally broadcast in 1987. Copyright 1987 Stewart Cheifet Productions.

      User Manual

  5. Aug 2023
    1. Hire Full Stack Developers for Bespoke Needs Fulfilling An End-to-End Solution Delivery.We facilitate a dedicated team of experts who build solutions assuring clients with not just high ROI, but even sustainable and disruptive tech impact. Our full stack developers go through a strong evaluation process to be client-ready and have specialization in specific domain and industries. Our developers give a time zone advantage as we work across overlapping time zones, no matter where the client is based. HIRE NOWPrevious Hire Ecommerce DevelopersBuild and deploy fully functional, customized shops and multi-store ops. HIRE NOW Hire Mobile App DevelopersRapidly develop native iOS & Android, or cross-platform mobile apps. HIRE NOW Hire JavaScript DevelopersFor masterfully scripted, multi-platform responsive Web services. HIRE NOW Hire Web Application DevelopersLaunch Progressive Web Apps with flawless backend-frontend engineering. HIRE NOW Hire Ecommerce DevelopersBuild and deploy fully functional, customized shops and multi-store ops. HIRE NOW Hire Mobile App DevelopersRapidly develop native iOS & Android, or cross-platform mobile apps. HIRE NOW

      HireFullStackDeveloperIndia is your partners in web and mobile app development solutions. Our streamlined hiring process, adaptable engagement models, and talented experts ensure the perfect fit for your projects. Transform your digital concepts into reality with ease and excellence. Whether it's front-end UI/UX, back-end functionality, or full-stack prowess, we've got you covered. Experience the synergy of skilled professionals driving your digital aspirations forward. For a cost-effective and skilled solution, explore the opportunity to hire full stack developers India.

    1. Auto-update aside, you might also have found it hard to find a Chrome binary with a specific version. Google intentionally doesn’t make versioned Chrome downloads available, since users shouldn’t have to care about version numbers—they should always get updated to the latest version as soon as possible. This is great for users, but painful for developers needing to reproduce a bug report in an older Chrome version.
    2. Auto-update: great for users, painful for developersOne of Chrome’s most notable features is its ability to auto-update. Users are happy to know they’re running an up-to-date and secure browser version including modern Web Platform features, browser features, and bug fixes at all times.However, as a developer running a suite of end-to-end tests you might have an entirely different perspective:You want consistent, reproducible results across repeated test runs—but this may not happen if the browser executable or binary decides to update itself in between two runs.You want to pin a specific browser version and check that version number into your source code repository, so that you can check out old commits and branches and re-run the tests against the browser binary from that point in time.None of this is possible with an auto-updating browser binary. As a result, you may not want to use your regular Chrome installation for automated testing. This is the fundamental mismatch between what’s good for regular browser users versus what’s good for developers doing automated testing.
  6. Jan 2023
  7. Dec 2022
    1. I'm finding that IndieBlocks may be the way to go since most of the indieweb plugins that are out there are lacking block editor compatibility and most of them state you need classic editor enabled which isn't helpful if you are trying to move forward with the way in which WordPress is going with the block editor. Maybe some of these devs haven't "learn javascript deeply" like Matt Mullenweg suggested and are still stuck in PHP land like many of the people like me are, sadly.

      Anecdotal evidence of long time WordPress fans who are being left behind in the move to Gutenberg and more JavaScript.

  8. Sep 2022
  9. Aug 2022
  10. Mar 2022
  11. Dec 2021
  12. Nov 2021
    1. How to Choose a Reliable SaaS Application Development CompanyKateCloud & SaaS Product ResearcherDmitryCEOSaaSHomeBlogEntrepreneurshipHow to Choose a Reliable SaaS Application Development CompanyPublishedAug 5, 2020UpdatedAug 5, 202012 min readCurrently, SaaS is the largest segment of the global public cloud services market. The growing SaaS industry provides an equal-opportunity atmosphere for businesses. It concerns enterprises from startups to tech giants – and any size in between. It explains why traditional software companies, like Microsoft and Adobe, decided to look into that direction too. Indeed, the time is ripe for developing a SaaS application now. But however tempting it may be, do not dive in headfirst with launching a SaaS product, because sometimes, it can be very challenging. That is why we have prepared a guide on finding a SaaS application development company that will be your best bet.

      Looking to build a SaaS app? You will need help of a reliable development team. Check our advice on how to choose a SaaS development company.

    1. SaaS Product Development: Why Choose Ruby on Rails Framework?KateCloud & SaaS Product ResearcherRuby/RailsSaaSHomeBlogTechnologySaaS Product Development: Why Choose Ruby on Rails Framework?PublishedSep 10, 2020UpdatedSep 10, 202013 min readWhich technology to pick for your SaaS business to succeed? This question is not uncommon in our days. In fact, quite the opposite because the SaaS model has become a meaningful part of every business domain. And the demand for SaaS product development is higher than ever and still increasing. This article will discuss the essential factors you need to consider when selecting a framework for your SaaS project. Also, we will introduce the top 3 frameworks for building a SaaS product with their pros and cons. Read on to see the best examples of SaaS applications.

      Choosing the right tech stack can help you save costs and make your app stand out in the saturated market. Let’s discuss why Ruby on Rails can be your best choice.

    1. What Makes Ruby on Rails Perfect for Marketplace Development?AlinaE-Commerce & SaaS StrategistMarketplaceRuby/RailsHomeBlogEntrepreneurshipWhat Makes Ruby on Rails Perfect for Marketplace Development?PublishedJul 13, 2020UpdatedJul 13, 202012 min readThe last several years have been marked with the rise of different marketplaces. Airbnb, AliExpress, Etsy, Booking.com are on everyone’s lips. That's not surprising that the idea of launching a second Amazon or eBay seems so appealing. To win the e-commerce race, entrepreneurs focus on providing excellent customer experience and build fast-loading and scalable websites. Besides, business owners take various security measures to protect their customers’ sensitive information. This way, they can gain clients’ trust and boost sales. When building a custom marketplace, what technology stack is best to achieve all these goals? Our answer is simple: Ruby on Rails. In this article, we will fill you in on the Ruby on Rails marketplace development. At Codica, we are passionate fans of this framework and have built numerous e-commerce platforms with its help. Based on our experience, we will discuss the key reasons to choose RoR for building a successful marketplace.

      The last several years have been marked with the rise of different marketplaces. Airbnb, AliExpress, Etsy, Booking.com are on everyone’s lips. That's not surprising that the idea of launching a second Amazon or eBay seems so appealing.

      To win the e-commerce race, entrepreneurs focus on providing excellent customer experience and build fast-loading and scalable websites. Besides, business owners take various security measures to protect their customers’ sensitive information. This way, they can gain clients’ trust and boost sales.

      When building a custom marketplace, what technology stack is best to achieve all these goals? Our answer is simple: Ruby on Rails.

      In this article, we will fill you in on the Ruby on Rails marketplace development. At Codica, we are passionate fans of this framework and have built numerous e-commerce platforms with its help. Based on our experience, we will discuss the key reasons to choose RoR for building a successful marketplace.

  13. Aug 2021
  14. Jul 2021
  15. Apr 2021
  16. Mar 2021
  17. Feb 2021
  18. Dec 2020
  19. Nov 2020
  20. Oct 2020
    1. Form validation can get complex (synchronous validations, asynchronous validations, record validations, field validations, internationalization, schemas definitions...). To cope with these challenges we will leverage this into Fonk and Fonk Final Form adaptor for a React Final Form seamless integration.
    1. About the argument against it, "{@const will make code less consistent ": I think the same is true now, since people can come up with very different ways of dealing with the "computed value inside each loop/if function" problem. Some extract components, some use functions, some will prepare the array differently beforehand.
    2. it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.
  21. Sep 2020
  22. Aug 2020
  23. Jul 2020
  24. May 2020
  25. Mar 2020
    1. Because it's easier for Indiana Jones to recover the Sankara Stones than for someone with an idea for an App to find a decent App developer.  And because we wanted to finally have a place to send friends and clients who constantly ask for our help in finding developers. Yeah, we know there are more than 140,000 iPhone applications out there already, so not everyone is struggling to find a developer. But believe us, the demand outweights the supply. Hence, this site.
  26. Sep 2019
  27. Mar 2019
  28. Aug 2018
  29. Sep 2017
  30. Nov 2015
    1. Companies need to have realistic expectations of the work-life balance of open source maintainers.

      When you hire an open source developer, you hire someone who works all the time--not just 8-5, not just at a desk, not just on that one pet project that management's currently excited about. They work on that, they work on the related libraries, they work on projects that use those libraries, they work on the next great version of the libraries the company will need in two more years.

      Plan for your own future by letting your developers explore it for you. They already are...even before you've hired them.

    2. They should be treated like adults though and allowed to spend what they see as an appropriate amount of time working on the project versus other projects for the company. Trying to quanitfy/limit the amount of time leads to conflict and strife and unhappy management and employees. It doesn't work and it's not a long term, maintainable solution.

      In the end, it's a quest of trust. Hire people who work on the open source projects your company depends on. Then, let them keep doing it--for pay...at last!--and expect them to continue to balance the worlds of open source and business...as they likely already were, but now with the needle tilted slightly (or more, one would hope) in favor of working on open source code.

      It's like picking flowers. If you pick them and bring them inside, they die. Plant them in some fertile ground, however, and let them keep doing their thing. (OK, that was a bit strained...but hopefully you see my point ^_^).