throw laugh;

After you make your 1st PR,
Gsoc is not far away! 😂

Go to the office, start the computer, get some coffee, open up Eclipse...

Java.lang.NullPointerException

Fuck this shit.

So, I work in a game development studio, right?
We're trying to launch the title on as many platforms as reasonable, because as a social VR app we're kinda rowing upstream.
So far, Steam and Oculus have been fairly reasonable, if oddly broken and inconsistent.
Enter store 3.
Basically no in-game transaction support (our asking prompted them to *start* developing it. No, it's not very complete). No patch-update system (You want an update? Gotta download the whole fsckin' thing!). No beta-testing functionality for most of their stuff ("Just write the code like the example, it will work, trust us!"). No tools besides the buggy SDK (Wanna upload that new build? Say hello to this page in your web browser!).
So, in other words: Fun.

We've been trying to get actively launched for two months now. Keep in mind that the build has been up on Steam and Oculus for over a year and half a year (respectively), so the actual binary functionality is, presumably fine.

The best feedback we get back tends to be "Well, when we click the Launch button it crashes, so fail."
Meanwhile we're going back and forth, dealing with other-side-of-the-world timezone lag, trying to figure out what is so different from their machines as ours. Eventually we get them to start sending logs (and no, Windows Event logs are not sufficient for GAMES, where did you even get that idea????) except the logs indicate that the program is getting killed so terribly that the engine's built-in crash handler can't even kick in to generate memory dumps or even know it died.

All this boils down to today, where I get a screenshot of their latest attempt.

I just can't even right now.

"damn bro, you made that? how can i get into coding?"

shut the fuck up. you can get into programming like anyone who wants to can. by googling how to code. it's not the question itself that bothers me, it's the fact that if you actually wanted to code so bad, you already would've googled it. stop projecting your lack of passion on me.

this is most common with programming, but it happens so often with so many other things.

if you want to learn about biology and chemistry, there's free courses online and papers from nih.

if you want to learn about forsenics read a book about it and read about cases and how they were solved.

i could go on and on. the internet gives you access to so much that if you actually wanted to learn something, you would've already have.

One crucial lesson I learned while diving into programming:

Use various learning resources. Everyone explains things a little different.

You can understand stuff much easier.

Just stumbled upon this question and it says the output is:

TRUE
FALSE

… but why? 😱

Things nobody told you when starting to learn a new programming language:

Congratulations! You became a collector. From now on you will collect websites, books and a ton of related software.

I work in the Android team in a company whose main product is a consumer facing mobile application. The backend developers around me are always looking to cut corners and do things the fastest and easiest way possible. If they think there might be a dependency to another team they go to extra lengths to avoid it just to save themselves the efforts of communicating and learning things that are beyond their scope of interest. I have to put up such a fight to ensure things are done the right way. Contracts are as optimised as possible.

I once had to fight for half an hour to ensure they processed the response before sending it over to app and left the processing to the end users mobile app. They just wanted to query their database, serialise it and send it over.

For my current project, I have proposed a solution which will not require any app side changes in the near future ever, if we make things generic enough and follow a set contract. The app architects loved this solution, but it was an entire task to convince the backend team. When they finally agreed, they keep hinting at how we should've just done things the easier way to solve just for our current use case because doing it this way is taking time.

Mind you, they are the ones who had set the deadlines anyway. And now they use the excuse of these very same deadlines to try and push out a very sub par solution.

My iOS counterpart is no less. We were given two sprints to finish this task. And he kept fighting me every step of the way to make things the easier way. I feel singled out and I feel like I'm being too pushy and uptight and if things are delayed it'll be my fault and not the because these people are lazy and incompetent.

Our manager doesn't care either. He just wants the feature out as soon as possible. He wouldn't care about the nitty gritties of the solution if it was delivered on time.

Not sure if reading tech blogs in bed while falling half asleep is a sign of brilliance or insanity.

Help is needed on observability tools to use.

I’m in the trenches trying to sort out tools for observability.

Did a bit of Googling and ran into Metoro and Groundcover. Both seem pretty slick, but I’m not sure which one to roll with.

Do any of you have experience with these? How do they hold up in real-world scenarios? Would love to hear any war stories or insights.

I've been looking for Grafana as well, but it doesn't fit my budget at all.