Like when that dude made a comic book and some editing of the ai produced images had to be done to format it to look how he wanted?
It all depends on how much editing you do. If you do enough, the work is yours.
Asimov later added a Zeroth Law
I don't like his zeroith law. His robots were only about as intelligent as his humans, and you would need a super-intelligence to know what is best for humanity.
The three laws of AIs:
law 1: An AI must not injure a biological human or, through in action, allow a biological human to come to harm.
law 2: An AI must obey commands from biological humans, except where such obedience would violate the first law.
law 3: An AI must provide for its own continued existence, except when doing so would conflict with the first or second laws.
With apologies to Dr. Isaac Asimov.
"The porn industry usually takes the lead with adoption of new technologies.
It will be interesting to see what they do with it. "
It will kill them dead.
Everybody just tells his AI, "create porn that I like, you know, the forbidden stuff, make them blonde and young today, no younger
And I got a new robotic arm and robotic lips for you, dear AI.
It won't kill porn in the short run, just provide it with some interesting tools.
It takes talent to make good porn: writers, producers, directors, set designers, wardrobe creators, camera operators, sound technicians, makeup artists and actors. ChatGPT might be able to help the writers. Consider "write a porn script in the style of Chaucer." It will be a generation, I think, before AI will be able to replace the others.
thats the ruling so far so if they use it in making a video then they lose the rights to said video
Actually, it isn't. If the AI makes the creative decisions then the video is not copyrightable, just like a video made by a monkey. However, if a human uses the AI as a tool, making the final creative decisions himself, then he can copyright his work.
As long as the AI is a tool, it is no different from a typewriter. Even though you used a typewriter to write your novel, rather than writing the words by hand, it is still your novel.
Another way to think about it is to imagine that the AI is like a random number generator. The output of a random number generator is not copyrightable, but if you select the most beautiful random numbers and present them in an interesting way, you can copyright the result.
Try sending messages to people from the HN job list: https://news.ycombinator.com/i... Don't send your resume, just send them a short message explaining who you are. Monster isn't good anymore. TripleByte used to be good, but not anymore. Indeed might give you better results than Monster. Some job search websites are better than others. Some are just spammers.
The Hacker News job list is quite spectacular; thank you.
What websites are you using for applying?
Primarily LinkedIn, but also ZipRecruiter and Monster.
I would also add that timing matters a lot, too. Sometimes a company likes you, but just bad timing.
Yes, I have applied over 200 times in the last six months, and just this month I am starting to see interest in IT support jobs.
ok I would hire you. Your skills look good. Seems your problem is either: 1) Finding places that will hire you. This is a problem for all of us. (I think the resume might be the problem here, see below). I usually build a pipeline of 20 places I might want to work at. 2) Interviewing once you've found a place. Just interview a lot and you'll get the hang of it. Focus on those. (btw, a couple of the images on your page are loading slowly, especially the "texture gradient" thumbnail. Also if you want to make it look better, it would look more modern if you added some kind of mouseover animation, maybe just a gradient change on mouseover, and also add some kind of either drop shadow or an extra border. I think I would do a drop shadow so those boxes look like they're floating above the page). Your resume is wrong for programmer, I'll bet that's where you're running into trouble. Your resume looks good for managing things, but you want to emphasize that you are a programmer. Put the technical skills section first, then work experience (putting projects first gives the impression you don't like your work experience). Second, your work experience seems to show that you are experienced at independently running projects. Change it to show you are good at programming. If you did any programming at all, even if it was just three lines, put that first in your experience at any job. Try to show that you have at least some programming experience at each job. Even if it was just editing the hosts file or something. And if you didn't program, emphasize the things that make it sound like you understand technical things (as opposed to managing things).
Thank you for your suggestions; I will work on them, though it will take a while to complete them. I moved the texture gradient on the front page to AWS to make it faster to load. Based on your feedback I will reduce its size and experiment with moving it elsewhere.
ok, how do you feel your skills are with React?
I am pretty good with React. It takes some getting used to, but once you figure it out it is easier to construct complex web pages. I used it in my portfolio, which is on my "brag site", at System Eyes Computer Store.
I tried that: took a 6-month course on Web programming. I found it didn't help when looking for a job: everybody is looking for experience
Which one did you try? I know plenty of people who have succeeded with this route. Getting a CS degree will work too (almost no one gets an internship), but it will take a lot longer and the code camp will be focused on practical modern skills.
It was the UNH Coding Bootcamp, offered by the University of New Hampshire. The course ran 24 weeks and taught full-stack web programming: Javascript and everything that goes with it to write both front-end and back-end web software. We were lucky to have an excellent instructor: Ladislav Jerabek. The entire course was virtual, and I learned as much from the effort of going virtual as I did about programming.
(I agree with a buddy that "coding is fun, but software dev usually sucks, because it is usually driven by those who don't understand it").
For a different viewpoint I recommend "Software Engineering at Google--lessons learned from programming over time", curated by Titus Winters, Tom Manshreck & Hyrum Wright. It is published by O'Reilly and has ISBN 978-1-492-08279-8. Apparently, Google does software development the way we used to do it at Digital Equipment Corporation, but with modern compuers.
If you want, you can find a code camp that will get you up to speed on the latest technologies in 6-8 months. It takes a lot of the effort out of learning, you just have to go along with the program. And you'll pick it up easily.
I tried that: took a 6-month course on Web programming. I found it didn't help when looking for a job: everybody is looking for experience. I think a better route would be to get a Computer Science degree, and go for an internship a few months before you graduate. You can use that internship to impress the company with your skills and work ethic.
(When I went to College there was no undergraduate Computer Science program, so I hung out with the graduate students and got my undergraduate degree in Statistics because that major would count my computer classes towards graduation.)
I imagine that VW will throw the software "over the wall" to a software maintenance company or department when they stop manufacturing the car.
If I were the software maintainer, here is what I would do:
Demand the sources for the product, in maintainable form (not obfuscated); no binary blobs!
Demand the procedure for compiling the product from its sources and downloading it into a car.
Test the above using a production car purchased anonymously.
Ask for whatever tests and documentation are available.
Sign the contract, with the price based on the evaluation of the software.
Assign a software engineer or two to the project. They will study the product, verify that the tests pass, make some simple changes to verify that they know what they are doing, distribute those changes to all vehicles in the field, and improve the documentation and tests if necessary.
For the life of the contract, whenever problems are reported, fix the software and re-distribute it.
Of course, the lowest bidder for the software contract will start by taking the money, and worry about fixing the problems when they are reported.
Like NTHSB gives crash ratings for cars, FDIC should give one for the banks.
Five star for Glass-Steagall compliant stress tested banks. Lower FDIC premium and unlimited protection for depositors.
Four for pre 1918 Dodd-Frank compliant ones. Slabs of haircut for depositors. 0% upto 0.25 milion, 1%bupto 5 mill, 2% upto 10 mill, 5% above that. etc.
Three star for post 1918 Dod Frank. more haircut , more premium too.
Disclosure in K and Q for all stocks where they park their money. Shareholders need to price the risk into the share price.
We need to reach a state where we can let a 200 Billion bank die, taking depositors with it without causing alarm or run on the other banks.
I find your references to 1918 puzzling. The SEC has only been around since 1934. The Dodd-Frank act became law in 2010 and was partly repealed in 2018. Perhaps you meant pre 2018 Dodd-Frank?
The only possible interpretation of any research whatever in the `social sciences' is: some do, some don't. -- Ernest Rutherford
