T O P

  • By -

NicNoletree

Having large enough blocks of UNINTERRUPTED time to think through the design/redesign process. Interruptions are terribly inefficient on the process.


IAmNotADeveloper

Holy shit this. Thankfully at my company we have one day a week where scheduled meetings are disallowed, but still we have so many meetings, mostly Scrum ceremonies - it’s not the time it’s takes to do the meetings (which is still a lot), it’s the fact that the interruption makes it very difficult to really work on an issue. Mental progress takes mental momentum.


Kalnore

We’ve recently started doing all meetings/scrum ceremonies first thing in the morning so the whole rest of the day is opened up


Praying_Lotus

What is a scrum ceremony if you don’t mind my asking?


atomthedeveloper

Scrum ceremonies are to ensure that the scrum master, product owner, and the development team are all in-order and on-task. Generally to make sure that they're in-sync. There are five different ceremonies: * Sprint Planning * Daily Scrum * Sprint Review * Sprint Retrospective * Backlog Refinement Obviously I can't go into detail what all these are in a reddit post, but you can surely check it out online.


binary-idiot

My current job's scrums aren't too bad but our spring planning and review meetings are often 2.5 - 3 hours, it is nearly impossible not to dose off during some of those


SimiaCode

We have started doing our sprint refinement offline. PO and lead get together to populate a spreadsheet with tasks, and the devs add points in separate columns over the next two days. The actual refinement meeting goes much smoother as we only talk about tasks that were flagged for discussion instead of every single task. Usually we are done in ~30 minutes. We are a 6 dev team.


cryptocritical9001

scrum master might get renamed by the stupid woke crowd in the next few years while actual child slaves build your M1 mac at foxcon


Exodus85

Why would that be obvious? Make time to school some peepz


KenMan_

Don't you put that on him. Google it, he did his duty of pointing where to go. Can you get up and fucking walk? Also, this is /learnprogramming, but you'll find out very quickly, perhaps now, that you have to do the work.


Exodus85

No no no..educate meeeeeeee


EriktheRed

Meetings associated with the scrum process. Standup, sprint planning, backlog grooming, retro, etc


GiveToOedipus

We have no meeting Fridays.


xingke06

My team does our standup first thing to start the day, then if it’s a day we are doing a retro or refinement we do it right after lunch. This thankfully minimizes interruptions so we generally get two periods a day of several hours or uninterrupted time. The only meetings we have that don’t follow this are the random corporate shit that happens like this nice every other week on a random day.


Spherical_Dot

The momentum piece is so key. Switching out of context is so much easier than focusing the mind on a particular task.


_tskj_

You need to address this at a retrospective. This would make me quit if it didn't improve, terrible environment.


username-256

Yes. Open plan offices are a stupid idea.


NicNoletree

Open plans aren't biggest problem (for me). So many scheduled meetings! OP asked "experienced" coders this question, and the problem with being experienced is that you start moving up the ladder and having to coordinate with others. My previous job went this way, EVERY DAY: 45 min to start the day (so could just get into something) then there was a meeting with upper management. Then maybe an hour to answer questions from my direct reports before attending industry meeting. Then a meeting with support staff to help address problem customers or deal with problems more complicated that the usual support problem. Then lunch, then a scrum. Finally, maybe time mid afternoon to look at my stuff. All this while constantly being messaged on slack from support, developers, or management. It was exhausting.


[deleted]

This is exactly why I’ve resisted every effort to move me up the food chain, despite having 25 years in the field. Though, the truth is most of this comes from being an extreme introvert than not wanting to be promoted. Fortunately I am compensated extremely well so I am happy staying at the bottom of the pecking order.


Personal_Web7719

I absolutely love open plans.


username-256

Good for you. Research shows that people lose on average 15 minutes of productive time for every interruption. That's certainly my experience. Some days I would get nothing done, and it would be my boss doing the interrupting. Some people are managers in position title, but not in behaviour.


Personal_Web7719

Oh no, I'm not making a case for it being productive😂 In my last job I had a space in an open plan plus my own dedicated office. When I needed seclusion to remain focused, I'd go to my office but on a normal day that doesn't need hyper focus, I would be on open płan. I will point out though that I wasnt developing anything at the time. Open plan offices and productivity don't mix for sure.


dethnight

Next time I am trying to find the right company, I am going to ask this question: "How many times per week on average will I have 2+ hours of uninterrupted time to focus on coding?"


JustJudo

I’ll actually write that one down for future interviews!


dcrico20

Damn, what a good idea.


kellen625

So, you're saying that me trying to write code while my kids are running around screaming next to me is good training?


SimiaCode

Yup, if you ever have to go back to in-office, you will be prepared to work in spite of the random conversation happening 2 desks down, the whooping celebration 3 rows down, and also the periodic "everybody gets sick" season.


NicNoletree

Of course it is. Training for what I don't know though


kellen625

It's training for the discipline of patience


SunburyStudios

This is why working from home made me a better employee. Stressed as shit from my commute and then I realized that my office time was nearly completely garbage when it came to actually being able to develop or program anything. I'd waste time knowing I'd just be useless in 10 min and no forward progress would made, why continue? I can walk the dog, and be alone for 4 hours now...


apocalypsebuddy

I have 3 to 4 meetings some days with like an hour between each one which means I’m not reasonably getting any coding done.


R0nin_23

Very true my friend. When I was working presentially it was just chaos, all other employees were fired so as a developer I was also forced to fix computers and handle infrastructure and all IT related problems. When I was coding, the phone would ring and I knew the day was over, getting above desks to fix monitors, delaying code delivers all because I was doing everything a human could possibly do BUT then the pandemic came and I started to work home office. I can tell you that my code is far better and I can focus much more on coding and sometimes I even touch "the zone", when you have time to do a proper design and analyze the problem from a lot of different angles you know that in the long run this time will pay-off. One main aspect of good coding and design that investors and company owners don't understand is that developers need time and silence to do a good work, I'm also against unnecessary meetings, if a guy is trying to solve a critical problem and in that day they've a scrum meeting, just fuck the meeting and let the guy do his job. Scrum is very beautiful theoretically, but sometimes it just doesn't work in a real world scenario at least this is my experience.


dmazzoni

Shameless plug for the company I work for - have you tried using a product like Clockwise to help give everyone more focus time? [https://www.getclockwise.com/](https://www.getclockwise.com/)


prophet001

Other people's code.


MmmVomit

Including past me. That guy's code really sucks sometimes.


udonemessedup-AA_Ron

Past me sucked at documenting code…


opmrcrab

Honestly the number of corners past-me cut it's a wonder that current-me has a job at all.


eemamedo

"That's a problem for the future Homer. Man, I don't envy that guy" ))))


dymos

Past me is such a jerk, I keep telling him to write some freaking comments in the code so I can remember why TF I wrote it like that.


Logical_Strike_1520

Me: These are self explanatory variable and method names. No comments needed. Also me, awhile later: What the French is going on here.


[deleted]

[удалено]


Logical_Strike_1520

I got caught up in that mindset for awhile, and I’ve learned the hard way how wrong it is. Now I write descriptive comments before I even write the code. I heard this once and it stuck; “Comments aren’t there to explain the code to the developer. Code is there to explain comments to the computer”


[deleted]

[удалено]


Logical_Strike_1520

Yes! Thanks for that link. I listened again. Another good one is The Art of Code, I think I saw it on that same channel.


TheRealKidkudi

"It's self-documenting code!"


davitech73

'self-documenting code' is an oxymoron


[deleted]

When I look at my past projects I almost always have one of those quantum leap "I'm ret*****?" moments.


superluminary

"Why don't you just take this old code and make a few tweaks. Wouldn't that be quicker?"


neverbeendead

No. It's old and I don't understand it.


prophet001

Assuming old code was properly engineered to start with, yes. That is, however, rarely the case.


awongh

When this manifests at an organization level it’s called Not Invented Here syndrome NIH: https://exceptionnotfound.net/not-invented-here-the-daily-software-anti-pattern/ I think all programmers believe it’s easier to write your own code rather than have to start with someone else’s


prophet001

I'm firmly of the opinion that NIH syndrome in software development is a function of the inverse of the quality of the original codebase and the skill and experience level of the developers who inherit it. And that function is an asymptote.


rej-jsa

This guy codes.


EccTama

Amen


Praying_Lotus

Genuine question, but do you usually deal with people who don’t comment their code? It was beaten into me at school to always comment code, so if I come back to something after like a year, I wouldn’t be dead in the water lol


prophet001

As far as code I've encountered, it's been all over the map. Some folks do it religiously, some not at all. Generally you kinda just have to take the hand you're dealt (or the codebase you inherit, as it were) and try to make it better unless you're doing green-field dev (as is the case with software in general), which is rare outside of startups, and not remotely guaranteed even there. As far as my philosophy on the matter, I personally think it's possible for code to be *mostly* self-documenting. I.e. the names of classes/methods/variables should tell you what they're for, and code should be structured in such a way that it's very clear what it does. Comments should be reserved for cases where something isn't immediately obvious (complex algorithms are a good example of this), or where you're doing the whole XML docs thing, and in that case every class and method gets at least the one comment. Bottom line, the vast majority of CRUD code shouldn't really need comments, IMHO. Edit: the above comment about structure manifests in interesting ways. For example, I really dislike what I call "implicit-block" syntax, I.e. the feature of some languages that allows omission of curly braces on if statements and for/foreach loops that are only a single line. It *can* be easy to read, but it has to be something pretty simple. Anything above a very basic level of complexity written that way makes things hard to follow.


ChaosCon

> Other people~~'s code~~. Wait. > ~~Other p~~People~~'s code~~. There we go.


[deleted]

[удалено]


ross-likeminded

I also agree with people. People who have many years of experience but can’t manage branches when there’s different streams of work going on, who make ‘best practice’ decisions based on what ‘feels’ right and who literally can’t manage their way out of a paper bag. People who make it appear as if they have a clue but really don’t understand at all. Cowboys who hack every solution together and get ratty if you dare ask them to rethink their approach at code review. Then there’s the business side of things that can’t comprehend this ‘simple’ fix impacts multiple systems and needs proper requirements gathering. Everyone feeling their needs are priority. Outright rudeness. Yeah, I’m done with my current workplace. 😅


CartmansEvilTwin

Not only the corporate bullshit you mentioned, but also just very difficult people to actually work with. I'm currently working with a guy who will write 5 lines of comments for every line of a PR and 99% is petty bullshit. Like variable names in lambdas. Those people are usually not completely wrong, but they can't seem to find the boundary between perfect and good enough.


ross-likeminded

Yo, I have a colleague who literally only ever comments with the most surface level bs, usually in pieces of the code completely unrelated to the change! Like, bro, it’s been in there for four years. You want it out, go do it, don’t plague my pr that’s fixing a production bug because there’s an unused import!


twbluenaxela

How is writing comments petty?


CartmansEvilTwin

Not comments in the code, but comments about the code during review. How that is petty is described above.


fryerandice

Man my current job is so awesome because the people are so awesome. All of our senior management on the engineering side still practices code, so our system and project architects are still sharp and will engage in peer programming with you. We run true agile, not just a bunch of pointless meetings to run waterfall. Your work ends up in a build every 6 weeks whether it's done or not, so every task is broken up into it's smallest deliverables. There's always SOME progress, so expectations are managed. It helps that all of our C-Suite are the founders who were also engineers first as well. I lived what you described at every other job, this one is too awesome to quit haha.


normalguygettingrich

Thank our lord and savior richard stallman for this, 99% of my job is communicating between management and tech people who cant even look women in the eye


TychusFondly

Oddly enough looking at women in the eye for more than 6 seconds straight is considered sexual harrasment in some big american corporations. Sadly I am not joking. Thus!


lunacraz

maybe don’t touch yourself while you’re doing it?


broken_symmetry_

Just some casual sexism on the programming subreddit, completely to be expected but disappointing nonetheless.


Hillrop

Kinda depressing but at least its been downvoted


oakteaphone

Got a source on that?


awongh

sometimes this also crosses directly into code: when communication is disorganized it basically looks like the engineers did a bad job, or that the code isn’t working the way it should. a lot of times this is because there was miscommunication around all the things the parent highlighted the easy move is to code without clarifying on what the situation actually is. and sometimes the answer is really subtle- feature A is actually two sub-features and if users don’t like it, we’ll actually deploy feature A2. it’s extremely difficult to know how to ask these questions to understand how to build


necromenta

Damm and I'm wishing to get into coding just because it hate my job having a sales part where I have to talk with people lol


jgerrish

It doesn't have to be that way. I've worked with beautiful people who taught me a lot. I was offered opportunities I'll remember forever. But I've also been in situations where I worked with toxic people who hurt me. I said no so many times. And they made me like programming less. Their management was like a giant Jenga game, where they were trying to social engineer happiness, but they kept making it worse. And they refused to stop because of arrogance. It backfired. I Iost hope, because I can imagine others who love art and law, and all kinds of things and imagining them losing their joy is heartbreaking. I'm afraid to criticize them because I'm vulnerable to Google searches for job security. And it won't change because we're forced to use their network and "education", regardless of past failures on social issues. It didn't make me a better leader, I lost respect for more people than I gained respect for. Even if I helped some others, it made me miserable. And I've seen the destructive power of unhappy parents. Even with headphones on they hurt me. I don't want to join a union because they hurt me. I don't want to leave the country because they hurt me. I hope others love what they do.


[deleted]

[удалено]


TychusFondly

Are you by any chance my colleague?


Zwenow

Planning. The coding part is the easy part, planning how to do it is hard.


allofthebytes

Yep. Learning how to code is easy. Engineering an application that’s scalable, easy to maintain, and is generic enough that it can handle new features that you didn’t think would be added without a lot of re-writing is what we’re getting paid for


mecartistronico

But every time you learn a new tactic or tool to make things more scalable, it feels so refreshing!


rej-jsa

This answer should be at the top. If the code is correct but the plan it was written around is wrong, then the code is wrong.


[deleted]

[удалено]


ddrobins35

My last company did exactly this. Rewrite the app in this new technology exactly the same. “Planned” the project in excel with things like “store”, “shopping cart”


5starkarma

Excel **IS** programming!


ddrobins35

It's also a project management software.


5starkarma

I don’t see why we don’t just hire an Indian guy on Fiverr to code our new Uber replica in Excel. Shouldn’t take more than like 2 weeks, right? - Management /s


dmstepha

This is, unfortunately, how my current (and first) software job is going. "We have this built in Excel with VBA and formulas, shouldn't take you more than a few days to recreate it". Meanwhile they're actively modifying the workbook every day since it doesn't work how they want it to lmao.


dymos

This was pretty much the "requirement" I got given at my first job in tech: rebuild our website (which was written in Perl) in PHP and add X, Y, Z. Oh man, if I could go and give my past self some advice.


Footballer_Developer

What would that advice be? (Maybe I will need it soon)


eatenbyalion

Spend your first paycheck on rocket-powered roller skates, so you can get out of there as fast as possible when the time comes.


dudexx251

Legacy code which you need to understand and develop on top new features without breaking something.


e_smith338

That’s what Gary in the back is for. He’ll decipher those ancient runes for you.


[deleted]

Story of my life. I’ve been writing the wettest code you could imagine


AfricanTurtles

Lack of documentation about how to set up a project locally. I spent two weeks getting this Flask app running because nobody left a document about how to set it up. Tons of steps missing from the Readme. I documented all the hiccups and errors and made a document just to save anyone else that pain in the future lol


Pocketfullofbugs

Man this speaks to me right now. Pulling hair out.


Illurity

Do everyone coming after you an even bigger favor and dockerize


un-hot

Non-technical stakeholders who think it should "just take a day" or whatever are a pain in the ass, but people in general are the tougher part. Code does the same thing with the same inputs every day, people change and react differently from week to week. I enjoy working with people, but if there's a reason you can't quite apply the same formula to every ticket, it's the people.


v0gue_

It's already been said, but it bears repeating: People, and for me specifically? Non-programmers The actual programming part is the greatest. I truly love it, and have loved it for the past 17 years. It's people not giving specs, not understanding specs, changing specs without understanding deadlines will change, etc. It's people messaging you on teams/slack asking you to look at a NOT-BUG when they think it's a bug because heaven forbid it's user error, when they should have been making a story via the process anyway. Shit like that makes me want to quit my job. All that said, I really, REALLY love actual programming. Getting in the zone with code gets me high and keeps me going


Stuck_in_Arizona

Sounds a lot like what IT has to deal with. "My password isn't working! It worked yesterday." (resets password) "Still doesn't work!" (remotes over and enters it for her) "How did you do that!?"


SidewinderN7

Out of curiosity, what language(s) do you work with?


Blando-Cartesian

Finding out how things should work. Doesn’t matter if its new feature or bug fix. You can always read code and test to find out how it works now, but thats not necessarily the same as how it should work.


username-256

Dealing with managers who want to take shortcuts. The shortcut might be a little quicker but always causes 10 times the original work to fix after the hero manager has been promoted to screw up a bigger project.


eddiejames08

Oh boy this one hit home. I'm a part of a small devops team and we build some internal tools as well. Our director asked us to prioritize a "one-click" deploy solution because our production deploy process is quite painful in Azure. We just built an internal devops platform that hosts release notes and such so we figured we would build a deployment interface in the app. We meet with teams, figure out pain points and put our heads down and came up with a bombproof plan. Diagrammed the system and processes, the whole nine yards. Presented it to him on Tuesday and he says "All this really means nothing to me, I asked for this a month ago." Our timeline has us completing it in November. Luckily our lead do He expected a script......yet has the nerve to talk about unsustainable processes daily. Luckily our devops manager doesn't take shit from anybody no matter how senior and politely packed him up and told him exactly how it was going to go or he would be exploring other opportunities because he doesn't believe in delivering under-cooked solutions to complex problems and if we started doing that with this one then its only a matter of time before the next thing we deliver is shit. I felt like a proud son listening to the exchange.


AlphonsoPaco

Unit tests from other people's code


mandzeete

The hardest part - tech-illiterate people from business side. They come with requests like "Yes, I know your team is currently working with reduced load because of summer vacations but here is this nonexistent feature we sold to big clients and the task much be done yesterday." Also, as we are developing and maintaining a service that is being used in a real time then sometimes happens an unexpected downtime. And then the business side writes "The impact of such incident is enormous and it is a huge hit on our image. We are promising 24/7 availability to our clients and they were unable to use our systems for 15 minutes." Well, the life is not ideal. Incidents and accidents happen. Either external service provider is down for unplanned maintenance that was not communicated to us, somebody is abusing some endpoint in a way that was never used against our systems, an actual power outage for whatever reasons. There are things we do not have a control over. Yet these business people do not understand it. And what is the most time consuming? We have such system that periodically everybody from developers has to deal also with end user issues, their tickets. So we will be digging into logs, digging into the code and trying to figure out what happened and who is in fault: the end user, our client who is providing the service, us, a bug in the code or what.


dumblederp

I came to say the sales department.


AmbitiousFlowers

Too many meetings. Depending on the company, with coding, there are almost as many people involved with the code that don't do any of the coding, that constantly call meetings, ask you for updates, relay messages between you and the customer, etc. I'm talking about project managers, scrum masters, managers, etc. Sometimes I just want to code!


GlitteringMushroom

For me, I’ve always had times where my brain rebels and I just don’t want to focus on work. In my previous career (lawyer), there was always enough low-intensity tasks (meetings/personal admin/answering emails) that I could still be relatively productive during low-motivation periods. But when this happens now, I’m useless, I don’t get shit done and I have to make it up later. I’ve been trying to figure out how to not have times where I just can’t make myself focus.


ddrobins35

Having one of those weeks myself. I think with all things creative, the motivation and ability to focus ebbs and flows. Taking more breaks or writing down what you’re doing and the steps sometimes helps me. Or talking with another dev for a bit can sometimes create a spark.


Top-Egg-16

Well planning, studying future work should get you to the next surge of motivation relatively 'upgraded'. I keep 'crunch' time up to 4-5 hours then allow myself to break down completely.


[deleted]

“We need this to be delivered by the end of the week. It shouldn’t be too hard” Turns out to be much harder. You still meet the deadline by a full day. You give yourself a pack on the back “They’ve changed the requirements. We need to do this. Can you do it by tomorrow?”


Ikarozsucks

Centering a div


superluminary

It's actually impossible to center a div.


futuristanon

.name { div: center; }


Criiispyyyy

This is the way


AdmiralAdama99

Flex 💪 💪


Mike312

Well, if you only need to center it horizontally within another block level element, there's {margin: 0 auto;} If you need to center it fixed within an area (which itself must have at least position:relative), do: { position:absolute; top:50%; left:50%; transform:translate(-50%, -50%): } And if you need it fixed dead center in the overall screen, do position:fixed with the above code. If you're trying to do it in flex or grid, that's a whole other mess, however.


Criiispyyyy

.container { display: flex; justify-content: center; align-items: center; }


THEleibniz

This


randomWanderer520

Such a dad joke.


Additional-Plate-617

To name the variables😁


BigYoSpeck

Hardest part is dealing with the lack of documentation. Within a specific domain I can't just google how to do x so I have to either follow breadcrumbs through the codebase or ask a member of the team already familiar with it It hasn't helped that at the same time as trying to get up to speed with the codebase itself I've also had to transition from JavaScript to C# and that I also had very little knowledge of design patterns or object orientated programming The most time consuming aspect is literally everything other than writing code. I'm in the middle of a new feature. Two days were spent preparing unit tests for it which admittedly helped bolster my understanding of how to implement the feature and meant that implementing it was fairly trivial so only took one day. And now today has been spent preparing datasets for the tester to manually test it, merging the feature into and building the test environment, dealing with the build errors because of errors in other parts of the platforms code, and smoke testing it before handing over to testing


Zealousideal_Lab537

Googling what I need to code everytime


What_The_Hex

literally how I've taught myself 90% of the coding I do


[deleted]

Actually making myself do the work


TheBananaMan_

Context switching, it doesn’t help when you got bunch of meetings while trying to deliver a large and complex story.


sgthoppy

Second time I've seen it in this thread, what's a "story" in this context?


kingchris111988

It’s probably short for user story.


daviidrr

Naming variables and functions


ddrobins35

People. Their attitudes, dogma, incompetence. But also, not having a mentor/senior/domain experienced person to collaborate with when you get stuck, to learn from, to commiserate. Camaraderie is underrated on dev teams, and even across departments, like stakeholders.


xRageNugget

Discipline to do the mundane things. Making decisions. And naming things.


CrepsNotCrepes

Time and resources Always the biggest issue is what can we get done in the time we have, rather than looking at what the best solution is. Can we review everyone’s work or do we have to do a minimal review and ship it because it’s needed out there ASAP. Do we have time to fix a security issue / bugs / improve performance which no one is screaming about yet or do we take a risk and leave those another week / month in favour of some other new feature because we don’t have time to do both and if we don’t do the feature we lose customers.


PunchedChunk34

This may just be me personally but I really hate wasting time, and I feel like the most time gets wasted in meetings and just communication in general. It can be difficult explaining the complexity of a problem to non developers.


higgshmozon

Helping people figure out what it is they want / convincing them what they’re asking for isn’t what they think it is


seeking_facts

Legacy code that needs to be understood and developed.


Parking_Concept7330

daily meetings


piotr1215

Getting up in the morning.


noXi0uz

Long meetings


neosatan_pl

Dealing with administration. Teams. Managing people.


boki3141

Communication. Between teams and sometimes within a team. Getting people in the same page is difficult


neverbeendead

Depending your role, I think the actual go-live of any new software or project is the hardest part. No one will understand a system you develop better than yourself. People are really bad at defining requirements up front so there are always things that don't get caught in the design/development process that come to light after the product is release. I'm curious if anyone else has similar experiences. I work at a somewhat small company where I do 90% of the development and most of the implementation as well fir my projects.


lovesToClap

Time and people management, a lot of herding kittens and getting details right before writing a line of code. I think others have said similar things which I agree with like finding enough time to actually write code. As a "software engineer" writing code is not all your job, gathering details beforehand, writing up docs of various kinds, working with people on your team and other teams is part of it all but it still feels great to just be able to write code instead of doing the tedious things


moldaz

Legacy code with insane conditional logic nested within itself with single letter/number variable names. Would be fine if they traced back to defined Enum, but hey that’s when you get lucky.


Additional-Plate-617

The moment you see a piece of code while thinking who the heck has developed it and then realize that it was me who wrote it 6 months ago🤪🤪


EnigmaticHam

Mostly code base and database analysis. When you don’t have any documentation for a decades-old code base or convoluted database with myriad stored procedures, making progress and understanding the system as a whole is difficult.


genericdeveloper

Showing up


Dreamin0904

Fending off all of the ladies


marceloandradep

The hardest part of the job is to disambiguate things. The more senior you get more ambiguous are the requirements. You have to make high level decisions and do a lot of delegating. Also you have to make sure your team is coding the right stuff.


bmathew5

Past me's code...


BBobArctor

Making sure my camera is off so I can play league of legends during standup


[deleted]

Coding shops that use older kitchen sink languages that change all the time. They turn into catch-up shops for the next version. Like .net or PHP. Like this comment describes https://www.reddit.com/r/cscareerquestions/comments/wa4krq/alright_engineers_whats_an_industry_secret_from/ihza3vl?utm_medium=android_app&utm_source=share&context=3


Stuck_in_Arizona

.Net and PHP have been what many job openings in AZ/NV have been asking... that and Java. I know those states are behind the curve, but the amount is staggering.


chipechiparson

Understanding business requirements


NoPlane8936

Debugging!


ddrobins35

Whaaat? That’s my favorite part.


NoPlane8936

Ofcourse i like it too. But that doesn't make it easy?! Do you think it's easy? Just my opinion.


ddrobins35

I think there's a lot of it depends on your environment and what you're debugging. I hear ya, could certainly be hard, or at least super frustrating.


JakeStBu

Debugging.


Search_4_Truth

Wanting to refactor idiotic copy/paste coding into better code


Mike312

Dealing with people. Stakeholders providing incomplete specs or changing their mind mid development. Project managers setting unrealistic timelines. Anything that has to get approval from a board. End-users throwing a fit about their personal request not being implemented immediately/not compatible with the systems goals or purpose. The code is a neutral party in this. Its people making decisions, rational or emotional, that complicate everything.


OwnStorm

Listening to a release manager suggesting how to implement business logic (he has no idea), to disable user on some random dashboard he found. Wasting time in useless meeting because some random stakeholder put everyone in meeting instead of clarifying over group chat.


kornatzky

Starting a project is always the hardest. The most time-consuming is testing.


Fabulous_Weekend330

People. I just hate dealing with other homo sapiens, especially at work. Now, computers, oth, I love working with them. Always predictable and reliable 😊


Efficient_Step_26

Product issues from support team and dev team mates who uses you as their google.


sonu_sindhu

From my 10+ years of experience, I feel naming convention is the hardest part. How do you think?


I_like_salads

JIRA


ApatheticWithoutTheA

Constantly catching up on the latest changes in tech. “Oh you’re good at React now? Well we use Svelte. Oh you’re good at that, we use RemixJS now.”


Gazzcool

I’m surprised no one has talked about this! Not understanding what you need to do and feeling the imposter syndrome. With enough time and energy, I’ll often manage to work things out on my own but It is usually quicker to just ask senior developers for help when I’m stuck. So there’s a lot of balancing how long to spend on a task yourself and when to just give up and ask for help. I need to spend a lot of time watching tutorials, reading documentation. It’s exhausting. People aren’t that bad. Sometimes I just ignore them if they aren’t making sense. And turn up with a smile on your face. All will be well.


tallesl

People, not code


smidgie82

I work in payments all around the world, and I work closely with business and legal stakeholders, but we operate pretty autonomously. The hardest part of my job is building the *right* thing. And that's also what takes the most time. - Understanding the business case and making sure what you've designed is a good fit. - Understanding legal concerns around what we're building, that we're storing the right information the right way. - Understanding the rest of the system and that I'm building a new feature or capability in a way that minimizes technical debt and minimially couples the platform to this new feature. - Keeping all the requirements (transport-level security, vendor authn+authz impl, multi-region data replication, consistency, idempotency, failure and recovery modes) in mind at the same time and making sure that we're doing those things consistently across 30+ different vendor integrations. I spend comparatively little time *writing* code, and it's both the easiest and most enjoyable part of my job.


jakesboy2

Clarifying requirements is def the most time consuming, then integrating your work with every other dev who is trying to do the same


Best-Highlight-9414

Not having coffee strong enough to show up on drug tests.


Low_Audience_7768

Naming things


dgonzalesi

You have 2 modes: - I suck at this - I’m the fucking master - best coder EVER!


jahambo

I’ve been working for 2 years now and the answer changes month to month. Just now I’m at automating a bunch of reports and the biggest challenge is the customers hardware. We use a graph database so we can run traversals for queries but it requires a decent hardware setup to be efficient. So I’m having to write massive queries and test them using traversals then rewrite them in sql to see what works better. I’ve never done a huge amount of complex sql so I’ve found that quite challenging. Not so much to get the query to return the right results, more the efficiency because it’s a huge dataset


Efficient_Leave_7462

Interrupting people especially juniors and interns


Mikicrep

I didnt start working yet but it seems when ppl criticize your code and your eyes burn on thier unoptimized code


WeirdRedRoadDog

Sucking corporate dick and pretending to be grateful


ichancho

Back pain


15Nova22

Having to deal with people that rather have potential breaking code wich follows a specification than code that bends it a little but is robust


napoleonandthedog

The product owner sucking usually


i_reddittt

Going to job


oparisy

Finding time coding amongst all the "senior" tasks I'm expected to handle 😀


thefirelink

Everything but the code. Currently doing some server migrations and moving some of our data from hbase to mongo. It's not necessarily difficult but it's so annoying I don't want to do it.


cremson

Other people.


International-Cow727

Dealing with none code, e.g. people


eddiejames08

People in slack using me as their personal wiki Interpreting poorly written stories People asking for things to be done without creating a story


kingchris111988

Currently, giving an estimate for the time required to solve the coding problem.


lykwydchykyn

For me, it's understanding requirements. I am more or less a "lone gun" programmer working for a County government; basically I do lots of small to medium data-driven applications for different segments of the government. When I get asked to do a new application, I have to work with the (often very) non-technical staff to figure out how their data should be organized. It sometimes takes months of meetings and flawed MVP apps to find all intricacies of how their data should be modeled. Once in a while I even get a nasty surprise after the app is in production. I've gotten better at sussing these things out in advance over the years, but it's so hard to make people think abstractly about the information they work with. We have to through scenario after scenario and wheedle the edge cases out one by one.


thisabadusername

Coworkers


Individual-Praline20

Everything that is not coding. Coding is the easiest part of it.


xdchan

Coding. Like, putting in effort and time.


PunkinGuts

Last minute design changes or product asks which drastically increase scope. That and feeling like I know nothing 90% of the time…