36 karma · joined February 23, 2014
I've never edited voxel models with the spritestacking 2D technique, I'll give it a try. Is it more efficient than placing voxels in a 3D viewport?
On a side note I've been building my own very simple voxel editor in VR you can take a look at it here: https://www.youtube.com/watch?v=tiaGvePo6jo
A thing that keeps worrying me is the amount of people I've seen/chatted with (empirical evidence) that don't trust these vaccines. The most common comments they make are: "I don't want to be guinea pig", "How do I know the government won't control me", and more conspiracy theories. All of these fears seem to come from misinformation on the internet, friends and family get a ton of memes/fake news through WhatsApp highlighting the unproven negative effects of the vaccine. Is there any effective way to control the propagation of misinformation on these platforms? How would one even get started to tackle that problem?
I used this first book as a project to learn Clojure https://github.com/ElHacker/rt-in-weekend-clojure
I'm slowly going through the 3 books series https://github.com/RayTracing/raytracing.github.io/
This past weekend I finished the second book "The Next Week", also implemented it in Clojure https://github.com/ElHacker/rt-next-week-clojure
It's been a great source for learning!
I'm sure this is happening in about 3-5 years from now, but not in your smart phone, but in an augmented reality glasses-like device (we can probably already build demos for this on NReal or Hololens). The HUD is going to be embedded in the real world. People will be able to control what information they show in their profile. I've seen some VR social apps already doing a very basic version of this, albeit in a 100% simulated environment.
I believe VR is coming very close to going main stream, probably in less than 5 years from now. Oculus Quest 2 is IMO by far the best overall VR device ever, and things will only improve from here. That's why I've recently made a career change to work full time on VR application development, I truly think this is the next big computing platform.
I'm working on building VR applications with Unity and C#. For that task I have to say that VSCode works pretty well, it has a ton of really nice features I regularly use: like debugging unity code, autocomplete/snippets from the unity API, and my favorite Zen Mode. My biggest complain with VSCode is how slow it runs sometimes, I can type faster than VSCode refreshes which adds noise to my flow, note that I don't consider myself to be a fast typist. If they would only fix that I would be very happy with it.
I find it very useful to easily navigate to the files I'm working with in the current commit.
Hope you find it useful as well.
From the site: "During inference, our system operates at 25fps on 320x240 images and 4-5fps on 800x1100 images using a GTX1080 graphics card."
For good VR/AR experiences you'll want better FPS
Does anyone has any suggestions on papers that try to solve that problem?
It would be very interesting to create a secret fake person profile and publish AI generated music under that fake name and see if humans feel identified with the lyrics and music. See how far it goes, who knows, maybe create the next super star. Then to later reveal the secret.
Developing discipline is difficult and expensive. At the beginning is a hard process. You need to get used to come everyday, sit down and do whatever you are supposed to do. The first few days/weeks you might want to set an special time for your activity. This time slot must be immovable and sacred. As the days go by you will develop a certain dependency on your routine, I call that effect momentum. Once you get a bit of momentum everything becomes easier and very enjoyable.
I'm on the process of developing discipline myself. I come everyday for 1 to 2 hours after my day job, sit down, grab an English etymology book to improve my vocabulary, and do the exercises very methodically. I do this because English is not my first language. The days I don't do my work I notice that something is missing, I even feel guilty for not pushing myself to do my daily routine. Using excuses makes my guilt even worse. That's why I do my best to not fail my routine.
When applied, discipline is a powerful tool to fully develop any of your ideas. And that's where the real value is.
The truly job of a founder is to focus on what really matters: user satisfaction. Working on the features they need, creating a 10x quality product, being the best at the specific area your startup is aiming at. Everything else will follow.
The monolithic approach makes more sense for big companies that have a large portfolio of projects, an army of software engineers and the resources to develop their own tools around a SCM. This solves several problems like multiple commits per minute, resolving ever occurring merge conflicts, code search queries and code sharing. Someone might argue that it can slowdown the development process by having to load tons of data on a local machine but this issue can be solved by creating the correct custom tooling to download a sub node of the overall repo. At this scale level this is the only feasible solution to empower developer productiveness and to avoid headaches in keeping track of a long array of projects.
The project-based repositories solution has nice qualities as well: Service oriented projects, clearcut responsibilities and clear dependencies. This seems to be a good solution for a small to middle scale organization. Can design a well documented interface for every service and even expose some of those services to external clients when needed https://www.nginx.com/blog/microservices-at-netflix-architec... . Not that this service design solution is incompatible with a monolithic approach, is just that is easier to come up with a simpler answer when having silos of knowledge.
At the lower scale, where most startups reside. Either one seems to be a reasonable approach. Albeit a startup doesn't have the resources nor the time to spend on developing custom tools to manage a monolithic repo, it turns out they don't need to, because they have a small amount of developers and ongoing commit traffic. A plain simple git repo works as well as a multi repo. This is a matter of taste and the organization the founders/early employees wish to create for their project.