@James i urge you to stack this with Stark. You might hate me now but will thank me later.
I wonder how valuable this title would be for people who already have years of experience in the software engineering industry
A bit of a late reply, but I figured the “years of experience” thing was worth replying to, plus I wanted to indicate how this title has been going for me since starting it back in late May.
Even though I have written plenty of software in my time, collaborative work in a team using a VCS doing things like submitting pull requests (PR), working with other developers using modern methods, and generally doing anything other than designing the entire software product myself from start to finish is something I have had very little experience with.
Similarly, even though I have written banking software in the past (submitting direct debit files, working with secure payment solutions etc), writing graphics software or software that relies a lot of graphics and physics is a whole different ball game than doing something where you are certain of the inputs and you’re just manipulating data.
I think even people with “years of experience” are going to benefit from the ability to quickly switch gears and think algorithmically using this sub. Because it doesn’t matter how many years of experience you have with (insert your favourite framework or API here), there is always more to learn if you’re not going to simply “specialise” in writing one particular type of code very well. You need to be able to very quickly switch gears and grasp very complex mathematical ideas in order to “keep up” with modern APIs.
I spoke to a local programmer who wrote the library I am using to write my own VR programs. He admitted to me that the process of learning Vulkan (a graphics and GPU API) for him was an extremely painful process of trial and error and that they could not recommend any particular tutorial for getting up to speed.
If you’ve ever tried to read the specifications for OpenXR or Vulkan, they are long meandering paragraphs of incredibly concise, precise and yet largely indecipherable language which are frustratingly under-illuminating until you read and re-read the paragraphs multiple times (or stand on your head and look at the paragraphs in a mirror, as if you were receiving a riddle from Entil’Zha
ffs). And yet I have managed to get enough up to speed with them in the past month or so to feel confident with writing the custom rendering code I need to write to begin my own app over this next week. I couldn’t say that literally a couple of days ago, but its an incremental thing where every new tutorial you read gets you a little closer towards your goal.
I would say using the sub the small amount I have in my stack has definitely helped. What I’ve noticed the most is how this sub will help you grasp on to a problem like a bulldog and just not let it go, even if it is painful to your mind (full disclosure: definitely take additional supplements if you’re not solely using IG UPX, particularly choline/ALCAR or whatever your doc/adviser recommends) until you have a solution. This can be particularly difficult if you have a sedentary lifestyle or if you are running a sub like Khan Black along with it, because the intensity of thought goes through the roof. But that dogged ability to find a solution is something that so far I can only uniquely ascribe to this particular sub.
Curious to hear how this compares to other peoples experiences.
So i guess this is the perfect subliminal for software developers and data/cloud engineers?
exactly
I can confirm now that using Index Gate: UPX, I’ve managed to go from knowing no Rust or Vulkan, to having a working Vulkan renderpass that does color blending and depth buffering.
Other than trivial tweaks to the code to get it to render to screen rather than as picture in picture, it’s 100% working. Now, like I said a few posts back, the experience of most people who go from knowing no 3D graphics APIs to trying to learn Vulkan find themselves lost due to the complexity of the spec. The guy I mentioned called it a painful process of trial and error. I am currently two months in to my business, wasted a couple of weeks due to recon on other subs and personal circumstances, but still come out with a solid understanding of the API at the end of two months. And I could have reached this level of knowledge a lot sooner if I had been a bit more focused with my daily work and wasn’t dealing with trying hard to keep a regular schedule, and being delayed thanks to the massive levels of distractions online lately.
I would say that’s pretty solid evidence that it’s helped. Bear in mind that IG is not the only sub I’ve been running (KB has been strong in there along with Paragon regularly and periods of WB, GLMC and scattered other subs). It’s not a focused stack, but there are enough repetitions in there of IG that I feel it when it kicks in. So others that have a more focused stack might have an even better outcome.
I am more than eager to run this after I’m done with my mission stacked.
I have this project running, coastal reform program involving corals, mangroves, and sea weeds. I build up a Unity design concept where we grow those three components at sea and a virtual interface is available for students at the campus to interact. Maybe I got overwhelm with the sensors, or whatever I got stuck, but I won’t rush this - this can wait till I run UPX.
I’m a coder myself, university computer engineer. For beginners that feel like giving up, just know it takes a while to get the hang of coding. It’s like a different way of thinking. But one day it will click. You’re not stupid!
I remember this douche bag teacher at university during a demo exam for our intro course to coding (you present your program and code). He literally said to this one girl “Darling, have you even picked the right education?”. Of course she quit 2 months later and went to be a nurse. Which is messed up because she was so smart in math, a course I failed 3 times, but he discouraged her. Plus our intro course was C. Which is probably one of the most unforgiving languages to code in.
Keep going, it’s worth it. I personally did a book called Learn Python The Hard Way before university to learn some coding.
(Not saying health care is for stupid people. But she picked this education for a reason. The industry needs more women. And this guy discouraged her.)
I find myself thinking in whatever language I’m working with. Lately it’s a lot of PHP.
I know of a problem, and I’ll start thinking algorithmically. As far as “seeing” PHP in my mind’s eye and then try to imagine I’m a computer running the code…tweaking as it goes.
It’s fun.
That’s awesome. Yes, I love getting these visions and then trying to make the PC understand what I want and make the vision a reality. Dealing with the limits is the language, the tech etc along the way. And once that programs run, it’s so satisfying.
I have a custom 2 core Stark and Indexgate.
The manifestations are really powerful.
I am in a cushy tech role on over 100K euros a year.
It was a long, hard journey. There were times when i wanted to jump ship but hung in there.
The resilence and focus to never giveup is strong.
The sales page mentions networking. I found this on Reddit
Ran this today. Made myself slow down a bit and re read some instructional material. Starting to understand a language I was worried I wouldn’t be able to figure out.
Further along than I have ever been
Congrats on your success - well done.
Does the Stark/Index Gate combo make you obsessive when working towards a goal?
James, really happy to hear that. I don’t comment much on your posts but I do follow them closely. Keep pushing man - you seem closer to hitting your goals than ever before.
Have both in a custom in QTKS, yes it does in regards to tech if you like the tech. Was solving a complex AI implementation into the cloud and i took a whole 12 hours to solve it without realizing 12 hours have passed because I was so into resolving the problem but on the other hand if you don’t like the tech or what your doing it will be a lot harder to finish.
Does it help with imposter syndrome in general or imposter syndrome specific to coding skills?