So here is the thing, this community by it's nature is mainly powered by people that actually understand what they are doing, enjoy actually using their brains to make things happen, and are likely filled with the ability to actually create real life changing technology.
AI cannot think, and just processes requests through input and generates output based from training data.
There is no passion, there is no human brain improvement or anything that we as a human race evolve from over time.
The best creations have been creations built by us and will continue to be that way.
Yes, we created AI, but what is next after AI, we still like to create things ourselves which is what fuels the creation of the next best thing.
People who pride themselves on using a prompt to get something output miss out on the intellectual stimulation and brain development that comes with doing the work yourself and collaborating with other humans to get the work done.
These build memories, group bonding, and other things that exist in the real world that will never happen if AI does all the work.
You will also notice those that offload everything to AI are horrible at thinking for themselves over time. It has to be a balance, AI has some great use cases, but should not be used for everything as that takes away the natural challenge we as humans need to have.
I have seen the devaluation of what should be done by seeing a coworker say we built this thing. When I say oh you and your girlfriend built it, amazing, then they say no me and AI did it.... I say so you mean you told it to build that thing. It give a very real false since of capability and accomplishment while not highlighting the hard fact that the prompter is not an engineer, architect, scientist and has not built any real technical skill and wastes away sending prompts to a machine while not actually growing their own capabilities.
Then said person gets frustrated because they are stuck in their job, tired due to vibe coding with no visible results on their investment of time except for loss of money they have spent on tokens. Tokens in little to no financial return is what the bulk of people are seeing because the bulk of us that spend money do not want to see the same vibe coding mess that has been spammed everywhere.
There is also the massive security issues that vibe coded apps have at scale which is very hard for a human to maintain, follow, and keep secure. As we don't know why x code is there and the logic of it being there would need to be reviewed by a human that is the only thing in the equation that can actually think.
So use it as a tool, but still continue to do the bulk of the work yourself so you continue to grow is the best route to success over a very long period of time.
If you are in the USA, you can sue for whatever you want, but you have to be the one to prove the actual law was broken.
Meta has the right to stop business with anyone they set for any reason at any time.
If they don't want you as a customer due to something your business was doing or customers you were attracting they can stop providing services to you which is not against the law. There could have been an accidental ban due to the algorithm they used, but this may also have been a risk threshold breach and it was not worth continuing business with your company due to the threshold being breached.
You don't sue because laws were broken. When you sue someone, it is a civil case, not a criminal case. You are examining case law and contracts to determine whether there is a viable torts case or contract violations that would result in you being able to prove enough damage that it is worth going to court over those issues.
So, no, it is not necessarily true that meta can stop business with anyone at any time for any reason. It is not necessarily false, either. As any attorney will tell you: "It depends."
I think this is great, gives those wanting a good formal foundation a guide to getting organized and making something happen.
With time this is also going to be great for the author with new iterations of the book, but getting in early like this can set the author and the language up for success long term.
Sounds like you have found some initial implementation problems that you have potential solutions for. The most important thing would be how secure is your appliance and how secure things are for when someone does get shell access.
Is all input validated and all output sanitized? Is the software continuously kept updated? Are you keeping up with regulations and security protocols required by the countries that your appliance is used in? Are you offering enterprise support contracts to pay for the added work of maintenance per customer?
Mistakes always cost money in terms of engineering hours spent fixing those mistakes. The feedback was poor and unacceptable from an engineering manager if the concerns are not backed by factual information and critical feedback to help steer you in the right direction you will not be able to grow.
In terms of your own self-improvement improve your internal processes for learning the code, and testing it before sending it off for a CR. Adding test cases for the work you do will help improve the quality of your work and enable it to be integrated easier into the overall codebase. If you need help or find issues with the code try to get clarification after spending time deep diving and learning and being curious (e.g., exhausted all other options).
Also note you can probably create your own dev pipeline so you can push to your hearts content and not break things, then only when things are working as expected submit a CR for others to review.
There needs to be a purpose behind the studying. Studying just to study can be done, but you will more than likely forget what you studied as it won't be applicable to anything of interest which at times is just a necessary evil.
For example I study programming language source code, kernel source code, hypervisor source assembly, gcc, LLVM, other compilers, write my own compilers, interpreters and study Assembly Language and tech specs for different architectures. My peers always wonder how I am so accurate in writing such high performance software. Well, what they don't know is I know what is going on under the hood literally down to the assembly and how what is written is processed through the chips, copper, and other elements on the board and other connected components.
I just really enjoy knowing how things really work and even better when things go wrong because I have the ability to debug down to the hardware level if necessary to fix the problem even on brand new hardware I have never seen before. As sometimes the performance or security problems are not a software issue, but a hardware issue that is holding things back or leaking secrets.
The challenge of solving hard problems is what gets me into studying which makes it fun and exciting to me as I know learning something new is just around the corner. Nothing like reading RFCs, SPEC sheets, NIST docs and more to help see the different ways things have been documented vs the actual implementation, what security loopholes were done and why there were done (mostly in the name of performance gains) and other things that the majority of people do not know of due to it being undocumented, improperly documented.
Key is to find a way to make the subject at hand somewhat of a challenge to help keep you motivated and push through it. Other engineers and scientists know that feeling of finding a breakthrough or truly understanding how something really works and that ability to squeeze every drop of performance out of something is amazing after putting in the time to study. If in the academic setting, professors respect those that can dive deep and show true mastery of the subject at hand. As most people only scratch the surface of the tech they use every day as deep understanding is not always required, but sure does bring a whole new level of fun to using or creating tech.
Yes, it is used to power many tech companies chat and text comprehension tools and services (e.g. Alexa, Siri, Hey Google, AWS Comprehend, Google Cloud Natural Language API, Azure Text Analytics, IBM Watson Natural Language Understanding, etc.)
With this customers feed the service the data or have humans or machines interact with the service and normally either conversations, metrics/analytics are derived from those services.
Example, a video might be uploaded to the service of someone that does not speak the language in the video and it has no captions, that service can then process the audio in the video and translate the text and depending on the tech do audio overlay and captions of that video to the language of the person that does not speak the original language in the video.
This could also expand into breakdowns of what was said in the video to translate into thousands of languages, pull in research data from the video, process and build a graph or other infomatics all based on what was said and seen in the video to auto determine and pull in related information based on how things were said and build on what was learned over time.
Another one could be analysis of a person talking to their infotainment system and sharing the results not only based on what they originally said, but also based on the tone and other things going on in the background to differentiate the tone and any additional context of the response. This could lead to a full on conversation that seems natural but with the information gathered allow that system to do a large amount of planning, ordering and other background tasks to accommodate the requests of the user for large planning items (wedding, property management, taxes, accounting, security, plane trips, etc.).
From reviewing your site it appears to be an official Microsoft website as you are using their trademarked logos as your favicon, the Microsoft design style and all around the site without properly notifying visitors up front that you are not officially affiliated with Microsoft. If you are, then you should have this listed on the site and link to your partner status validation with Microsoft.
This is why it has been marked as a phishing site due to not properly identifying your affiliation. There is no footer with the details of the business behind the site and the about us page does not properly identify your company or business information which is very common on phishing websites.
Best practice is to come up with a unique web design that is not easily comparable to the products main vendor that you are creating a service for. Once you have properly identified the site and changed the design you might be able to get unsuspended, but for now the site looks and feels like a phishing website.
Thanks, do you think I can't use anything from the Fluent UI ? I just wanted to build a useful App to connect license supplier with users and optimize the used licenses
Nice work you have here, I will go ahead and ask for the curious ones what is your background and what would your top recommended books, videos, and additional educational resources that you used to learn C and game development in C?
Also, have you thought about making your own indie game studio to do this full time or on the side if you are not already doing so?
Not OP but I'm currently writing a game in C: just throw yourself into it. The language itself is minimal enough that you probably won't need much guidance other than looking up library functions and with modern tools like the various sanitizers in clang and valgrind it's hard to go too wrong.
AI cannot think, and just processes requests through input and generates output based from training data.
There is no passion, there is no human brain improvement or anything that we as a human race evolve from over time.
The best creations have been creations built by us and will continue to be that way.
Yes, we created AI, but what is next after AI, we still like to create things ourselves which is what fuels the creation of the next best thing.
People who pride themselves on using a prompt to get something output miss out on the intellectual stimulation and brain development that comes with doing the work yourself and collaborating with other humans to get the work done.
These build memories, group bonding, and other things that exist in the real world that will never happen if AI does all the work.
You will also notice those that offload everything to AI are horrible at thinking for themselves over time. It has to be a balance, AI has some great use cases, but should not be used for everything as that takes away the natural challenge we as humans need to have.
I have seen the devaluation of what should be done by seeing a coworker say we built this thing. When I say oh you and your girlfriend built it, amazing, then they say no me and AI did it.... I say so you mean you told it to build that thing. It give a very real false since of capability and accomplishment while not highlighting the hard fact that the prompter is not an engineer, architect, scientist and has not built any real technical skill and wastes away sending prompts to a machine while not actually growing their own capabilities.
Then said person gets frustrated because they are stuck in their job, tired due to vibe coding with no visible results on their investment of time except for loss of money they have spent on tokens. Tokens in little to no financial return is what the bulk of people are seeing because the bulk of us that spend money do not want to see the same vibe coding mess that has been spammed everywhere.
There is also the massive security issues that vibe coded apps have at scale which is very hard for a human to maintain, follow, and keep secure. As we don't know why x code is there and the logic of it being there would need to be reviewed by a human that is the only thing in the equation that can actually think.
So use it as a tool, but still continue to do the bulk of the work yourself so you continue to grow is the best route to success over a very long period of time.
reply