For asking permissions, Google should explain thé code with GPT3
But, hmmm, in 2023, really ? Google use chatgpt3, give it the developer's app or extension code, and that's all!
But, hmmm, in 2023, really ? Google use chatgpt3, give it the developer's app or extension code, and that's all!
(And I wont be able to cheat at work by using AI generated code and docs cause I am a bad dev who need to earn money decently)
What keywords or sites should I use? I dont find many relevant results.
I have picked up the most important sentences chapters by chapters and shaved them into a Google Sheet, close to pertinent code snipet provided by the doc and that illustrate the concepts.
I have added one or two sheets in thé Google Sheet that contain only a few main words picked up in thé orher sheets. It is a memento, a kind of cheat sheet.
I read this memento and, if needed, the adéquat pages every two weeks.
But I still forger important things.
I think I need to praticien but I dont fond any pertinent project that would allow me to put in practice What i have learnt.
For other and various reasons, Magnesium (Oxyde and Hydroxyde) deodorant have been created.
What are their impact on bacteria?
Is this magnesium absorbed by the body? (I bet yes, and it would not be harmful I guess).
Or to live like a Scandinavian.
I think I remember one of the things he advised was to make people feel like they were making a choice.
(A spy or someone working in the secret service of a country)
I think I remember one of the things he advised was to make people feel like they were making a choice.
But I need to know if people would be interested in paying to use this site, and if lots of people would use it.
I also need to imagine highly-specialized features that would interest manufacturers that they would not find nowhere (and idem for customers), so that my Webapp would have a real added value.
What are the steps to follow to answer those questions? Could I simply go to their forums and asks them their needs?
You know what? I actually find that 2021 front-end development has a problem of productivity.
A. Big. F*ing. Sh*ty. Problem of productivity.
Read below, my dudes.
Front-end development is better than back-end to making deadlines fly away like gulls. ;-) -> Front-end choose their techs by thinking about speeds. But not the good ones. i. Speed of frontend execution at client-side. ii. Speed of transfer of the frontend from the server to the client. iii. Even speed of execution of the frontend... backside (NextJS). -> BUT F*
MY GUYS. YOU KNOW THE F*ING WHAT? Nowadays, Internet taken as a whole is so fast, servers are so fast, clients are so fast, all is so fast that looking for fast front-end fetching queries to the server and/or for execution gains of the frontend is shallow, overengineering, USELESS. So why are you thinking about those speeds again and again and again. You would have better to throw your watermelon to the trash.What would be welcome and ACTUALLY USEFUL? I answer you in two words, 7 letters ;-). FAST. DEV. FAST DEVELOPMENT, fucking JESUS. (Well the whole list would be: fast dev + super UX-design). The other speeds? Don't care. Blablabla. Don't. F*
ing. Care.Trust me. Trust the speed of dev. It's the FUTURE.
1. What would be very useful: a kind of WYSIWYG to create responsive and UX-designed GUI for webapps and websites. You would be able to bind your WYSIWYG widgets to some logic (NodeJS Nest.JS or PHP Laravel) and both frontend and logic would be bound to some model (Strapi). You would choose the good techs in order to maximize speed of development. Should this WYSIWYG tech be open-source, proprietary, self-hosted, cloud-hosted, should it output dependent webapp/websites or actual, i.e. self-sufficiently executing webapp/websites, should this WYSIWYG be subject to versioning, all of these questions = I have my own opinion but yeah;
2. What would be useful if this tech doesn't yet exist in 2021: a fast dev frontend framework (or more exactly I should rather say: a fast dev frontend widgets&design library).
NOW MY GUYS. Read again bellow AND TRY IT.
1. Open HackerNews. Or Google. Type "low code frontend", "low-code frontend", "lowcode front-end" and whatever the syntax you want. What you will find are only 2 or 3 solutions. All except one cost the ass and are proprietary (not even open-source wtf). The last one, AppSmith, is for internal projects only (don't allow us to do responsive designs/widgets).
2. Open HackerNews....... Google.... Type "frontend" and read 10 first pages like I did. You will mostly find Next.JS + Ant design or Svelte. But are they really fast dev? Nooope my dude, nope nope nope, they just have a learning curve faster than React ;-).
You guys, I actually find that 2021 front-end development has a problem of productivity.
A. Big. F*ing. Sh*ty. Problem of productivity.