This has been bothering me for a few days; I’m 99% sure that my parent is a bot. If you take a look his profile, _all_ of his comments share a remarkably similar structure.
Yes, I think you're right. Another observation: despite asking so many questions across their comments, this account also never responds to others who respond to them.
easy: how many genius people do you know who were also prodigies? early intelligence only gets you so far, the rest depends on hard work, passion, etc.
"Prodigy" and "genius" both lack rigorous definitions, so your problem might simply be one of cherry picking. Going with my own gut on each definition, here are a few examples to add to those already provided by sibling comments:
* Magnus Carlsen (chess grandmaster by 14, world champion for 10 years as an adult)
* Frédéric Chopin (concert pianist at 7, one of the top composers for piano)
* Blaise Pascal (rediscovered Euclid on his own at 12 with no training, went on to become one of the most famous mathematicians of all time).
* John van Neumann (could divide two 8-digit numbers in his head at age 6, learned calculus by 8, went on to be a founding figure in computer science).
I looked at the Star Machine repository and it looks like its using SDL_gpu [1,2], so I am a little confused about where the 'CPU' rasteriser designation comes from.
I haven't read though the whole thing, but my rough understanding is:
- A ray tracer runs on the CPUs, and generates surfels (aka splats)
- The surfels are uploaded to the GPU
- Then the GPU rasterizes the surfels into a framebuffer (and draws the UI, probably other things too)
So it's the ray tracing that's running on the CPU, not the rasterizer. Compared to a traditional CPU ray tracer, the GPU is not idle and still doing what it does best (memory intensive rasterization), and the CPU can do the branchy parts of ray tracing (which GPU ray tracing implementations struggle with).
The number of surfels can be adjusted dynamically per frame, to keep a consistent framerate, and there will be far less surfels than pixels, reducing the PCIe bandwidth requirements. The surfels can also by dynamically allocated within a frame, focusing on the parts with high-frequency detail.
It's an interesting design, and I'm curious what else is possible. Can you do temporal reproduction of surfels? Can you move materials partially onto the GPU?
Use revision control and frequently commit your work, preferably along with comments describing your thinking process. In law school I used Git as that's what I was familiar with and it made it easy to backup my work (git push), but I suppose the tracking feature in MS Word might suffice.
In law school you cite almost every sentence in a written work. In theory you don't need to cite your own, bare opinions, but even then it's common to provide citations for rhetorical effect. And legal citations are very specific and descriptive, which is why footnotes are often so long. Rigorous citation is just a good idea in any field, and they're more costly to fake, at least if they're more than just last name & year. (If you're playing a long game, make sure archive.org has a snapshot of any online sources; they provide browser extensions for that.)
It also might not be a bad idea to capture your browsing history, so you can show a timeline of how your research went. In law school this history is already captured by the legal portals as part of their billing system, but standard browsing history would be more than sufficient.
Finally, and perhaps most importantly, if you do any of this, then be consistent. Don't do this for one class but not another, or have browsing history for some papers but not others. Consistency speaks to both credibility and reliability of evidence. So it's better to have no browsing history for any than only for some. A professor in a Wills & Trust class explained it this way: one day you'll be presented with a document you helped execute 30 years ago and asked, for example, if the identities of witness signatures were verified. You'll have no direct recollection of this. But you could answer in the affirmative; you could say, "Yes, because whenever executing a document I always did X, Y, and Z, without fail." (Or alternatively, "I almost always did X, Y, and Z, and the rare exceptions are memorable".) And if you indeed were consistent about this, there'll be corroborating evidence. So if someone is skeptical about whether your Git version history was authentic, you want to be able to point them to version histories for all your most recent papers as corroborating your process.
Type your work in a Google Doc with edit history enabled. Or if you're writing code, push signed commits to a repository shared with your professor, every few hours you're working on it. Honestly, even for essays, maybe share the Google Doc with your professor ahead of time. It might annoy them but at least you're covering your bases early.
Alternatively: write about controversial topics and/or fill your paper with obscenities :)
Do what the exonerated student did - use the track changes feature in your word processor. I would think something like Github and some simple tools (so a non programmer could use easily) to provide basic version control would be a good way to track versions and time stamps of updates to docs, projects, etc.
The cynic in me says that human student papers will stand out for being badly written, while the ChatGPT cheaters will have more superficial polish (if less solid reasoning).
Sure. It's not the coarse language that I object to — it's the lazy, juvenile humour. It's similar to penisJS[0] — a software analogue to children defacing the chairs in their school classrooms with drawings of genitalia.
I think it's a pretty bad look for the industry.
Not to say there shouldn't be humour — there should be more humour. Personally, my most popular software projects are purely comedic, and they're also a little more coarse than this.
To put it another way: I'd prefer the software humour to be a little more Sean Lock and a little less Beavis and Butt-Head.
Sure, in the same way that most DE's will give you a GUI for adjusting monitor layout, but it actually working has nothing to do with the DE itself and everything to do with the underlying distro/OS.
