slindsey
Joined 15 years ago
Joined 15 years ago
The problem with Firefox currently is the organizational structure; the way that they need to monetize; the fact that you can't pay for Firefox development. The problem with forks is that they are all "Firefox plus this" or "Firefox without that".
I can read a book, learn about the concepts, then use or repeat those concepts. The AI can do the same. But is it really "learning"? It may be just spewing out pieces of the content without any understanding. In which case it's a copyright violation, right?
After a few months something would happen and I'd stop. Then after a few more months, the pain would start again and I'd get back into it the same way.
Separate from that, there don't appear to be any benefits to having it "integrated" into GitLab. I'm assuming we'll switch to another tool shortly.
The simple answer is probably Google Docs with all the tracking and collaboration turned on so that every change is tracked by who made it and when. But again, that's only relevant for the text and maybe minimal layout.
Capture the Flag (CTF) in computer security is an exercise in which participants attempt to find text strings, called "flags", which are secretly hidden in purposefully-vulnerable programs or websites.
An LLM is regurgitating what it reads, true or false. There's a bias for things it sees more often. There's randomness in the response. Sure, humans are error-prone but a problem with known computer responses is that humans tend to think "a computer did this so it must be right." And LLMs are not pumping out true thoughtful answers but simply putting a string of probably words together.
The internet is vast and is increasingly filled with garbage, stolen and duplicated data, and monetization. It's nice to be able to look in the nooks and crannies of the internet for data.
I'm actually more interested in sites that do personal curation of interesting links that are personally vetted and of interest to someone than what's found through google or chatgpt.
No. Computer Science (CS) is the basis. It's the fundamentals underneath Software Engineering (SE).
The author is trying to convey that current CS education is not enough to create a good Software Engineer, which is true. But SE is a specialization and CS is a broad overview of the core components of a computing education.
If you want to create a comparison to Civil Engineering (CE), this isn't it. CS to SE is more like the underlying physics that support the specifics of Structural Engineering.
A more apt comparison is that the low-level programmer who takes a spec and just implements it is the "welding"; this would be that fresh hire out of college in their first position.