Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Dear me,
We have noticed you uploaded files to a public github with your API keys in plaintext.
Please proceed to bang head against desk until you have learned your lesson.
Sincerely me.16 -
More than half of all support calls and tickets we get are so fucking easily searchable through our own fucking website and search engines, it's really fucking annoying sometimes.
"how do I redirect a site?"
Type the fucking word redirect into our helpdesk page.
"how can i reset my email password?"
Literally fucking type the word EMAIL into fucking search bar?!
"hey the article said to go to yourdomain.com/webmail, I'm not getting anything!!!"
"what domain did you use?"
"yourdomain.com of course!"
😥🔫
"how can I add a domain to my hosting?"
Search for the FUCKING word DOMAIN on our online helpdesk.
IT'S REALLY NOT THAT HARD, PLEASE APPLY COMMON SENSE AND USE YOUR FUCKING BRAIN.17 -
Fear of fucking failure and this thing called an inferiority complex.
I've had these two since highschool. I thought/was hoping the bullying would stop when I entered highschool but it only got worse.
All this lead to the fair of failure and inferiority complex I still notice and have to deal with every day.
The thing is that I know that I'm good at what I do and when I get a compliment I of course really like that but I forget about it rather quickly.
But I'm terribly afraid of failing/fucking something up badly and always that fucking feeling like you're inferior to every-fucking-one.
One might think that just telling me that I'm not inferior to anyone (and the other way around) helps, and I do appreciate it when people tell me that, but one person saying that once or twice is not going to overshadow the years and years and years of hearing the opposite.
Yes, that still eats me alive now and then and overcoming that with/in my work is still a huge-ass challenge.13 -
Convincing my parents that I'm doing something useful on my computer and that it can also help me get a job5
-
My biggest personal challenge as a dev? The one friend that keeps yelling at me to learn vim when I'm doing just fine with VSCode.11
-
Getting older. I've been needlessly worried about my age as a developer since I was 23, which is hilarious.
People always need good devs. You don't have to become a manager or commit suicide at 30. Just be awesome and someone will pay you.5 -
My biggest personal challenges as a dev are these two:
1. I tend to work too much (by choice), which impacts my personal spare time heavily.
2. I tend to not let loose of a problem until it is solved. This often results in longer work hours or me not taking brakes...4 -
Playing cool with people who
- Do the same mistakes repeatedly
- Do not think through use cases and blabber out the first thing that comes to their heads
- Are always downplaying the effort others put into their work
- Do not know when to have a discussion
- Do not take responsibility for their mess
- Are rude to newbies who are trying their best
- Are mean to the minimum wage workers1 -
Fight against procrastination.
//now I can cross "make your first rant" item on my todo list from 2016.6 -
Staying nice.
I care about the product we're creating. More than I care about the feelings of my coworkers... and that's not always a strategically sound plan.
Getting annoyed with someone rarely helps make them see things your way — even when you're objectively right, and they're absolutely to blame for all that is wrong.4 -
I was told that I am too sensitive and afterwards a liability because I couldn’t concentrate in a working space where interns were constantly screaming, running around, hitting and farting each other, throwing shit around and playing games (instead of working)...
I was told by the HR person that “boys will be boys”...9 -
When the email address is the primary key and the customer "doesn't have an email address"
Like, they're free and it's 2018... Why not?13 -
Just bought a bmi scale, confirmed what I already know: I am just a lazy piece of shit.
Get fit and be healthy.6 -
I'm a backend engineer, but since I pioneered the entire project, I had to work on frontend. And so I died on Mar 2 2018 because of Webpack and Vue16
-
How do I don’t over complicate things?
Background: I’m currently working for a game with some base project. It alr has pretty complicated ai and some other system.
Today, I was asked by boss to help him set up a test environment for testing taking damage of a character.
First I tried to read up how the battle system and ai works in the base project. Figured, it’s overkill for this testing purpose.
Then, tried to use some plugin to automate the ai and movement. Make the enemy follow the target and stuff.
Alr spending half day, then suddenly realised all I need is just to make one script that takes damage on collision.
Why am I still a programmer? 😭6 -
My biggest enemy is what i call "development fork bomb".
My boss duplicates code on a daily basis. Instead of creating subclasses he simply creates new files by copying lines from other files. The projects class hierarchy is as flat as holland.
You can take a comment, do a project-wide search and you will find 3+ matches, an ugly hack i wrote exists 4 times in the project, and so on.
Worst of all, we spend more time on bugfixes than refactoring. With my power i could add a commit-hook to block or lessen this behaviour, but i cant. There's no program that can detect this reliably and sometimes it needs to be done.
This is a curse i'm stuck with appearently.6 -
Something I refer to as the "Lost Cause Syndrome".
Basically you start working on a project enthusiastically with the resolution to write the best possible code. But either one (or some or all) of management, client and colleagues succeed in transforming the project into a comedy (or tragedy, depending on your outlook) of errors.
Then finally, one day you decide that the project is a lost cause and stop caring about it. You end up in a "Let's get this over with and get out of here" type of mindset without making any efforts to improve the situation.3 -
There was a time when I couldn't code a line in Python. My friends were all very proficient at the language as well as different Frameworks.
I started off with a strategy where I did 10 lines of coding today, 20 next, 30 day after and it grew. I became proficient with the language and built a stock market simulator for my college project.
Learnt multiple topics from math, programming, and DevOps to deploy it as well.
Most satisfying feeling was when 300 people played it for 2 weeks' time. That was when I realised I made it. Not literally, but figuratively.2 -
Focusing. I'm part of two teams that use slack, office 365, email, jira, and Trello to communicate simultaneously. I'm expected to respond to urgent messages--so I'm in productivity-killing notification hell and it's really taking a toll. :(6
-
Dealing with other technical professionals who cannot think outside their respective boxes.
Here is an example.
A QA (who is very good at her job) said this...
Her:
“We need to get one customer who is willing to pay us a lot of money to make the features they want!”
Me:
“But you realize we are a SaaS company and that means we need lots of customers and constant growth”
Her:
“No, we need to find a customer who is willing to pay us, like a million, to make the features they want. Then we make them for that customer. Then we do that again.”
Me:
“We sell software to small businesses, none of them have a million dollars to pay us, and even if they did then why wouldn’t they build it themselves?
Her:
“Well, when I worked for my last company this is what we did...”
Me:
“So you worked for a contracting company who built software for individual companies. We are not that type of company. We are a SaaS company.”
Her:
“It’s the same thing”
Me:
~Facepalm~
As a software developer and entrepreneur it frustrates me when everyone think everything is the same.
You’ll here things like...
“All we need is to get lucky with one big hit and then we will ride that wave to success, just like Facebook or Amazon!”
Holy fucking shit balls, how stupid can you be!
FB and AZ run thousands of tests a day to see what works. They do not get “lucky”. They dark launched FB messenger with thousands of messages and then rolled it out to their internal team first, they did not get lucky!
Honestly though, I can’t blame them. Most people just want a good job that pays. They aren’t looking to challenge their assumptions.
Personally I know I will be in situations again where my pride, my assumption, my fears are realized and crushed by the market place and I do not want to live in a world of willful ignorance.
I’d rather get it right than feel good.1 -
Biggest challenge: Remember to put ';' (semicolons) in line endings after coding python for 5 years.1
-
I need to stop doing this,
"Fk I have this, this, and this due tomorrow. Well time to implement this cool new thing I found yesterday in my personal project. *2am* okay if I sleep for 4.3 hours and then..."
Why don't I just do required stuff first so I don't have to stress?!1 -
Biggest challenge as a dev was breaking away from the mindset that I was some brilliant, genius programmer and accepting that I like most people knew nothing. And that there was something I could learn from everyone, including my juniors.3
-
Picking the web development field and becoming more of a business person than a dev.
I want to develop more interesting things (like games, AI, etc) rather than corporate websites and web apps. Now, I can't even write a mobile app ffs.
I can't even work on my hobby project lately.6 -
New clients and impostor syndrome.
As a self-taught freelance web developer-designer with minimum experience and an introvert it's hard to find new clients. Also the impostor syndrome-experience (call it as you want) doesn't help at all :/8 -
Step by step here:
1. Choosing a stack
2. What to put where(folder structure)
3. Naming stuff(variables, classes etc etc)
4. Finish what I started.1 -
Beating my imposter syndrome at work. Finishing my degree so my coworkers consider me a "real programmer." Having the confidence to do both.4
-
Sometimes naming variables and classes. Because the name should be relevant, short and understandable. 😊2
-
Tried both vscode and atom. However, keep coming back to Sublime Text, now only if they provided completion as good as IntelliJ, they would beat everyone12
-
Communication.
I started coding at Engineering school (so like 4 yrs ago) and even if there were projects by group, I kinda learned it all the way by myself so I actually learned to code alone. And to resolve my issues alone.
And it costs me a job right after my internship. Was a big problem since I was almost alone (someone worked also on it but they was on multiple project at the same time so not 100% available).
That was one of my biggest fear in my career and one of my biggest challenge too in my personal development.
And so, like 8 months later, I got a job, I'm in a big team and no more problem of communication. That's something I'm very proud of. But I'm still young in my career.1 -
Any type of creativity what so ever. Whenever I have to design anything my mind kinda just goes blank.
Most of the sparetime I actually want to program is spend not programming because I'm not a very creative person.
Pic related, it's my webshite. Would like to make it nice, but I have very little in the department of creative talent 😭
3 -
Finding the right balance between well written, need-one-week, maintainable software, and fast-written, ready-in-2-hours-and-never-look-at-it-again software.
Last time it took me 20 minutes to integrate with a new API. I had a script that did everything you needed. I then spent 2 weeks on handling error responses, unexpected responses, exceptions, intelligent retries, logging, unit tests, integration tests, caching, documentation, etc. -
Actually finishing a project.
I am a person who gets a lot of ideas for projects I want to work on, then I start writing the code for them, then I reach a wall, stop and restart the cycle all over again.
Fuck my life.2 -
Hiding my secret side project that I spend 69% of my free time thinking about and 11% of my free time working on.4
-
So a team of 3 went to a hackathon. One of us didn't know how to code, the other just front end and I back end.
So we started with some ideas and choose one, starting to code it.
After we were about 80 precent into it at the end of day 2 (the event had 3 days) one of the coaches came to us, saying our idea is already a launched startup out there and we had to have a change of idea at the beginning of the third day.
Other two completed the simple front-end of the new idea about 7am and went to sleep.
And I, while was awake for 50 hours already, had to code backend of a minipay app from scratch in 10 hours.
That was HARD for a newbie like me, but in the end I did it.
We didn't win anything. But that was a really great experience for me. Plus coffee was provided infinitely there ;)4 -
Others: I can speak English, Spanish, Chinese, Russian, etc...
Me: I can speak Gujarati, Hindi, English, Javascript, Php, Python, Java, XML, Rust, ReasonML, etc...7 -
Keeping myself from getting bored af at work. I am a backend engineer doing mostly frontend. And right now it ain't even the interesting stuff. I am merely passing photoshop files to static displays.
Kill me. Every once in a while I do maintenance on Java and PHP apps, but still...bored.....more Rails or Django please -
Going through legacy or other developers code which don't have documentation or even comments. Plus the author of the code is not working in same organisation anymore to consult. We have to understand the code like deciphering any ancient language. 😥2
-
Starting. Seriously I'm closing that gap on turning 30 and I'm tired of being a wage slave so I'm teaching myself by using resources I've found online but the immense amount of knowledge I need seems unsurmountable.
I'm coming home from work and learning for at least two hours before going to bed and going back to work but it seems so far until I get to be creating stuff instead of just trying to absorb as much of the basics as fast as possible.5 -
Overengineering. Finding the right point between overdesign and no design at all. That's where fancy languages and unusual patterns being hit by real world problems, and you need to deal with all that utter mess you created being architecture astronaut. Isn't that funny how you realize that another fancy tool is fundamentally incompatible with the task you need to solve, and you realize it after a month of writing workarounds and hacks.
But on the other hand, duct tape slacking becomes a mess even quicker.
Not being able to promote projects. You may code the shit out of side project and still get zero response, absolutely no impact. That's why your side projects often becomes abandoned.
Oversleeping. You thought tomorrow was productive day, but you wake up oversleeped, your head aches, your mind is not clear and you be like "fuck that, I'm staying in bed watching memes all day". But there's job that has to be done, and that bothers you.
Writing tests. Oh, words can't describe how much I hate writing tests, any kind of. I tried testing so many times in high school, at university, even at production, but it seems like my mind is just doesn't accept it. I know that testing is fundamentally important, but my mind collapses every time I try to write a single fucking test, resulting in terrible headache. I don't know why it's like that, but it is, and I better repl the shit out of pure function than write fucking tests. -
My biggest personal challenge as a dev is learning and retaining, as well as keeping current, any particular language. I swear I really did build a career as an HTML/JS/CSS programmer. I have a resume that shows I did. But for some reason, lately, every time I open an editor I feel like I'm starting over from 22 years ago. Everything I do nowadays is copy/paste from StackOverflow, hiring another dev to help out, or cribbing code from past projects. I'd love to be able to just open Sublime and start coding like a badass like I imagine other coders do, but I just can't even get started. WTF is wrong with me?
-
Getting a job opportunity w/o a degree and only knowing what I learned as an ... obsessive ... hobby4
-
I didn't really plan to study computer science, it just kinda happened. So when a few years into school my GPA was low my mom concluded it wasn't right for me.
Thing is, I knew I was good at programming and problem solving and so did my classmates. I even helped people who the school system said were smarter than I was.
So now I am constantly doing projects and freelancing with hopes that I'll prove myself to her.
... -
I love Slack because people say all sorts of things and then forget.
So resharing the direct link to a Slack conversation is a passive aggressive way to tell them off.
The second passive aggressive thing is making an animated gif of where that conversation took place.1 -
The lack of human interaction in most dev jobs is really frustrating especially that some companies solve this deficiency with hundreds of meetings per week which is even more annoying.1
-
Not just as a dev.. but as a person who does anything - getting over the mental block which keeps stopping you from taking up actual projects or completing them without abandoning them... the struggle is real... and I'm still struggling😅1
-
Not to burn professional bridges every time I have to review a pull request, not the biggest challenge but the one I face more often.
-
Biggest one is dealing with idiots who break everything. Can’t space anything properly. Oh you needed that function? I got rid of it because it broke my code, and it was easier. Oh yes, just perfect, get rid of a core fucking function you retard that multiple parts of the code rely on. (Luckily it wasn’t pushed to the main, otherwise everything would’ve broken...)
Another one is finishing a damn project, I have like 20 by now... all in different languages that I want to learn. Time comes to work on it? Oh wait, let’s make this because it’s more fun! Just adding more projects to my graveyard. -
1) keeping my shit together until my 3 month notice period is done.
2) moving cross country.
3) starting a new job with a new tech stack which I'm not as experienced in. -
Being on time for that 10 am stand-up meeting.
Yes, all the cool kids are doing it. Yes, sometimes there is a benefit in being in the office at the same time as your colleagues. Yes, communication and backbriefing is important.
Yet why has it to happen at that early early possible time? Yes I know other places are worse demanding to be in office starting from 6 to 9. (I wonder why I don't work there. Oh wait, I don't.) Some companies even try to trick you with free breakfast in the morning. Thanks, but no thanks, I just want coffee.
Here's a crazy thought: You let me do my work on my terms when and where and I guarantee I invest the hours we agreed upon in the contract and try my very best to achieve the current goal, and maybe I'll be a happy and productive employee.
How about that? No. Ok. By the way, is this a good time asking for the possibility to work from remote? Also no? Ah okay. Didn't think so ...2 -
My biggest challenge has been moving away from an unmaintainable Java/Tomcat/Spring Security application server to a Node.js/Express application server. That handles single sign on and two factor authentication. In 2 weeks.
I'm a front end dev. I'm sure it's fine 😓6 -
I'm currently founding a startup right after graduation. As the CTO with no employees at the moment I'm like every position in the company related to dev and Ops. It's the biggest challenge I've faced as a dev so far. Though I really learn a lot and grow mature pretty fast and it is challenging in a good sense from a technical perspective, I'm facing hard personal problems like insecurity in decision making, doubting my skills since I'm definitely no senior and a mid to high effectiveness to stress.
I've mixed feelings about the pure speed and developments right now, but the good side of things is far more exciting then the bad side is frightening.
What truely pisses me off though, is the missing time to spend here on devRant. FUCK. FML.
Have a good (REST) weekend.4 -
Sometimes it's a challenge to show how much work I've accomplished to a non-techie (<- any good nicknames for such people?).
I mean yes it looks like it's pretty simple but there were like ~5000 new lines of code and 2 weeks of work put into getting this thing working perfectly, looking sexy, and moving efficiently all while making sure it protects our infra from idiots like you!2 -
Sometimes I feel people are too damn slow.
Usually I have to outpace every particular person in the sidewalk.
Some of my dev friends have the same problem too, so I guess it should have something to do with being a dev.1 -
Concentrating and understanding someone's code/ script. :|
The code is not in class form, does not have comments, and indentation is out of control. T_T1 -
The urge I always feel for proving that I'm not as selfish, arrogant and costive as I look sometimes, specially when I'm trying to explain my colleagues about the amount of stupidity I find in something they've done.2
-
My biggest challenge was trying to convince my old boss why things need to be done the way I'm saying and not the way he wants (of course, arch wise and not business wise)
After giving up, I ended up going back to collage, studying Masters in Business Administration just to know how managers think, took me two years, and now I'm in my final semester, even though I left my old job, I am now able to handle things in a better way in my current one regardless if I was arguing with general manager, or project manager, luckily clients are not allowed anywhere near me ... -
I hate doing discovery and system analyst type crap. I'm a Dev, not a technical documenter. I'm not the product owner and I shouldn't be defining requirements for the application. Why does this seem to happen a lot?1
-
Me:"<generic coworker's name> could help me with my problem."
*sees that his/hers office is in the other building at our complex*
"Naaaaaah i'll google it again and waste another 2 hours of my time." -
API changes. Customer downloads newest version of dependency, and breaks my software. Why? Because the devs making the dependency don’t phase anything out with deprecation, just poof. So then I’m up all night making a patch so I don’t have to deal with set client.
-
Myself. Two minutes of googling a problem turns into an hour of reddit/youtubing things totally unrelated. Then I need to go back to searching for the original solution.
-
the biggest challenge i've faced is to keep up the motivation and lower my frustration where a project enters the AMS phase.
It's so stressful, you stop improving your dev skills and you have to deal with shitty and boring problems everyday. -
My biggest personal challenge as a device? Staying on topic and meeting deadlines. I get too caught up adding bells and whistles because I want my work to be badass. So badass that I forget that I'm supposed to release it and not spend months working on adding features2
-
Reading the documentation instead of blindly guessing how it works until something that resembles the solution appears
-
Stress has always been my biggest problem in development. The constant imposter syndrome when I get a project from the team is something that I can't seem to get over.2
-
- Naming things in English as a non-native English speaker.
- Maintaining a good sleep schedule as a remote worker. -
Accepting a 3 year old scratched and beaten PowerBook as my "new" dev machine. Especially when my personal, 4 year old one is as powerful but with double the disk space (SSD) and RAM... Then of course the new guys just joining actually do get new out of the box devices just as we're accepting that it's just not how the company works... I guess that's the bane of doing dev in a company that does resourcing as it's main focus thereby never understanding what's needed by us developers and why it is, or rather should be, different from the rest of the company.2
-
Mentoring someone in iOS from scratch, then teaching him how to maintain 3 different apps. He is able to maintain them without me now which is testament to how well I taught him, but it was challenging. Especially since I had to simultaneously work on other tickets and live prod issues.1
-
Getting along woth my incompetent boss. I have 4 bosses and 3 of them are great, 1 of them got an email from me this morning detailing why he stresses me out and was the reason my predecessor quit.5
-
Dealing with customers
What they want is moronic, and when I provide a working alternative that solves so many existing issues and is easier for me to develop they don't fucking like it because it's different from what they're used to... -
Scope creep.
Stopping scope creep when it rears its goddamn ugly head.
I kinda want project managers to recite "The Riflemans Creed" but replace rifle with the project scope. So they realize how important sticking to that scope is.
"This is my project. There are many like it, but this one is mine. My scope is my best friend. It is my life. I must master it as I must master my life. Without me, my projects' scope is useless. Without the project scope, I am useless...." -
Realising that group projects meant the best member of the team does all the work and the rest just sit around back seat driving 😅2
-
Fighting what I call "FTS" (Fuck This Shit) syndrome.
Most of my mistakes or challenges caused to my future self can be attributed to succumbing to FTS. -
Getting my own self focused on what the fuck I'm actually trying to do.
Example: right know I should be coding...... but devRant though *sigh* -
Giving time to understand concepts to the core, rather than reading the docs, getting a surface level overview and coding.
-
Took an interview, where the interviewee was trying to spin tales around react fiber and preact. I was like sure, I just was watching React Conf 2017 yesterday, and he shut up.
-
Can't stop gaming. I mean if
I put my heart to it I can learn anything I want within a few months but just can't resist the urge to boot up Witcher 3 every night.2 -
being middleware... had to split up back end work in two parts which wasn't necessary but for 1 day it is split up and at the end 3 days delayed because of split up... controlling temper was the biggest challenge of that part.
-
Thinking through a problem with different language constructs. Even to this day, I'm more easily versed in idioms for tasks I write regularly enough than I would be if I went through the logic.1
-
Overcome the fact that even though I'm starting to be really good at what I'm doing, someone will be better at what I do, and there are always new things to learn from anything. And instead of crying on my own lack of skills, don't waste time and learn from these guys who are better1
-
My biggest challenge is moving from framework to framework or language to language.
It takes me a good day or day and a half to get used to it. I'll finally have a eureka moment and figure things out. But until then, it's quite hard and I end up questioning my competence. -
Not shouting and yelling at the client. Something along the lines of:
"The data has changed because of a mapping table chance you fucking signed off last fucking November!
And no I can't provide data that's not in the source system - which orifice exactly would you like me to get it from?!?"
#sigh# much better.... -
Trying to move on from a job that got my foot in the door but has absolutely no possibility of helping me grow anymore. It's the worst. Feeling comfortable but knowing that you're not being challenged and learning and growing. I'M TIRED OF FIXING YOUR DAMN SCANNER OR PRINTER!1
-
That I'm actually as good as my coworker tell me.
I have much to learn, no question there.
But for a long Time i didn't believe that I should be a programmer and do profesionally what makes me fun.
A lot of thanks to that goes to my two coworkers, which i'll soon leave.
(the next big personal challenge: to leave the first friends i ever made. Even though that we'll Stay in contact) -
Working in the industry for several years on dozens of projects with little to show. Between clients who can't pay, who abandon projects, who have scope creeped out of control, or are just plain slow to respond, my actual finished project output seems like 25% and somehow we're the ones who get shouldered with all the blame.
-
Fitting all of my open apps onto three monitors. I think maybe six monitors will hold them all. Ironically, staying focused is also something I struggle with. 🤦♂️😅
-
That satisfaction you get from working something out for yourself is sundered only by finding another bug further down the line.
-
Dealing with clients is probably the biggest personal challenge. I'm not much of a people person, and I find it hard to converse with friends and people I've known for years, let alone clients who are looking for answers for why things aren't working, and wanting you to explain exactly (but in simple terms) why a thing that seems simple is so complicated.
Another challenge, which is somewhat related is expressing myself. This again, stems from not being super great or comfortable in conversations, but as a dev, even among other devs, your opinion on things gets asked a lot. For someone who was used to sticking with the status quo and mostly agreeing with things, stuff like peer code reviews, or giving pointers on how to implement something is a big challenge (but I'm improving)2 -
Tying to make something of myself without working for anyone else.
It used to be easy for me, but fear kept me from perusing things all the way thru when I was younger. I never wanted to leave what were decent jobs at the time.
I finally did it. Threw away a very good job to bet on myself.
But the difference is, now I have a family and finding free time in itself isn’t that hard, but finding free time to code uninterrupted for hours... the way one needs to in order to hold a program in ones mind... yeah, near impossible these days, haha.
I have great ideas but I need help to get things to that ‘next level’ where an idea could take off and get real investments. And I need money to pay the help... Just getting the ball rolling would be nice. I used to take it for granted how easily I could get side jobs and be literally the best in town. But now it’s insanely competitive. I don’t even consider Webdesign an option for side work anymore, with sites like Wix and customers that don’t appreciate what I do vs a kid that gives them a Wordpress theme for just the cost of dirt cheap hosting... traditional Webdesign is dead.
But that’s all well and good, i saw that coming over a decade ago and focused more on coding application. I do think there’s a niche for my programming skills, so my current goal is trying to exploit that, or at least see if it’s viable. I just need something to get money to invest in my real projects.
I’d love to hear from people with similar situations! Not sure if I’ll pull it off before I have to go back to work. Although, I viewed never returning to the workforce haha. We’ll see... -
Trying to find a summer internship. It's mandatory for my degree, so I need to find someone who wants me. 😓 Suggestions?4
-
It sucks that you need to transition to other roles.
Started as front-end dev, now I have to write PL/SQL code. Which I don't like and not confident as NodeJS, Vue, React, Angular4, Java, etc. -
1)not thinking too much.
Seriously, my mind is way too stupid to sit idle and relax. In my mind, Somewhere there is a thought about an incomplete project, somewhere there is a startup idea, somewhere there is a fear of an incomplete assignment, while somewhere there is a sad song playing.. and out of nowhere, there comes my beautiful crush and me kissing, and woah, am now doing bhangra and round and rounds of shotz with her, whoops whoops whoops go back, bro , go fucking back to your work :|
(After 5 minutes...)
"whats going on devrant now?, whats goin on insta now, has she repied on whatsapp? what she eating? hey!, i could make an app for....
And this cycle goes on.... -
Delays. Delays in payment, delays in scope and spec delivery, delays from the graphics guys, delays from the X guy, the Y guy, this company, that company. No matter what the reason, delays leave that leave the Dev waiting and sitting around despondent and losing interest faster than the second to latest viral video.
-
Knowing I'm probably more experienced and a better developer than most of my peers but not able to show it in interviews to land a job that actually would use it.2
-
I was the kind of guy that hated JavaScript 3 years ago. Then my interest on React was awesome, the hard part was understand JavaScript. Now I love javascript3
-
Make a good game which can make enough money so I no longer have to make websites to survive. I want to make great adventures, games, leave a footprint after me...6
-
!wk94
Those meetings.
Those bloody meetings are nothing but time suckers. Much akin to some family event where they bring everyone together, regardless of their relevance to the agenda.
Also, the fact that we have been scheduling some important meeting always since 2 fucking months, only to be declined ALWAYS. The bloody meeting has been floating as an action item for 2 months, but none gives a fuck.
But no, we want to have meetings about meetings, and meetings about why a meeting didn't happen.
Also they ask us to stretch and accommodate, sucking time out of dev.
W H Y ?1 -
So the testing team at my company are a stickler for rules and are somehow bureaucratic as hell. Since I'm new to the project I usually have to make direct contact with them. They are short of me getting in their face and screaming like a madman.
-
Not to dislike 9 to 5 developers who have no passion for their craft and leech my hard work and knowledge while getting mad at me for not taking my time to sit with them and explain every small aspect of their tools to them that they should already know after having used them for 15+ years.
-
• being good enough to be given the "software-y" cool work
• hoping the more junior devs are just happy to be there and take on anything regarding CSS -
I think motivation and constant improvement are the biggest challenges, but I guess these are applicable to life in general. On a dev prespective one of the biggest challenges was the jump from college work to job work. The professional environment brings some responsibilities that in college you just don't have. Good side, in most cases, when you get home you don't have to think about it.
-
When the documentation suggests you use composer to install swiftmailer so I can use sendgrid.
Even though I can install composer as an extension and sendgrid is integrated within the portal it's down to me to work out the azure cli or is it a powershell cli or is it bash?
Echo gives kudu error, oh well if there's kudu why am I using composer?
Grrr azure you don't make it easy. -
Not slapping someone when they call an object a thing or worse a thingy, it's like working with basic Starbucks bitches
-
Studying information technology, working as a devops guy and in parallel paying a flat for my girlfriend and me, as well as a car and motorcycle.
Just struggling as there is not much spare time for personal projects. -
Confidence in interviews/imposter syndrome. I know need to keep practicing and just take a deep breath-I really want to get that dev job!
-
rip life. Webpack is strangling me. You'll turn degen if you came from backend...
Looks like this is my biggest challenge as a dev so far.2
Top Tags
Weekly Rant
View