The 'i am a total noob' feeling is real fiah like a mix tape right now. last week on a personal project i had the problem of placing a div within a div and the buttons not being clickable. i fixed it by fixing the positions of the elements. today the same thing but will a scrolling div and f*ck me right i just had to forget the solution. now i have been stuck for hours trying to figure out the right way and fooling around with no solution. learn your fundamentals.

Was recently in a motorcycle accident and haven't been cleared to go back to work yet so I'm trying to build my first Android app.

I don't know Java, XML, kotlin, Android studio, or what the fuck a Gradle is; but I figured I'd take my app idea and download Android studio then try winging everything from there.

Needless to say, I'm having a damn hard time lol. I have been watching firebase tutorials on YouTube to try and figure out how to add authentication to my app. I kinda got it working in the AVD. But my personal Google account has 2FA enabled so I can't seem to get the app to sign me out, or sign me back in. (I was able to authenticate once successfully.)

I have no idea if having 2FA enabled is even the problem. I tried turning on debugging and can't seem to figure out how to actually get the app to debug or get a debug console open.

I seriously feel like the world's biggest n00b right now. Going to go YouTube/Google how to get the debugging working. Then I'm off for a round of learning how to read a debug report!

Hahahaha... Kill me now -_-'

As a total Javascript/node.js noob my biggest take from it this week is that it's a lighter version of the backend while doing a lot of the front end heavy lifting in a programmatic style. It's not a total replacement to ASP.NET MVC or JDBC MVC, it's nowhere near as powerful. But, I could see this being a very good replacement for JSP's and simplifying the front end. I need that because the front end terrifies me more than the backend. The devil you know is sometimes easier.

Still, my first week in node.js and Javascript has been... pleasent. It's simpler and less powerful than static or dynamic typed languages but that doesn't make it bad. 🙂

I am biased though. My first language was C++ and anything is easier/better than C++ 🤣

I've been using go for two days and I'm already pissed at it. Don't get me wrong, I like the language itself, I love the simplicity, the tooling and frameworks are the problem. Like, why does everything have to be so hard?

Why do I have to spend around 4 hours in total just to configure a fucking linter?

Why does everything have to live inside the fucking GOPATH?

Why the fuck can't I put a src/ folder in my project so I don't mix code with config files, docker files, etc?

Why the hell does documentation for frameworks/libraries/tools suck so much? Looking at you Gin and Gorm.

Why can't gin-swagger just find out what routes I have?

I must be either dumb or chosen the wrong frameworks and libraries, but the "development experience" I'm having sucks. Nothing works first try and documentation is shit and vague.

I want to like the language, but I can't, at least not if it's always going to be shit like this. Does it get better? Am I just a noob? Or should I just jump ship and look for something else?

Hi fellow ranters, I humbly request your opinion on a matter.

I am a CS student in his last year of college, and currently developing a Node.js app as his final year project with a partner. The project has potential, and we've been at it for about three weeks, but the problem is that the more I code, the less I see myself doing Node in the future.

I was a total noob in CSS before starting the project, and I have learnt a ton in just 3 short weeks, but that has taken a toll on me, because I fell pretty far behind our schedule. However, for as much time and effort ad I have put in, my partner has put in a lot more (and he knows way more than me), thus increasing the gap.

My partner and I have (for the moment) different views on the amount of effort that we want to put in the project, since I see it as "slightly more than just another subject" (9-hr a week), and he sees it as a real passion project (endless hours). This could be due to the burnout of the first weeks, but I'm really not that excited about the project anymore, and I find myself thinking that I am wasting both of our time (I don't want to be dead weight), and that if I worked on a project that really made me passionate, such a compiler or a runtime environment, or a new programming language, I wouldn't mind putting in the hours that he does. Just to give more context, this whole project was his idea, and although I find it a great idea, and I know he is capable of building an amazing product, I am not sure whether I would be useful, or even if I want to be useful. Again, this could all be because of burnout.

Anyone has had such an experience?

TL;DR: I am working on a final project with a partner (it was his idea, and I found it interesting), but I think I would be happier switching to a project of my own.