EZeats (ez-eats.com)| Software Engineers | On-site in Cairo, Egypt (remote possible in MENA region)
We are shaping the future of F&B and contactless dining with a cutting-edge POS tailored for the MENA region.
Open Roles:
- Senior Backend Developer (NestJS): Expert in architecting scalable backend systems using NestJS, with deep proficiency in cloud platforms, microservices, and API optimization. Collaborates with cross-functional teams to deliver secure, high-performance solutions aligned with industry best practices.
- Senior React Native Mobile Developer: Skilled in building cross-platform mobile apps with React Native, focusing on performance optimization, third-party integrations, and CI/CD pipelines. Partners with designers and product teams to craft intuitive, user-centric mobile experiences.
- Senior UI/UX Designer (F&B Products): Specializes in creating visually compelling, user-friendly interfaces for food and beverage platforms, leveraging user research, wireframing, and prototyping. Balances brand identity with usability to drive customer engagement and business growth.
- Senior Product Manager (F&B Products): Leads end-to-end product strategy for F&B digital solutions, from market analysis to roadmap execution. Bridges stakeholder needs with technical teams to innovate and scale products in a competitive industry landscape.
if you are interested send your resume to [email protected] with the job position in the title.
The original document initially mentioned the 'software industry' and I indicated that by signing it, I would be legally agreeing not to work in the software industry at all. They mentioned they would provide a more specific definition, but I still found it unusual. I understand signing an NDA, but a non-compete agreement feels more like giving them the right to sue me if they choose to.
That's what I am trying to say. Personally, I don't mind if my code is being used for commercial or not. I do mind when Microsoft uses my code without a reference and asks me to pay for copilot just because they decided to put it behind a paywall.
Still, it's good to be an option. If you see this as an advancement you can choose something like MIT if you don't like your code to be trained by a paid copilot then you can choose something like MIT-Human only.
It's a better solution than don't use GitHub at all. And whether we like it or not, a new license should be introduced to address the new data model.
There should be a new open-source license specifically designed to restrict the use of code for commercial purposes, whether it involves training machine learning models or not. It could be similar to GPL but tailored specifically for the field of machine learning, ensuring that the code cannot be utilized for ML commercial purposes or trained without limitation.
Thanks for pointing out the accessibility issue. DFlex stands for a better user experience that includes of course adding accessibility to the main mechanism. At least the essential one. But at this moment, the project is still in development mode and many things need to improve including accessibility.
It's not the size of the package. DFlex is actually small compared to other libraries. But I need to reconsider the size of the demo container before updating the version because when you resize there's a possibility to add a scroll to the container. Adding/removing scroll while dragging is not shipped yet.
Demos in the site are behind the current version and not being updated to the latest one [1]. And updating the demos will take a while since I have to take resizing containers into consideration. So the current version is 2.x.x while the last one was 3.7.0. Sorry about that.
In the drag-and-drop context, an interactive element is an element that can traverse the DOM tree and change its position without causing a layout shift and with a proper reconciler and transformation mechanism.
Cloning elements and duplicating containers are what DFlex tries to avoid. Because the usual implementation is to clone the element (ghost it) and then append a new one with a fixed position. The result is to reconstruct the DOM tree directly with every user interaction which leads to poor user experience and not a very practical transformation. That's why the default thing to do with DFlex is not to clone or change the element position unless there's a need to do so, for example: transforming from a container with a scroll.
In the nutshell, it's designed to drag an element into a droppable area. So let's say you are dragging a file to be uploaded, in this case, it makes perfect sense to use HTML API. Otherwise, you need a framework that can orchestrate the transformation. It's like using React. In theory, you can manipulate DOM directly in the browser but instead, you use a framework to build your app.
We are shaping the future of F&B and contactless dining with a cutting-edge POS tailored for the MENA region.
Open Roles:
- Senior Backend Developer (NestJS): Expert in architecting scalable backend systems using NestJS, with deep proficiency in cloud platforms, microservices, and API optimization. Collaborates with cross-functional teams to deliver secure, high-performance solutions aligned with industry best practices.
- Senior React Native Mobile Developer: Skilled in building cross-platform mobile apps with React Native, focusing on performance optimization, third-party integrations, and CI/CD pipelines. Partners with designers and product teams to craft intuitive, user-centric mobile experiences.
- Senior UI/UX Designer (F&B Products): Specializes in creating visually compelling, user-friendly interfaces for food and beverage platforms, leveraging user research, wireframing, and prototyping. Balances brand identity with usability to drive customer engagement and business growth.
- Senior Product Manager (F&B Products): Leads end-to-end product strategy for F&B digital solutions, from market analysis to roadmap execution. Bridges stakeholder needs with technical teams to innovate and scale products in a competitive industry landscape.
if you are interested send your resume to [email protected] with the job position in the title.