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
-
I'm tired of working for small companies.
I'm always either the sole developer, or the only dev for a specific stack, and therefore don't have anyone to ask for help. If I can't figure something out, it just doesn't get done.
It also means I don't have anyone to bounce ideas off, do code reviews with, or even friggin' have someone who understands what I do.
It sucks.
It would be nice to have someone I could actually ask for help! As it stands, I tear my hair out in frustration until I'm desperate enough to beg for help on discord or SO. whereupon, of course, I get ignored, as per usu. asdjfklasdjf
It really sucks.
It also means that I'm often surrounded entirely by sales people and managers... you know, those super-talkative people? who basically get paid just to talk? and are absolutely computer illiterate? Yeah. Think someone who says "I need my deliverables by end-of-week," "customer success representative," "turnkey solution," etc. completely seriously. (ew).
They're the people who constantly wonder why I can't push `n` features in `n/4` days, and ofc can't understand anything I say in response because of the aforementioned illiteracy. They're also the people who, almost every week, ask how long `y` is going to take, and then yell "But I need it by Friday! I just sold 50 clients on it!" (And they do this, of course, without ever asking for timelines)
It really fucking sucks.
Though I suppose larger companies would still have these problems.
but at least I could ask for help once in awhile. that would be nice.40 -
I greeted my staff this morning with the phrase
"Morning, mind if I ruin your Friday?"
They laughed, but won't be soon enough. The task we've been working on for weeks, ripping apart the codebase changing it to work a different way, fixing a tonne of bugs, making it faster and simpler to add features too. Well business has decided they want us to stop, undo it, spend a month on something "with higher ROI" and then finish it off after that.
Business are expecting this to have no impact on any of the timelines and just to be like flipping a switch. Now obviously I won't let that happen and fight back for more time, but yet another session of compromises, arguments, and yelling. YIPEEE!!!!!!11 -
What is it with clients who have never even seen a single line of code in their entire lives telling me how long they believe a certain change request should take to code.
I mean, what if I told you that your "seemingly simple enough" change needed an update to 36 class files, 9 oracle stored procedures AND several database schema changes. Also, who the fuck is going to perform a regression test to make sure I didn't break anything? Your Uncle Bob??6 -
I'm unbelievably angry. So please bear with my venting.
QA guy and I are stuck working the entire weekend. A few months ago our company decided to promote an account manager to a Product/Project management role with 0 experience and offering them 0 training. They have no experience working with devs and have been making our lives hell. I work easily 50-60hrs per week and they still budget projects according to 40hrs/week meaning they're stealing my time not to mention they're incorrectly setting the client's and company's expectations.
They now have complete control over roadmaps, client communications (this wouldn't normally be bad except that they're having technical discussions with the client with 0 tech experience), timelines, etc. and since their experience was in account management they are now working with devs but making decisions that exclusively put the client first at all costs, even if it means everyone else has to work weekends while they go on vacation!!!!
I've approached them several times to offer help on budgeting time or to propose that we do a Q4 planning so that we can improve the product instead of stay in a shitty position as we are. I'm responded with "You deal with what's in front of you. It's my job to look at the bigger picture."
They mismanaged a $500,000 project and our CEO got wind of it because the client called him while he was travelling. He in turn gave shit to our Directors who in turn chewed the QA guy and I out. "You need to be more meticulous when deploying. How could you let this happen? We're eating shit because of this. You need to work over the weekend to make up for this", etc.
I'm now directly responsible for having delivered something that wasn't up to standards even though I was already putting in the overtime.
This is honestly fucking ridiculous. How can I be blamed when I'm truly doing the best I can and putting as many hours as I can while edging toward burnout.
I love what I do but I hate feeling extremely pressured to turn down friends and family like this. Maybe I'm just too easy going and need to say no more. Who fucking knows. I know that I'm angry with the company right now.
What do you all think? If you read this rant, thank you. Feels better to write it out.12 -
Do managers not fucking understand that Jira is meant to eliminate all this stupid "What's the status with X?", and "Is Y done yet?" chatter. Our communication channels should be on business logic and other global updates about the company, not about fucking workflow status updates because you have nothing else to do with your day but ping me every 5 minutes.
LOOK AT THE REVIEW COLUMN ON JIRA. I MEAN ITS LITERALLY CALLED REVIEW. SO REVIEW IT AND DO YOUR FUCKING JOB.
I swear the devs consistently have a better overview on timelines and project status than management does - which is sad, because this is literally the definition of management!!!17 -
OK.
1. So i tindered.
2. I got a really nice girl.
3. We chatted really long and good.
4. We tried to meetup it did not work because of our schedule. New
job on my end, she is a student.
5. I thought its over. Fine whatever.
6. She gives me her number.
7. We continue chat on whatsapp
8. Blablabla 3 days long, she gets bored and tries to friendzone me
9. I revert the shit and state i wanna be serious and there wont be a
friendzone/nice guy comin from me.
10. She happy and continues to chat.
11. I get emtionally invested in her.
12. We exchange thoughts dreams and music.
13 We want to meetup at weekend. I cant. Got a family wedding all
weekend.
14. We want to meetup the second week.
I cant. Im off on a company trip. Again new job here.
15. So we say in the week after I get back.
15a. Before the weekend we need to deliver an rc and go all out to hold
the deadline.
15b. We deliver, but shit happens on the customer side. His fault but we
get the blame.
15c I go onto the company trip.
16. We chat and i send her pictures of the trip over the weekend so she
sees I care.
17. She seems fine. And happy.
18. I come back from the trip late night and need to work the next day
jetlag style.
19. I work jetlag style. And try to fix the shit from last week.
20. I come home really tired and looking forward to date day tomorrow.
21. I cant do anything. My home looks like shit and the bag still
unpacked. I just eat and fall asleep.
I feel bad bcs my home will turn her down instantly if we make it to my
place.
Need to hope that it does not come to this.
22. Date day comes. Today.
23. I wake up at 6 early to plan ahead to make sure my clothes are fine
and i arrive on time in the office to exit early.
24. I expect to check what goes on today in the city and give her the
location to meet and time.
25. I enter office and immeadetly get caught up in meeting planning, dev
questions and the meeting itself because the project is on edge.
26. We have a 5hours long meeting where people go on and on and on.
27. 3h later in the meeting:
my brain was fried and around 12 i go to lunch with some people.
28. Meanwhile the city is turning into a rainy mess of a shitty day. No
way I can have a nice walk with her like that. Bars and coffeshops are
just to boring.
29. So i eat to regain some sense and we go back to the office.
Meanwhile I am thinking all kinds of locations and stuff in my head.
30. Havent given her any update since a good morning in the morning.
31. We reenter the meeting. Things continue like before. The project is
on impossible demands and impossible timelines. Still we try to do our
best.
32 3h later on 3pm I tell her i am in a long meeting and working on a
meetingspot.
33. shes not happy.
34. I get a call from a relative
35. i need to go out and take the call. not good for the collegues.
again new job here.
36. family trouble, money trouble, goverment demands. I promise to
handle that tomorrow. Before work.
37. i get back into the meeting.
38. still super slow and no results.
39. need to focus but start to check for locations on my phone.
40. she asks me where i am
41. I send her my location.
42. she thinks i am saying she should pick me up!
43 i joke and say no definitly not.
44. shes pissed.
45. I decide for a coffeeshop. after work. and send her the location
46. She says to call it off.
47. I go all in and go romance style. I say ill wait there even if she
does not come to show her how much i care.
U know to avoid the lets do it some other time fuckery and then it never
happens.
47. She goes quiet.
48. 2h later we finish the meeting. Meanwhile QA foudn a bug we need to
fix because why not.
49. I got 30 minutes to find the bug and fix it before I need to go to
uphold my word.
50. I find out what to do, but it might break a lot of other things
without careful test and implementation. Collegues says he takes it.
51 I feel bad but I need to go. I even leave earlier because otherwise I
would not be on time.
52. I arrive 15 minutes early. I grab two coffee2go and wait outside,
53. Shitty weather, sometimes rain, sometimes sunny, cant decide what it
wants.
54. The weather is just like how I feel.
55. I wait 1 1/2h
56. I think I should feel stupid, For gods sake its tinder. People dont
give a crap, Enough people around why should I Invest so much into this?
But I dont feel stupid. Because this is how I want it. I dont want
appointments, I dont want safety. I decided for her and I went all in.
57. I send her pics from the sceneray as proof that I waited,
58. I think I blew it. She is still quiet.
59. Friends are asking me for plans for the weekend. I wish I could say
I already have some with her.
60. I feel lost right now. But my head says I put too much stress on
her, And i fucked up with the planning. I should have been more precise.
My head also says that i am putting myself into the victim role, which
is wrong always. Should I continue to reach out to her? Is there
something I could do still?68 -
My Dream Job?
✅ 100% Remote Work.
✅ No dogshit Proprietary Stacks like Adobe Experience Manager.
✅ Reasonable Timelines.
✅ Management defers all technical decisions to you.
✅ Actually Challenging Projects.
These are my Big 54 -
So... I've seen my dad talking a lot about quantum computers, and it's getting quite embarrassing to be there when he talks about them. He doesn't understand shit about them, except that they somehow use quantum mechanics for something.
Last week my uncle from Spain visited us. He's a Cristian pastor, and a cool guy, so they always talk about god and similar themes. We gathered the family to have a dinner with my uncle as he only was going to be one day with us. This is how part of the dinner went by:
" so, <Uncle's name>, have you heard about quantum computers?"
me thinking:*Oh my God. Please not again... *
"The nasa, the US government and all kinds of powerful entities are getting the quantum computer."
He always talks about THE quantum computer as if it was just one big machine.
"They have found that multiple universes exist through it. If this is what they are telling us, imagine how far they've gone. Remember that technology is always 8 years ahead of actual public technology."
Me:*please dad, stop. Who the fuck is made that claim and how many fucking years ago?*
"Did you know that many people remember that Mandela died in prison, while in the oficial version, he died after it? They must be messing with multiple universes, or multiple timelines are getting intertwined."
Me: *please, not the mandela effect again*
Then my dad procceded to talk about multiverses and how THE quantum computer was the future and about some parts of the Bible that supported it. Bizarre, I know.
When we are alone, I always try to tell him how things actually work but he always twists my claims to support his. Last time I told him that the mandela effect was perfectly explainable by psychological phenomena around forgotten memories. But this is going to far... Fuck the guys that made zeitgeist. Fuck Alex Jones. Fuck random youtube conspiracy channels. They make technology look like fucking magic for muggles.10 -
I'm a lead Dev on an agile team. We were just handed a fixed scope, fixed date project. On Monday, instead of helping push this out, I get to have a meeting to explain how throwing more bodies at it will slow us down.
"No! We are not code monkeys! Knowing JS and Java isn't the same as knowing our application. Stop fantasizing that it's a simple manpower issue and leave us alone so we can work these fucking nightmare timelines in peace!!"
I'm looking for a better way than that to explain it to the Sr management for the business so I don't get fired.16 -
*phone dings*
Manager: Please share the timelines for feature X
Me: *swiping away the Teams notification* Please get a life and stop texting your engineers at 9 PM5 -
After refusing to work over 40 hours a week and refusing to work last Sunday, today I was fired. It's been the 2nd time in my life and it's been the same deal: totally unrealistic timelines and totally unrealistic work expectations.
No big loss. Fuck that place.7 -
This is literally me! I'm handling multiple projects with overlapping timelines. Pressure comes from all directions!
4 -
Another shithole agency reached out to me out of the blue 4 weeks after my application.
The senior bro sends me an assignment with 30 requirements to build an app with multiple screens. Ofcourse no design provided and no API provided. Timeline 2 weeks.
Tried ask to expedite the process and reason with him because now Im in other processes where Im expecting an offer next week so I can send him a link to a very similar project I did, he can review and if he wants to I can jump on a technical call and I can answer all questions. Guy ignored the proposal entirely and wants to stick with his stupid timelines and stupid requirements which he wrote probably down while taking a shit with zero research.
Best part is there was no introduction, no discussions about hourly rate or expectations, nothing.
Disorganized shithole. Told them to get their shit together and withdrew my application.3 -
So like... did every social media app meet up and go
"yo!
Ordering notifications and timelines chronologically in a way that makes sense?
Yeah mate, fuck it!"?2 -
dev, ~boring
This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.
I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:
1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by
I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.
At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:
"Hierarchy and structure should arise from an understanding of a problem domain"
As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.
In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.
Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).
I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:
1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth
Given that, I can devise a heuristic, organic framework for growing a team:
- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it
Last thing isn't derived from the train of thought, just things I feel are true:
- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy
/rant2 -
I'm praying for our newly hired Software Architect. Because He sets unrealistic timelines. He said that He will code, but yeah He just said it. Also, praying for our project. Coz it's really doomed!8
-
This is long rant/story:
My manager conducts sync-up meetings regularly. The idea is to sync up all developers on current state of work. He does’t conduct stand-ups. He doesn't have time for it. He rather discusses on individual basis if we are blocked. The rule of the sync-up meeting is NOT to discuss any blockers or problems but simply explain each other what we are doing and how we plan next.
Sometime ago, the manager brought up and explained a new way of working in the sync-up meeting. At this point, a new developer in the team was absent due to sickness.
Today, there was a sync-up meeting and the manager started to question the new member about the newly introduced way of working. He was unaware of it and the manager never communicated this important information via email or any mode of communication available.
So, the conversation goes on as follows:
"Manager": — "Why didn’t you complete your task as per the new way of working?"
"Employee": — "Well, I've no idea. Am I supposed to do? I’ve been working as usual like any other"
"Manager": — "We have a new process and you have failed to follow it, so we’re late in delivering your work"
"Employee": — "I’ve already finished my work on time. I've raised a pull-request this morning"
"Manager": — "It doesn’t matter, it is not merged to main branch and so we can’t include your work in the release"
"Employee": — "I’ve no idea about the new process"
"Manager": — "Haven’t you asked around about what happened from previous meeting"
"Employee": — "Yes, I have. I was told which tasks were handled, but nothing about a new process"
"Manager": — "Aren’t you interested to learn it?"
"Employee": — "Why won’t I be interested? I was on a sick leave and I have no clue what happened here"
"Manager": — "What’s happened is past now, let’s not focus on it"
"Employee": — <Dumbfounded>
The Employee felt ashamed in front of everyone. He did his job but it didn’t pay off.
…. After an hour … the Employee had a talk with the Manager
"Employee": — "You shouldn’t have pointed me out in front of everyone. It made me feel real bad. You should have emailed this information if its important for the team."
"Manager": — "I have no idea what you’re talking about. When did I say so? I think you’ve a bright future in the team. You should be focusing on doing better things."
Employee goes back to work. A minute later, the Manager sends a PowerPoint screenshot of the process in the group chat.
**The Process**
It's about delivering release packages based on priorities defined by client. Each release package is a set of work items or requirements. Individual developers are assigned to work items. They are expected to deliver on planned delivery timelines in order to consider a work item into a release package.1 -
Product Managers: I know what users want! They want 10 different things stuffed into 1 piece of software that does nothing well because I don't understand budgets, timelines, or scope.
Everyone else: How about we do 1 thing, and do that well.1 -
"Scientists discover the world that exists; engineers create the world that never was"
I've come to love this quote. We, the engineers, are shaping the world. We have the tools, knowhow and expertise to move mountains.
I said it before years ago and I'll say it again: all the other roles are meant to assist us, not the other way around. We don't work for managers, sales dept., bosses. They can't do shit without us. Why do we need them? To buy us toys, to sell our creations and suggest us how to shape our creations to make a better sell.
Quit slaving if you feel you are a professional. Quit bending over to sales' and mgmt nonsense timelines and demands. Hear them out, consider their concerns and give them YOUR estimates and approaches.
WE are the power of creation. THEY work for us. Not the other way around.
Does not apply to juniors. They are still learning their way around3 -
ideal sprint fallacy.
total days 10 , total hours(excluding breaks ) 8 hrs per day= 80 hrs per dev
code freeze day = day 8, testing+ fixing days : 8,9,10. release day : day 10
so ideal dev time = 7days/56 hr
meetings= - 1hr per day => 49 hrs per dev
- 1 day for planning i.e d1 . so dev time left . 6 days 42 hrs.
-----------
all good planning. now here comes the messups
1. last release took some time. so planning could not happen on d1. all devs are waiting. . devtime = 5 days 35 hrs.
2. during planning:
mgr: hey devx what's the status on task 1?
d: i integrated mock apis. if server has made the apis, i will test them .
mgr : server says the apis are done. whats your guestimate for the task completion?
d : max 1-2 hrs?
m : cool. i assign you 4 hrs for this. now what about task 2?
d : task told to me is done and working . however sub mgr mentioned that a new screen will be added. so that will take time
m : no we probably won't be taking the screen. what's your giestimate?
d : a few more testing on existing features. maybe 1-2 hrs ?
m: cool
another 4 hrs for u. what about task 3?
d : <same story>
m : cool. another 4 hrs for u. so a total of 12 hrs out of 35 hrs? you must be relaxed this sprint.
d : yeah i guess.
m cool.
-------
timelines.
d1: wasted i previous sprint
d2 : sprint planning
d3 : 3+ hrs of meetings, apis for task 1 weren't available sub manager randomly decided that yes we can add another screen but didn't discussed. updates on all 3 tasks : no change in status
d4 : same story. dev apis starts failing so testing comes to halt.
d5 : apis for task1 available . task 3 got additional improvement points from mgr out of random. some prod issue happens which takes 4+ hrs. update on tasks : some more work done on task 3, task 1 and 2 remains same.
d6 : task1 apis are different from mocks. additionally 2 apis start breaking and its come to know thatgrs did not explain the task properly. finally after another 3+ hrs of discussion , we come to some conclusions and resolutions
d7 : prod issue again comes. 4+ hrs goes into it . task 2 and 3 are discussed for new screen additiona that can easily take 2+ days to be created . we agree tot ake 1 and drop 2nd task's changes i finish task 2 new screens in 6 hrs , hoping that finally everything will be fine.
d8 : prod issue again comes, and changes are requested in task 2 and 3
day 9 build finally goes to tester
day 10 first few bugs come with approval for some tasks
day 11(day 1 of new sprint) final build with fixes is shared. new bugs (unrelated to tasks. basically new features disguised as bugs) are raised . we reject and release the build.
day 2 sprint planning
mgr : hey dev x, u had only 12 hrs of work in your plate. why did the build got delayed?
🥲🫡5 -
I work in a large organization that previously didn't have it's own development team. Therefore various business areas have built their own solutions to solve problems which mostly involve Access and Excel.
Many of these applications still exist and we are expected to resolve any issues with them and update them when necessary performing this support role while still expected to meet our (very tight) development timelines.
I can't tell you how much of a pain in the tits it is to be trying to power through a priority development only to be interrupted with an urgent instruction to fix a 17 year old Access database that's running slow.
Of course it's pissing running slow, it's 17 years old, has nearly a million records and you have multiple users accessing it across the country!! I think it's time to peacefully let it die.6 -
I really hate working on work that require constant reporting and decision making: I don't understand how people are olay with work like that. let me present 2 cases : for context we are working on a complete ui revamp of our app.
case 1 Screen A ui revamp.
task : change screen A ui as per new figma
me : evaluates, give estimates, make new screen by changing ui wherever applicable , adding logics for new screen wherever applicable , and removing old logics whichever not mentioned in figma. finishes a task in standard timelines
Engg lead : NO!! WHAT HAVE YOU DONE! WHY DIDN'T YOU ADDED THE OLD CHANGES/MENTIONED THEM TO ME! YOU ARE THE WORST DEV IN THE HISTORY OF MANKIND
case 2 : Screen B ui revamp
new eng trainee
- starts on screen
- ask doubts on how to make new ui box 1 on day 1
- ask doubts on how to make new ui box 2 on day 2
...
- ask doubt on whether to keep feature 1 form old ui on day 11
- aks the logic for showing box 3 on day 15
...
Engg Lead : UwU MY SWEET SUMMER CHILD. YOU ARE THE POWERHOUSE OF NEXT GEN. HERE TAKE THIS QUARTERLY AWARD AND THE KEY TO MY ****
wtf? i mean yeah i should ask questions if 9/10 changes are covered in the ticket and 1 festure is missed, but if you are asking for 2 changes and not putting 10 changes, why would i bother asking about the other 8? Its like asking for an apple from a farmer and then scolding him for not coming up with "5 sacks of green diced and cutted and packed in platic containers ready to be shipped" when he comes back with a single apple in hand. ASK FOR THE CORRECT THING!!2 -
For me side projects have been things I'll make to do something that others will use. Some people call it innovation, some call it side business. But that's how i look at side projects. So the points below are more to do with entrepreneurial experiences.
1. If there are more people involved, ensure that there is work for everybody (also level of commitment is tested by how much they put in). Also have as varied set of skills as possible. So that areas are well defined in terms of scope of work and areas of expertise.
2. Put in some money. Money is super glue. It will ensure that you're committed to the thing. Things change when decent amount of money is involved. You're invested, as may be others.
3. Learn something as an intention. This has nothing to do with the learnings you'll get on the way. This one seems obvious, but nevertheless needs to be said.
4. Set timelines and deadlines. Ask someone else to check on whether you're keeping on to your deadlines or not.
5. Don't go live without proper testing.
6. Make something you feel strongly about. The path will be exciting and clear.
7. Talk to people to get their feedback on everything. You may not like what's told to you. Listen dispassionately. Absorb everything. Feel miserable. But listen and think about it after sleeping over it.
8. Continuation of above point. Talk to varied set of people in terms of backgrounds. You would be surprised as to how differently people think.
9. Ask for help when stuck. Kill your ego and be vulnerable.
10. Check out what's already available. What value are you adding. And make it! -
That moment when you found out, the "digital PMs" and "digital art directors" who have NO FREAKING CLUE about the limitation of the web... promised the clients fantastical things... at ridiculous timelines... WITHOUT CONSULTING any of the devs... GARGHHHH
3 -
You’re know you’re screwed when you get pulled into a project you weren’t involved with in the beginning, and coz of tight timelines they tell you “it’s time to jump and swim now”
FML2 -
After 4 major releases of our system with truly tight timelines & 2 years away from devrant and other socials networking to avoiding distractions, I back to devrant again!
It is nice to be back again reading rants and jokes again2 -
How the fuck do Jr devs end up doing things someone specifically asks not to do.!!!!!
Fucks timelines up
So I asked my Jr Dev to leave a feature as it might not be required in this release and rather concentrate on the thing that is gonna make this release work , the “SAVE” button.
I mean how had is it to understand,
This dude goes ahead and “utilises” days on the thing that isn’t gonna be released(a dropdown) , and no, the dropdown still doesn’t work.
I understand the spirit of solving the bugs first. But what’s the point of solving it if it doesn’t fucking “save”
P.S. I’ve done this too as a Jr Dev :p7 -
First post yay!
I'm a "tech" lead for my team. The "tech" stands for technically, I can go on a whole different rant there but that's not why we're here today.
So we have a new PM on our side and a new PM on the client side. I've been working on this project longer than any of the devs and PMs have.
One of the tasks that my team does is validate and ingest data. It's pretty straightforward and it's fully automated. It takes minutes, and at most an hour, to complete this task. We get these tasks from users randomly and they don't have any schedule to it. It's FIFO basis and we just add it to our current sprint if we have bandwidth or add it to the next one if we don't. Not a big deal, no users have complained about it before, it's just business as usual. And we have a tracker of when we received it, how big it was and when it's been ingested. Super simple.
So now comes in the new client PM. He's been asking us to come up with timelines for these ingestions. My project's new PM is bending over to him and saying okay we'll come up with it, no problem. Well, there is a problem. We don't know that far in advance for when these tasks are coming in. Even if we did, now we're supposed to create timelines for a 10 min task? It literally is uploading a file and our system handles everything and I've explained that to my pm but he still is like well that's what they want. It takes less effort to do the ingestion than to make these timelines. It just means project managers bothering devs about timelines.
Idk how to deal with this. Thoughts? Any similar experiences?5 -
Do you folks have a constant "culture switching" in workplace? by switching i mean things like standup time , leaving time , lunch time etc getting changed every few days?
I feel like being part of team that is run by a dictator ever since our tech lead changed.
earlier we used to have 11 am standup, now out of blue she decided it will be on 9.30.
Its weird because most of the team can't reach office before 10am on WFO days and I personally ma having my breakfast with laptop open till 11 on WFH day.
I mean it could look bad if I was a construction worker getting paid by the hour, but am a fucking developer who can write code on his own time and only my work and timelines should matter.
same thing about leaving office. there is no official time to leave but i have to travel 2 hours so i usually leave at 5. i usually compensate this with working till 8 -8.30 on a wfh day but now sudden 1.5 hour meetings are becoming so much more common.
Another thing about leaves. earlier we could take leaves if we had some of our 22+ paid leaves remaining.
We would just need to inform to our manager and 99% of time he would instantly approve.
Now it feels like giving a request to government office. TL would not approve until the very last day. and if the leave falls in a month where other people are on leave as well, it might not get approved at all .
mind you, our team is quite decent at 5 android devs, 2 ios devs and 2 backend devs. i am an androdmid dev and i couldn't het a leave even if all 4 other devs are present on a day but an ios dev is not present, which I don't understand why?
weird cultural shift from "we have a relaxing environment and only focus on achieving targets" to "you do as we say, there are no team decision and votes"4 -
I actually like where I currently work, sure it has problems and some office politics. The work is not always exciting but what makes it good is not having someone breathing down my neck about timesheets, noone cares if the hours you work are not exactly business hours and a bunch of other stuff.
What I really like though is having a boss who backs my judgement. If I refuse to commit to timelines or work without being given the information I need he'll support me. I've had too many yes men as bosses which always ends up with the devs coping all the blame when everything goes belly up. -
Dev planning
- set timeline for feature for 2 weeks
- share timeline with everyone involved
- project manager calls and says it's taking too long
- dev adjusts timeline to 1 week
- project manager call next day asks for a new feature to be included in the 1 week timeline
What the f*** is wrong with these ppl. People don't seem to get the concept of schedules, timelines and organizing work. It's not like there is an abundance of resources (only few devs available ) with limited budget and salaries -
A remote team decided to annoy me by trying to hold me accountable to their project plan timelines while not delivering a viable API. So, I code reviewed them.
NOT ONE FUCKING TEST! They are "meeting the date" and will "fix it later".
They beat me to production though.
No wonder they argued that a complicated, fragile, expensive, multi-product flow test was absolutely required.
I returned the escalation favor. -
Tldr: intern here, I like staying in my workplace for longer than my work hours. Is it going to cause me trouble if i become a permanent employee?
Long story: So as per my previous rants i joined a startup as an android intern, company is of around 80-90 employees with many teams and standard/sad rules like 9 hr shift, 1 paid leave per month etc.
I was worried of these rules due to being a regular clg student and living very far from office, so i complained and got a little compensations like 7 hr work shift, few half days and work from home days, etc
Now the thing is : i actually have kind of started to like this work. Its been a month and i took around 12 days leave last month for papers, but marked some of them as wfh and half days, so deductions were not what i expected (although payslip is yet to come, which would have given a better explaination). But overall Pay is decent, work environment is chill ( people work in teams here, but since am the only android dev, i got no timelines, or tech leads. Just the ceo, whom i send a daily progress message), there are good refreshments available and after papers, i am pretty much free.
So I like staying here for longer hours like 8, or 8.30 hours. My family is also working, so they are usually not much worried, tho my mom starts sending messages when i leave after 7. But this friend of mine, keeps saying "its wrong, your managers are gonna call you weak and would force you to work for more hours when they notice you can come for 9 hours , etc"
So am i doing the wrong thing here?2 -
Do you guys still see the relevance of using code freezing instead of just properly managing versions, repositories and branches in a cyclical manner, given how advanced software practices and tools are supposed to be?
To give some context, the company I work for uses the complete trash project management practice of asking teams to work on a sprint basis, but there is still a quarterly milestone and code freeze to commit to and it's where shit hits the fan.
Development teams rush features at the end of the quarter because they had to commit at the very least to a 6 months in advance planning (lol?) and turns out, not being able to design and investigate properly a feature combined with inflexible timelines has high chances to fail. So in the end, features are half-assed and QA has barely any time to test it out thoroughly. Anyways, by the time QA raises some concerns about a few major bugs, it's already code freeze time. But it's cool, we will just include these bug fixes and some new features in the following patches. Some real good symver, mate!
Of course, it sure does not help that teams stopped using submodules because git is too hard apparently, so we are stuck with +10Gb piece of trash monolithic repository and it's hell to manage, especially when fuckfaces merges untested code on the main branches. I can't blame Devops for ragequitting if they do.
To me, it's just some management bullshit and the whole process, IMO, belongs to fucking trash along with a few project managers... but I could always be wrong given my limited insight.
Anyways, I just wanted to discuss this subject because so far I cannot see code freezing being anything else than an outdated waterfall practice to appease investors and high management on timelines.8 -
Stupid timeline, there is this company I was working for. It was sub-contracted by another company to do a government project. Government only pays after you deliver in my country. It was a complex system I must say. We were to work with my buddy on this project...now the timeline we were given were not feasible since another company had been given the same project and were not able to deliver. We had a meeting and discussed with our CEO about the project timelines. From the workload the feasible timelines were around 8months if we were to work as two devs. My CEO said that was not going to happen.. The only timelines that was allowed was not more than 3 months. So we suggest use an existing system to customize. .The meetings with the clients were to be weekly demos. So we choose to go with google docs api for the document management part. We were working around 20hrs a day to be able to achieve the target deadline..we management to complete the project within the given timeline..on the commissioning date of the project we faced a government panel and this was my worst disappointment. At the point of login we had to use Google email for business to obtain the API. Just as I was logging in the guy noticed and yelled. "Is that google account ?" and I replied yes..and he said "no need of proceeding since it will be of no use and they won't approve the system". That was my lowest moment in programming. I thought I had done the best project in my life as a programmer only for stupid man to declare my project as null. I felt like calling him son of a bitch but I knew that would have made me more angry...i just walked out. I went to the toilet and all I did was cry for the first time as I can recall.. My question was I was doing weekly demos. Why didn't they raise any questions by then so as to change the entire system??? Later after that demo we went and discussed about the issue and there was time extension. I redid the project using 'open office' but just before deploying the system I got a better job. I wasn't feeling like working on that project anymore. I want to release that project as open source. Recently after one year they haven't yet deployed the system. They are calling for my help. And I don't feel like helping after the humiliation...
-
Things I have come to expect in my future since being on DevRant: shitty timelines, both funny and cruel office pranks, PMs who have no idea what they are actually managing, clients and some coworkers not knowing what my time and work is worth, merge conflicts for reasons unknown1
-
Why TF does nodejs just eats 100mb of ram away for a simple application with ONE websocket connection ? I've tried getting some heap snaps, memory allocation timelines and used memwatch-next, but to no result AT ALL! Since the heap stay small but the rss memory grows like there is no tomorrow.
-
I'd like to work for a small software house that pays decent, understands a life/work balance (40hr/wk), has a relaxed environment, worries more about the end product than timelines, and gives you Fridays to work on pet projects and training.
-
Timelines will shift because of my incomplete code. My senior will be pissed that I took so many days and delivered a simple code with no junits with a lot of conditions missing.
I am doing nothing. I am. preparing for a switch but I am feeling anxious again. I earlier also got a feedback that I ask for the feedbacks or suggestions very late, in this case my senior kept on saying that he'll review directly. This code review was expected to have problems but now the timelines are set. Although I knew that the iterations will be there, I did not put those in the timelines, I could not voice it out in front of my manager. I suck.
I never got a positive feedback here. NEVER. Looks like 2 people I need to closely work with are always pointing out the problems and I have lost my confidence and anxiety hits me hard.3 -
Recently I've noticed that a lot of projects that I get assigned to have some ridiculous timelines/deadlines whilst other projects seem to have all the time in the world. Why can't I ever have that kind of breathing space?
-
So how do you find motivation to finish a work project which is supposed to "go long"?
So, umm, this is weird, but i have been in this situation a few times and i am not sure if i deal with them correctly.
- the company proposes a brand new feature : a feature which never existed in the product before.
- they have high level directions (both business logics and technical) on how its supposed to be build
-they set vague but comfortable timelines (20-30days) to complete it
- they align me as the main dev for frontend, some x guy for backend , some y guy for parallel frontend (ios/web) and kinda forget about us.
- the business requirements are evolved/cleared as we go on making the product, the backend keeps on providing evolving apis which get stable over time.
- the business ppl shows that yeah there is no pressure and we won't mind extending this for release as other systems will be "obviously" taking time.
- our (the folks on new feature) feature is sidelined .nd we are rarely talked about until we reach those deadlines and at that time we are questioned.
I... am not a powerful performer in these situations. adding a new feature required solving some major problems again and again , while solving smaller problems too, so as the product finally takes shape . for eg:
1. i will start fast by adding all the possible screens, their abstract code, their navigation logic, their xmls etc
2. then based on designs, i will try creating designs a bit
3. then once the apis arrive, i start adding them and modify the logic to handle those.
4. meanwhile many smaller problems come up , like when sending an image from one screen to the previous screen, the thumbnail don't show up, so i spend 5+ hours ensuring that it works precisely . or how i could make 3 api calls in async and make the upload flow better.
5. this goes on for days, until and i and other people start to realise that my project is not upto the point of completion
i keep getting distracted from the original goal of making a working poc first and then fixing the nuances2 -
Going through my lore notes. And I'm playing a game with myself, so to speak: it's called "is this metal enough?", but with a side of quasi-metaphysical arcane technobabble plus mass wallmelting and nightmarishly psychedelic confusion.
For example... why are shadow gates a thing? Well, because of the undoing of time caused a multiplicity of parallel cycles that will, inevitably, slowly collapse upon themselves through a sequence of irreducible asynchronicities. But of course!
Now, as for the metal part, that's the undoing of time. You see, the Somberlain attempted to cast the most sinful signa in order to restore the desolate mortal realm as it stood on the brink of a world-ending cataclysm, this was after a decade of brutal, reckless litechnical abuse during the civil war fought amongst the first undecimvirate...
Now, he intended to roll back time itself as a way to avoid the cataclysm and restore life to the mortal realm, but the cost was immense: time was not rolled back, but rather __forcefully__ torn apart; it was effectively shredded, shattered, and undone.
Countless lives were lost as nearly six hundred years of Being were __erased__ in an instant, the most heinous large-scale blood sacrifice in history, spanning the entirety of the lower fragment of reality. I mean is this too dark, I'm not sure. How about I clarify: he didn't just snuff out their lives, no, they CEASED TO EXIST. THEY NEVER EXISTED. GONE. UNBECOMED INTO A TRUE IMMEMORIAL. OVER FIVE CENTURIES OF EVERY CONSCIOUS MOMENT ON EARTH DEVOURED TO FUEL HIS DARK MAGIC.
That's gotta have consequences, right? Well, obviously you'll get temporal distortions after that shit, I mean duh...
But wait, I'm lost, you say the undecimvirate deified themselves but were cast down after the whole superman spinning the earth backwards thing went full bathory and erased entire centuries from the fabric of the cosmos, so they were turned into the eleven thrones to guard over the eleven circles of the night eternal... but how is that linked to natural occurrences of teleportation?
First off, because *natural* teleportation is distinct from *artificial* teleportation. Failed experiments with (and miscasts of) mass transference of living matter are one of the leading causes of death among litarchs. It is not an instant transmission, just very, very quick, moreso than a mortal mind can process, that's why the "dilate" and "delay" sigils are added, so as to make the journey seem slowed down to the perceptions of whomever is teletransported, this is meant to ensure their brains don't __melt__ from the experience.
Similar reason as to why you have to give the _approximate_ total weight to carry when inscribing the ritual circle, you *do* know that it is __highly__ recommended to use accurate weighing scales to approximate this quantity, as under or overestimating it can lead to _FATAL_ consequences... do you not?
No, *natural* occurrences of teleportation do not have these constraints for two reasons: one, because both ends of the gateway are _fixed_ in both time and space due to the logic-defying occurrence of a future event being undeniably the cause of the past it revisited. Put on this toga. They are inextricably linked through the metaphorical and *literal* corpse of infinite collapsed timelines, which generates a conduit through the first circle of the night eternal, which *is* the domain of both forgetfulness and horror immemorial.
Second, the final layer on our stratified reality, that is, the final circle before the INVIOLABLE divine veil, wraps around the night eternal, which is why we call it "the shell". Or "Crisalida" if you dig Luis Alberto. It is a realm entirely outside of time, which is why the patriarchs can grant immortality, you see. By proximity to this sacred shell of existence, the timeline-corpse-conduit that links both ends of a shadow gate is, for all intents and purposes, approaching total chronostasis, therefore making it so bypassing physical space in a few seconds doesn't give you permanent loss of the sense of self as your brain turns into liquified jelly.
I don't remember what I was getting at and I don't care.4 -
It's finally annoyed me enough, I gotta ask...
Am I the only one getting annoyed at procedurals (the shows about crimes) and their accuracy irl, at least when it comes to timelines and alibis that are deemed as 100% uneditable fact... based on metadata and system log files???
Or is this another case of me assuming other humans must realise things i see as simple, should be common, sense?
If it's the latter... ANY system can be modded, timestamps have sooooo many ways of being altered from multiple angles, a few lines of code in an apk file on a dev mode device can make your gps show as anywhere in the world...
even a basic early 2000s runescape bot creator should know the basic methodology of this... and even OS-innate output of event logs can be set up to effortlessly mod themselves to selectively delete or rewrite upon the system's command to show them.
For anyone thinking im FoS/this isnt a simple concept of reality... or simply never considered the reality of how much less work it'd be to just commit whatever crime that high intellect people plan meticulously for years, often still getting caught... including via their own, or easily hacked timestamps/lack of alibi...
Wanna blow your mind?
...
If you remove all hdds/ssds and even all RAM, any external devices of any kind, cut off all networking, then put brand new, all 0s, storage and RAM in... then only connect directly to a totally direct connection to WAN (aka the internet via ISP... and your ISP has no malware etc)...
Without browsing anything, and a totally fresh, safe, OS newly installed to 0'd new ROM... no one actively finding/targeting you...
Can you already be infected with spyware/viruses/malware/etc?
YUP!
how? Someone who knows what dev u use and concise coding and drivers in binary... they rewrite your bios to turn on basic components, no fans/lights/etc... bios has the clock, u can be asleep, see/hear nothing while bios boots up totally dark, runs a cimmand to pull all the malware to u... youd be oblivious11 -
Black Sheep Construction LLC: The Leading Construction Company in Holly Springs, NC
When it comes to choosing a reliable construction company, Black Sheep Construction LLC stands out as a trusted name in Holly Springs, NC, and the surrounding areas. Whether you’re planning a new build, undertaking a renovation, or require specialized construction services, our team is dedicated to delivering top-notch results with a focus on quality, reliability, and customer satisfaction. With years of experience and a commitment to excellence, Black Sheep Construction LLC is your ideal partner for all your construction needs.
Why Choose Black Sheep Construction LLC as Your Construction Company?
Experience You Can Trust
With years of experience in the construction industry, Black Sheep Construction LLC has built a reputation for being a reliable and skilled construction company. We’ve handled a variety of projects, ranging from residential builds to commercial developments, and have a proven track record of delivering high-quality work on time and within budget. Our team has the expertise to manage all aspects of the construction process, ensuring that your project runs smoothly from start to finish.
Comprehensive Services
As a full-service construction company, we offer a wide range of services to meet all your construction needs. Whether you’re building a custom home, renovating your existing space, or working on a commercial property, our team can handle every aspect of the project, including design, planning, and execution. We provide services that include but are not limited to:
New Construction
If you're dreaming of a brand-new home or commercial property, Black Sheep Construction LLC is here to make that dream a reality. From site preparation to the final coat of paint, we manage every detail of the construction process. Our team works closely with you to ensure that your vision is brought to life, and we make sure all safety and building codes are strictly followed.
Home Renovations and Remodeling
At Black Sheep Construction LLC, we understand that your home is a reflection of your style and needs. Whether you're renovating your kitchen, updating your bathroom, or adding a new room, our expert team ensures that your remodeling project is completed with precision and care. We focus on bringing your vision to life while improving the functionality and value of your home.
Commercial Construction
We also specialize in commercial construction services, helping businesses create spaces that are both functional and attractive. Whether you're opening a new retail location, building office spaces, or constructing a restaurant, we work with you every step of the way to ensure that your commercial property meets all your business requirements and design preferences.
Custom Projects and Additions
If you're looking for a custom-built feature or an addition to your property, Black Sheep Construction LLC can help. We design and build custom decks, patios, outdoor living spaces, home additions, and more. Our team will ensure that your project integrates seamlessly with your existing structure while adding unique elements that enhance both the function and appeal of your space.
Roofing and Exterior Services
As part of our comprehensive construction services, we also provide roofing, siding, and other exterior services. We help protect your investment with high-quality roofing materials and professional installation to ensure your property is safe, secure, and energy-efficient.
What Sets Us Apart from Other Construction Companies?
Quality Workmanship
At Black Sheep Construction LLC, we take pride in the quality of our work. Every project, no matter how large or small, is completed with the highest standards of craftsmanship. We only use premium materials and work with skilled professionals to ensure that every detail is perfect. When you choose us as your construction company, you can trust that we will deliver results that exceed your expectations.
Personalized Service
Unlike other large construction companies, Black Sheep Construction LLC offers a personalized approach to every project. We take the time to understand your specific needs, goals, and preferences, tailoring our services to meet your individual requirements. We work closely with you to ensure that your project reflects your vision and is completed to your satisfaction.
Transparent Communication
We believe that clear and open communication is essential to the success of any construction project. Our team will keep you informed every step of the way, from initial consultation to project completion. We provide detailed timelines, transparent pricing, and regular progress updates so you always know where your project stands.
1
Top Tags
Weekly Rant
View