About<aboutme> If anyone bothers to read and screenshot this, I'll personally build you a website for free* </aboutme> *FAKE NEWS
SkillsI'm playing with so many sneks! HEEEEEELLLLP
Joined devRant on 5/14/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Nearly 30 days into my new job. Haven't done any coding.
Just a lot of paper pushing and meeting scheduling.
I've been playing this really awesome game where you have to use code to manipulate the world around you to solve the puzzles.
It's awesome, colorful, and has been my obsession for the last couple of days.
The game is called "One Dreamer"
Summary: Manipulate the world around you by editing source code in an adventure game about a burnt out indie game developer's quest to fulfill a lifelong dream.
Honestly, even the summary doesn't do this game justice in what it's been able to give. It's so well done.
Also Steam link, if you're even remote interested. I figured the crowd here might enjoy it, even for it's novelty.
Also demo if you don't want to spend money. A little less polished than the main game, but gets the point across well.
I see now why people can despise WordPress.
2nd week of just pure learning and I gotta say that I can see that the way it was built was paved with good intentions, but it's clear people wanted more from it and things have only gotten more and more messy.
Honestly, it's fine. It's not my favorite stack, but whatevs.17
Check out this amazing project that won the 2022 Summer CodeDay challenge.
It's a different take on whack-a-mole that's multiplayer using SSH
Is a week enough time to figure out if a company is right?
I'm not sure if I like this new leadership team...
I'm starting to think that I might have been far happier with my previous gig...9
The scope for this project was absolute horse shit, and now they are mad because the end product is still horse shit...
I want to feel guilty for the outcome, but I just can't. This is something they should have had foresight for. Validation and testing is absolutely atrocious here. No official real scenario testing, and now the whole thing has been blown wide open for all the shit it can't do.
I'm not going to get any real work done today, am I...
Here I sit waiting for the next problem to pop up because of silly untested edge cases by this team.
I seriously cannot stress how important it is to build good reliable tests. Especially regression testing.
I am crying inside over the amount of time I've lost in my integration hell.
Seriously stupid shit that should have been tested but never did because I was too fucking lazy. Don't be me. Don't put yourself in the hell I'm in. Be better.1
I told these people that this issue would happen. Did they listen? Nooo
It'll be fine, they say. We likely won't be having that much data returned to the front end, they say.
Day of the install. Web Application attempts to query 68,000 rows of data straight into the web page.
*Surprised Pikachu face* when they are consistently getting crashed browser tabs.
And now everything gets pushed back and we're behind by an entire month because they didn't heed my warnings.
Oh, and now I have to pick up after them, and do some stupid work arounds that will likely be defunct in a month or two. 🙄5
Finally figured out that 500.30 error.
You won't believe it, but y'all probably will... But I solved my problem by fixing literally one line of code.
This of course pissed me off because this problem persisted for an entire week, even my supervisor could not figure it out.
But I learned so much in failing to find it and making wrong assumptions along the way.
Solving a problem is sometimes just half the battle, the journey along the way counts for something.
My supervisor was super impressed too, so that made me even more happy.
Anyways onto the next problem. 🤪6
Literally spent all day trying to figure why I'm getting a 500.30 error on my application. The damn fucker won't let me get THROUGH. I know it's possible to do because I did it with another application, but this one is being a little shit.
I feel like the very definition of insane right now because I've been doing little incremental changes but getting the same results.
I just want to rip the entire thing apart.7
I'm literally one junior developer building a front end stack for a company that uses the waterfall method of building shit...
My application has not been fully tested and none of the real user base has actually tested it. I have no clue what potential egde cases exist in my application. I did as much testing as possible but it's keeping me on edge that there is potentially something broken lurking underneath that I don't know about.
If it is broken it's all erupting into flames and there's nothing I can do about it because the application will have to go through a whole beuacratic process to allowed to be fixed.3
Got the newest update for Emojis and I was scrolling through them, and what do you know? This one popped up. All I can think of was "Devrant did it first"3
I went down a rabbit hole of code changes to try and delete a stupid for loop with a break in it.
It was super stupid and I gave up and submitted to the fact that some battles are not worth the time and stress.
OK... But seriously, It was returning multiple entities from the database, but we only always want the first one. My logic is that we should just go in there and fix the LINQ so we are explicitly getting one entity out.
But fuck that logic. No I'll have to change fucking everything that's tied to that method and expects a list from it. Every fucking thing. That includes error handling, parsing, for loops..... Nevermind...
You can have your foreach and your break. I'm taking mine, now.1
I'm going to talk to my supervisor about redoing their code base.
It will take time, it will suck a bit but I think the long term investment in doing this right will be worth it.
Wish me luck in convincing him 😂🤞7
"And in a stunning turn of events, he got it to work!"
But seriously... I've literally been throwing shit at a wall and seeing what would stick.
Fucking DTOs and getting shit out of a database. I need better resources on how to do this properly!
Anyways, I found that just using 'object' and letting the compiler deal with the rest of the bullshit actually allowed my code to work and run. I'm still a little in shock.
I'm over here trying to keep things in a nice one-to-one because that's what my PM recommended... and instead I just get slammed by Type casting nonsense and more errors than I can begin to understand. And unfortunately, Stackoverflow is of no help because everyone's issues are very nuanced and unrelated to my problem... Maybe I'm the problem? 🤷
But here it is working without all that bullshit. I don't know man... This code base is not the rager I was expecting. I'm getting my ass kicked with code that doesn't fall in line with the book I'm learning from.
You know how they say, "forget everything you've read and learned"? I'm feeling that really hard right now.
Constantly fighting the urge to rip everything down and do it based on what my book is recommending, but then the logical natured side of me is like "you ain't got that kind of time to be unfucking someone's work, only to get caught in more trouble. Your ego is not worth it"
Anyways, it's fucking late here and I'm glad enough to not have to think about this issue anymore. Bye.3
Ughhhhhh. This fucking code is a disaster! The guy says he built it DRY, but it's WET as fuck! So much fucking repeated code!
I'm annoyed most because I know that it'd be a fucking waste of time to try and rebuild what these guys have built over the past 5 years, but goddamn it, it shouldn't be an excuse to keep on making code like this!
I know that I'm not super experienced in C# but pick up a goddamn book on good coding practices. This thing is a disjointed mess and it never had to get this way.
So many fucking interfaces!!!! AAAAAAAAAAAAAAA19
No rant today. I'm actually really happy where I am. There are things that can be improved from a stack perspective, but I'm happy to have a good supervisor who's supportive of my training.2