Works for the time being while there's low hanging fruit, but researchers will use those exploits to help build more robust systems.
Eventually there'll be no point in doing it anymore.
121–130 of 206 posts
Works for the time being while there's low hanging fruit, but researchers will use those exploits to help build more robust systems.
Eventually there'll be no point in doing it anymore.
Earlier quoted context omitted.
In most jurisdictions, a professional engineer is essentially a specific legal thing. In most jurisdictions I am aware of, software engineers are not professional engineers. I am sure there are many exceptions. That said, I think all of the above are rather easy to apply to SWE aside from, arguably, the first bullet point.
And I can list counter examples for each. Civil engineers and architects don’t “move fast and break things” or “fake it til you make it” after a 3 month bootcamp.
There are others, like consumer app development, where there's simply no need for that kind of process, so it doesn't exist. HNers might complain, but average people don't care if their social media app crashes once in a while and they have to restart it — so why should developers care? Better to spend their time on other stuff. Whereas people care a lot if their airplane crashes.
I don't think it suggests anything about the relative value of working in those domains.
Calling yourself a Prompt Engineer makes me think you don’t know college math and computer science. Prompt Engineer sounds like a Subway employee calling themselves a sandwich artist.
My advice? Don't fight it, accept it and embrace the change. Don't sell yourself short, you only need to put in like 3 months of work to earn that Principal Prompt Engineer title!
Earlier quoted context omitted.
Hard to apply those to software engineering as well.
In most jurisdictions, a professional engineer is essentially a specific legal thing. In most jurisdictions I am aware of, software engineers are not professional engineers. I am sure there are many exceptions. That said, I think all of the above are rather easy to apply to SWE aside from, arguably, the first bullet point.
Professional engineers are typically: * Regulated by a profession and associated legislation * Work first to ensure the safety and welfare of the public * Perform only within their area of competence * Act as faithful agents or trustees for their clients * Avoid deception and represent matters in an objective and truthful manner * Invest in continuous professional development * Can be subject to penalties for malprac…
Earlier quoted context omitted.
Eh yes and no. "Traditional" engineering professions, ones where you need to get licensed, are all grounded in physics. Software engineering isn't (ignore the fact that bits running on silicon is physics, it's irrelevant). Software engineering is based on best practices and algorithms that are based on...some guy writing them, saying they're good, and others trusting that they're good. There's a million different way…
Engineering = Applied Physics. Software Engineering = Applied Math. Both are about modelling, so you have a good idea if a solution works before you build it. If you're gluing stuff together and hoping it's not going to fall apart too often you're not doing either.
Applied Physics = Applied Math.
Earlier quoted context omitted.
And I can list counter examples for each. Civil engineers and architects don’t “move fast and break things” or “fake it til you make it” after a 3 month bootcamp.
There are software engineering domains, like aerospace, where the process is very stringent with rigorous planning and testing. There are others, like consumer app development, where there's simply no need for that kind of process, so it doesn't exist. HNers might complain, but average people don't care if their social media app crashes once in a while and they have to restart it — so why should developers care? Bett…
Earlier quoted context omitted.
There are software engineering domains, like aerospace, where the process is very stringent with rigorous planning and testing. There are others, like consumer app development, where there's simply no need for that kind of process, so it doesn't exist. HNers might complain, but average people don't care if their social media app crashes once in a while and they have to restart it — so why should developers care? Bett…
But those consumer apps that use or sell personal data against that persons interests as a business model, or those that leak or lose personal information through negligence are very harmful to society. Why should they get a pass?
Earlier quoted context omitted.
LLMs are very quirky. They need the correct context to produce something good and it’s often surprising what that needed context is. OP just play around with midjourney and you’ll soon realize that it is a very real thing
100%. People who have not tried to interact with these models don't understand there is actually quite a lot of skill in navigating the latent space.