10 karma · joined May 29, 2023
Socials: - aymanjaber2012@gmail.com
---
Remote: Yes (preferred)
Willing to relocate: Yes
Technologies: TypeScript, JavaScript, React, Next.js, Redux, Ruby on Rails, PostgreSQL, GraphQL, AWS, Supabase, LangChain, RAG
Résumé / Website: https://aymanjabr.com/ Github: https://github.com/AymanJabr LinkedIn: https://www.linkedin.com/in/ayman-jabr/
Email: aymanjaber2012@gmail.com
Experience: 4+ years
Full-stack developer with 4+ years of experience building scalable web infrastructure and AI-powered applications. Led technical development at DAITECK, architecting full-stack solutions from concept to deployment. At EXTENDI, I delivered high-performance React applications for clients like Lego and government agencies. Expertise in Ruby on Rails, modern JavaScript ecosystems, and agile methodologies.
Looking for: Full-time roles, preferably with startups with equity as part of the compensation.
This would also cripple a lot of business in advertising, but not a big loss, if someone really wants to talk to you, they can pay the price.
What am I missing? Why would this not work? What side effects on other industries could there be?
Remove all of this, just let me directly use your app, I want to search and create engines on the fly.
I don't need to save them for future uses, if I am not going to use your app even once.
If you want this to take off, it needs to just work, no extra steps unless I want to.
1) Use libraries like ShadCn that give you all of the functionality that you need for the components. Use Tailwind or other frameworks, to change the styling of these components to fit your application theme. Using the components and theme, let Claude 3.7 design the apps for you, it is good enough to get you to pretty decent and custom pages that do (mostly) work. If there is a specific page that you don't like, then you can redesign it.
2) Do the designs in Figma, and then use Builder.io to convert the designs directly into code, use Cursor to fix anything that builder has broken.
Of course, the 2 methods above can be mix and matched, this is what I have personally used in both startups and more established company projects.
All pretty standard stuff, and you can set it up in a day, a lot of the boring work can be done by LLMs, so you won't have to waste a lot of time on it.
I find that just doing the above things gives a project enough stability, and it gives the developers enough courage to refactor with confidence and ship relatively fast.
At the end of the day Software Architecture is a craft, if a system is not working for you or your team (or you don't understand why you are doing something), then you want to look at changing it.
Data privacy is of course very important, but not something the general public is super interested in.
The author doesn't give any practical solution to the problem, or things anyone could do to improve their specific or general situation, we call that whining.
Taking the words of Government officials who have the blessing of the military to "whistleblow" is just not good enough.