Details
-
AboutVR/AR indie game developer and consultant
-
Skillsblender UE4 c++ c# blueprint image editing all the VR headsets Android AR Core fuck ios
-
Locationnew hampshire
-
Website
-
Github
Joined devRant on 8/13/2017
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Fuck off you disturbed snowflakes with your SJW bullshit.
I get it, words cause damage, but words taken out of context for emotional self pity is on you.
Ok I expressed my feelings on the matter, see you next year for the next round!12 -
That moment when you ask your friend if he/she has plugged it in and they say yes and your answer is ”send a picture” and they respond with this....12
-
Whats your weirdest bug/issue in your code? Which you couldnt figure out why, but it was something simple and you was Like ”oh how could i miss that...” etc.
I need to have some fun in my life right now haha.7 -
Late night thought :
Google is a search engine company having with an operating system(Android) as a side product.
Microsoft is an operating system company having a search engine (bing) as a side product.6 -
When you're really stuck on a problem amd rubber duck is of no use..
The supper effective silver terminatior duck with diamond is here to help!!4 -
If you have to program in JavaScript, don't forget to drink water. Excessive crying could dehydrates your body very quickly.3
-
Just found that some of the movies published in the late 2000's are actually published at perfect resolutions to completely fill ultrawide displays (1920x800 renders perfectly on a 2560x1080). At least those ultrawides are good for watching some video content without black bars 😄
-
A guide to estimations.
1) don’t give an immediate answer. The first “timeframe” you give will be held against you and will result in overtime and working weekends.
2) think of a relevant piece of work and the time that took.
2.1) if it’s something you haven’t done before, add some adequate research time.
3) allow half a day of testing for every day of development.
4) add a day as buffer - this is good for on the fly bug fixes
5) calculate time
6) now give an educated estimate.
7) this should take you 5 seconds to get through mentally.
8) if scope creep occurs: goto:15