Need answers before signing up? No problem, check out our FAQs below. If you still cannot find the answer, please visit the Contact page to send us a message.
What makes us different?
We like to think we offer a unique, easy to understand perspective that the majority of people will understand. With our close attention to detail, high standard for best practices and a passion for knowledge we think we can offer something truly satisfying.
Isn’t all this information already free on the internet?
Yes and no. Obviously some of these algorithms already exist. We do not claim to be pioneers. Instead, it is our concise solutions to core questions that we pride ourselves on. We consolidate questions into a simple easy to read email straight to your inbox. No googling or book marking required. Plus our answers come from reputable sources (not just a wiki page anyone could edit).
Why can't I just use print statements?
Today's modern applications are increasingly complex. With legacy monolith applications or more recent micro service architectures, embedding print statements like it's still 1999 simply won't cut it. With today's expectations and tight project deadlines, being able to quickly and effectively troubleshoot your code when it matters most can make the difference between a project's success and failure.
Can these techniques only be used locally?
No. We provide 2 sets of debugging techniques. 1. Techniques for debugging code locally 2. Techniques for debugging code in a production grade environment
Can’t I find most of these answers on Google?
You may find some similar problems on a blog post somewhere. What differentiates this SubStack is our consistent postings overtime. Our answers come from reputable sources. All challenges come with answers and it is our solutions that offer a competitive advantage.
What’s in it for us?
Well, the monthly membership fee enables us to create great posts and do so on a daily cadence. We are programmers too. This is created with love as a token to our appreciation to the field of Computer Science. We enjoy solving problems like most engineers. What’s more is some of us are even hiring mangers for large firms. Naturally, we’ve included algorithms that we have used during actual interviews.
When will this product be made available?
We are completing the final pieces as we speak so everything is ready to set sail on this new endeavor. We will be making major announcements soon. Sign up to stay informed.
What do I need, to get started?
A hunger to learn, an email address, a free GitHub account and a Visual Studio Code installed on your dev box. That’s it.
Do you offer discounts for students?
Not currently. Our pricing is as low as possible for the value we provide. Please feel free to drop us a message on the contact page if you are a student and would like to see this in the future.
What language are the algorithms written in?
Why is SRE next level?
Simply put, it's where software engineering meets infrastructure. More so now than ever is it imperative to consider not only code but where that code will live.
This is the space where worlds collide and for good reason, both are essential for 2022 enterprise grade applications. SRE teams are responsible for system availability, latency, performance, efficiency, change management, monitoring, emergency response, and capacity planning. Our course challenges developers in all the areas mentioned above.
Who is our targeted audience?
Honestly, whether you're first starting out or are a seasoned developer, our flagship is designed for developers. When software developers first start out, the last thing on their mind is learning how to debug. Devs want to learn how to code, not how to debug. Unfortunately, as a result, debugging is typically an after thought. We truly hope you find our recipes informative, easy to follow and most importantly applicable to whatever development environment you may be up against.
Who is our targeted audience?
Chances are you will be given 'happy path' examples. Sure that isn't a problem when you are first starting out, however, it is simply unrealistic to expect your code to work as expected every time.
Reduce time spent troubleshooting production issues