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
-
Hey everyone,
First off, a Merry Christmas to everyone who celebrates, happy holidays to everyone, and happy almost-new-year!
Tim and I are very happy with the year devRant has had, and thinking back, there are a lot of 2017 highlights to recap. Here are just a few of the ones that come to mind (this list is not exhaustive and I'm definitley forgetting stuff!):
- We introduced the devRant supporter program (devRant++)! (https://devrant.com/rants/638594/...). Thank you so much to everyone who has embraced devRant++! This program has helped us significantly and it's made it possible for us to mantain our current infrustructure and not have to cut down on servers/sacrifice app performance and stability.
- We added avatar pets (https://devrant.com/rants/455860/...)
- We finally got the domain devrant.com thanks to @wiardvanrij (https://devrant.com/rants/938509/...)
- The first international devRant meetup (Dutch) with organized by @linuxxx and was a huge success (https://devrant.com/rants/937319/... + https://devrant.com/rants/935713/...)
- We reached 50,000 downloads on Android (https://devrant.com/rants/728421/...)
- We introduced notif tabs (https://devrant.com/rants/1037456/...), which make it easy to filter your in-app notifications by type
- @AlexDeLarge became the first devRant user to hit 50,000++ (https://devrant.com/rants/885432/...), and @linuxxx became the first to hit 75,000++
- We made an April Fools joke that got a lot of people mad at us and hopefully got some laughs too (https://devrant.com/rants/506740/...)
- We launched devDucks!! (https://devducks.com)
- We got rid of the drawer menu in our mobile apps and switched to a tab layout
- We added the ability to subscribe to any user's rants (https://devrant.com/rants/538170/...)
- Introduced the post type selector (https://devrant.com/rants/850978/...) (which will be used for filtering - more details below)
- Started a bug/feature tracker GitHub repo (https://github.com/devRant/devRant)
- We did our first ever live stream (https://youtube.com/watch/...)
- Added an awesome all-black theme (devRant++) (https://devrant.com/rants/850978/...)
- We created an "active discussions" screen within the app so you can easily find rants with booming discussions!
- Thanks to the suggestion of many community members, we added "scroll to bottom" functionality to rants with long comment threads to make those rants more usable
- We improved our app stability and set our personal record for uptime, and we also cut request times in half with some database cluster upgrades
- Awesome new community projects: https://devrant.com/projects (more will be added to the list soon, sorry for the delay!)
- A new landing page for web (https://devrant.com), that was the first phase of our web overhaul coming soon (see below)
Even after all of this stuff, Tim and I both know there is a ton of work to do going forward and we want to continue to make devRant as good as it can be. We rely on your feedback to make that happen and we encourage everyone to keep submitting and discussing ideas in the bug/feature tracker (https://github.com/devRant/devRant).
We only have a little bit of the roadmap right now, but here's some things 2018 will bring:
- A brand new devRant web app: we've heard the feedback loud and clear. This is our top priority right now, and we're happy to say the completely redesigned/overhauled devRant web experience is almost done and will be released in early 2018. We think everyone will really like it.
- Functionality to filter rants by type: this feature was always planned since we introduced notif types, and it will soon be implemented. The notif type filter will allow you to select the types of rants you want to see for any of the sorting methods.
- App stability and usability: we want to dedicate a little time to making sure we don't forget to fix some long-standing bugs with our iOS/Android apps. This includes UI issues, push notification problems on Android, any many other small but annoying problems. We know the stability and usability of devRant is very important to the community, so it's important for us to give it the attention it deserves.
- Improved profiles/avatars: we can't reveal a ton here yet, but we've got some pretty cool ideas that we think everyone will enjoy.
- Private messaging: we think a PM system can add a lot to the app and make it much more intuitive to reach out to people privately. However, Tim and I believe in only launching carefully developed features, so rest assured that a lot of thought will be going into the system to maximize privacy, provide settings that make it easy to turn off, and provide security features that make it very difficult for abuse to take place. We're also open to any ideas here, so just let us know what you might be thinking.
There will be many more additions, but those are just a few we have in mind right now.
We've had a great year, and we really can't thank every member of the devRant community enough. We've always gotten amazingly positive feedback from the community, and we really do appreciate it. One of the most awesome things is when some compliments the kindness of the devRant community itself, which we hear a lot. It really is such a welcoming community and we love seeing devs of all kind and geographic locations welcomed with open arms.
2018 will be an important year for devRant as we continue to grow and we will need to continue the momentum. We think the ideas we have right now and the ones that will come from community feedback going forward will allow us to make this a big year and continue to improve the devRant community.
Thanks everyone, and thanks for your amazing contributions to the devRant community!
Looking forward to 2018,
- David and Tim
48 -
Sales employee Bob wants a clickable blue button.
Bob tells product owner Karen about his unstoppable desire for clickable blue buttons.
Karen assigns points for potential and impact (how much does a blue button improve Bob's life, how many people like Bob desire blue buttons)
Karen asks the button team how hard it is to build a button. The button team compares the request to a reference button they've built before, and gives an ease score, with higher score being easier (inverse of scrum points).
These three scores are combined to give a priority score. The global buttonbacklog is sorted by priority.
Once every two weeks (a "sprint") the button team convenes, uses the ease scores to assign scrum points. Difficult tasks are broken up into smaller tasks, because there is a scrum point upper limit. They use the average of the last 5 sprints to calculate each developer's "velocity".
The sprint is filled with tasks, from the top of the global button backlog, up to the team's capacity as determined by velocity. Approximate due dates are assigned, Bob is a happy Bob.
What if boss Peter runs into the office screaming "OUR IMPORTANT CLIENT WANTS A FUCKING PINK BUTTON WHICH MAKES HEARTS APPEAR"?
Devs tell boss to shut the fuck up and talk to Karen. Karen has a carefully curated list of button building tasks sorted by priority, can sedate boss with valium so he calms the fuck down until he can make a case for the impact and potential of his pink button.
Karen might agree that Peter's pink button gets a higher priority than Bob's blue button.
But devs are nocturnal creatures, easily disturbed when approached by humans, their natural rhythms thrown out of balance.
So the sprint is "locked", and Peter's pink button appears at the top of the global backlog, from where it flows into the next sprint.
On rare occasions a sprint is broken open, for example when Karen realizes that all of the end users will commit suicide if they don't have a pink heart-spawning button.
In such an event, Peter must make Bob happy (because Bob is crying that his blue button is delayed). And Peter must make the button team of devs happy.
This usually leads to a ritual involving chocolate or even hardware gift certificates to restore balance to the dev ecosystem.23 -
Summary of the summary: Boss is an asshole. Root gets angry; boss leaves instead of picking a fight for once. This makes Root sad (and really angry).
Summary: Root has another interaction with her boss. The boss is an asshole. Root is a bitch. Root would have been so so so much more of a bitch if the boss actually fucking responded. Root is sad this didn't happen. Root might have gotten fired. That would have made Root happy. :<
-------------
Le wild blackout appears!
-- Conference call (the short-short version) --
Boss: *freaks out* Fix it! Why aren't you fixing it? You have to fix it.
Me: I'm already fixing it. 😕
Boss: You have to fix it! This is important!
Me: Then let's get off this call so I can focus on fixing it!
Boss: Okay but fix it! *begrudgingly hangs up*
-- Slack --
Me: (posting a running log of what I'm doing) This is what i discovered. this is the cause. these are the possible fixes. I picked this one because it's quick and has few consequences, though it may break ____ so it'll need followup fixes. I'll do those tomorrow. Blackout resolved!
Boss: (apparently doesn't even noticed I fixed his shitty service)
-- Next day --
Boss: I want you to work on [stupid shit] instead.
Me: But what about the followup fixes?
Boss: Top priority! because customer service!
Me: ... fine.
-- Next week (verbatim because wtf) --
Boss: Did we test that [resolution] on ______? No one thought to test this. It didnt cross anyones mind at all? Either you guys can make good decisions and document concerns or I have to be part of every decision [...]. But this is basic. SHould have been a team heads up and said if we are switching this what can it break and can we test it. [sic]
Me: Did you want me to resolve the blackout quickly and allow people to actually use our service, or spend two days checking everything that might possibly have gone wrong? I weighed the possibilities and picked the solution with the quickest implementation with the fewest consequences. You're welcome.
Me: (Quotes boss's "SHould have been a team heads up" and links my "this is what could go wrong" heads-up in Slack)
Boss: (pretends not to even notice)
Boss: (talks about customer service related crap)
What a fucking loser.
I'm so angry he didn't respond and start in on me over it. I wanted to tear him to shreds in front of everyone.
Related:
He tried adding another huge project to my plate earlier today, and I started flipping out on him for all these shitty sales features he keeps dumping on me in place of real work that i still get blamed for not finishing. The contractor stepped in before it got too heated, though, which is probably best because my reaction was pretty unprovoked. The above rant, though? Asshole doesn't read, just blames and yells when he's angry.
I really hate him.20 -
Thursday
PM: Hey why is A delayed? It should be top priority.
me: I just completed B, and C which were also top priority but got scheduled earlier, so I thought they..
PM: Agh, yes. But can you then finish A by the end of week? it would be very important!
me: No, I unfortunately don't think I'd have enough time by the end of wee..
PM: Why? This should be *the* top priority task. You should not start other tickets before A is done.
me: Exactly. But I *just* started. And. I. don't. have. enough. free. hours. left. this. week.
PM: But why?!
me: So just on Friday I have these 5 meetings here..
*shows calendar*
PM: Ok... OK! Then don't attend those before you are done. This should be more important.
me: Ugh, oh-key...are you sure?
PM: Yea, just let who invited you know that you can't attend and feel free to cc me in, I'll explain A is most important atm.
me: Ok, thanks, but that won't be necessary.
PM: What? Why?
me: You invited me to the Friday meetings.
Obviously I had to attend all 5 meetings today and A is pushed back to next week. :)10 -
In an effort to deal with the number of “top priority” tickets, management has come up with a new priority level, “urgent”, to help differentiate between tickets that are “top priority” and tickets that are actually “top priority”.
So as you can guess all tickets are now codified as “urgent”.
I’ve suggested management downgrade some tickets back to merely “top priority” as we’re clearly right back where we started with it being difficult to determine which order to do tickets in.
They’ve ignored my request as the bletherings of a clearly unenlightened peon, and have instead came up with a new priority, “mission critical” which will be reserved for the most hallowed of emerg— oh no wait everything is now “mission critical” who would have guessed?
So “Top priority” is the now lowest priority a ticket can have…Naturally.16 -
Manager: Feature C doesn’t work
Dev: We never built feature C
Manager: Nonsense, I remember feature C clearly!
Dev: It’s still in the backlog
Manager: But we had many meetings about it
Dev: Never got put on the board
Manager: Feature C is very important!
Dev: It was never assigned to anyone
Manager: What could possibly be more important than Feature C?
Dev: All the other features you placed on the board and assigned up until now
Manager: Well I need Feature C done asap! It should be top priority!
Dev: Ok then next sprint add feature C to the board and assign it to someone
*Next planning session manager leaves feature C in backlog in favour of other tickets*
*2 days later*
Manager: What is the status of feature C?
Dev: You opted to leave it in the backlog
Manager: BUT IT SHOULD BE TOP PRIORITY!
Dev: …9 -
Mon: Ticket A is now low priority, Ticket B is top priority
Tues: Ticket B is now low priority, Ticket C is top priority
Wed: Ticket C is now low priority, Ticket D is top priority
Thurs: Ticket D is now low priority, Ticket E is top priority
Manager (Fri): You haven’t completed a ticket all week! What gives??
Manager (Following Mon): Tickets A, B, C, D AND E ARE TOP PRIORITY!!!!!
Dev: …12 -
*In teams meeting with client*
Manager: Yes we can do all of that and it will be actioned very quickly. We will make all of these feature requests top priority. We will set aside everything we are currently working on in order to get this done!
Dev: ...Are you writing any of this down?
Manager: I don't need to, I always remember everything!
Dev: Just so you are aware, I'm not writing anything down. You're going to need to create a ticket with requirements spelled out for each one of these promises you're making otherwise they won't get actioned by the team.
Manager: I know that!
Dev: ...
*Later that day*
Ticket Title: Action client feature requests TOP PRIORITY!!!
Ticket Description: *empty*
Dev: ...13 -
This company!
Ugh.
Two days ago we had an hour and a half meeting on which projects to focus on, with the result being all seven are top priority. Because of course.
Last night I told my boss why an api he has me hitting always returns 401s; even gave him the line# responsible for the response (in his code). After an hour and sixteen minutes of him debugging, he finally admitted I might be right. zzz. This morning, he tells me it's on my end, and to ask someone else for their project's API code. The problem is that the server is not accepting the new application's key, since that key is not in the allowed list. That other project works just fine. Guess why? Their key has been whitelisted for months. But it's totally my code. Yeah. Bloody brilliant. 🔅
Anyway, today we're discussing "Winning with Accountability," a 100 page book that boils down to "do what you say you'll do, by when you said you'd do it, and take responsibility if you don't." But a huge part that the boss is stressing is: provide the exact date, time, and timezone of when things will be completed by. I mean That's fine for sales calls and reports and such trivial busywork. But dev projects? Not so much.
And that's been my past three days!
Friggin joy.6 -
Management had the idea to have a hackathon on saturday. Everybody should gather ideas what to do on this day, but top priority is to have fun.
In the end, management decided that we should work on tasks from our backlog.
Yeah... unpaid work on saturday... sounds like fun10 -
The way things are prioritized:
Emergency
Critical
ASAP
Do first
Top priority
Urgent
Urgent ASAP
Major urgent
Fuck sakes.. 😣12 -
Project Manager: Hey Gid, we need to start migrating project-A to the new Server.
Me: Okay, I will inform Dev-Q.
Project Manager: Please do and treat as top priority!
Me: Hey Dev-Q, we need to migrate project-A to the new Server and we need to get it done asap.
Dev-Q: But I'm currently working on some critical bug XYZ which PM wants fixed before COB.
Me: I dunno maybe you want to speak with him.
Dev-Q: I was told to...
Project Manager: Yes! we need that done right away.
Dev-Q: What about the critical...
Project Manager: No! treat this as top priority the client just called.
Dev-Q: Okay.
Me: Any update yet?
Dev-Q: Yep but it seems like the database is quite large and the migration may take a while.
Me: Okay take your time.
Dev-Q: {hours later} Pheww done! All files and database migrated successfully.
Project Manager: Good good. So the critical bug XYZ was also completed and migrated to the new server right?
Dev-Q:
6 -
Manager: We will be building a new app. THIS TIME EVERYTHING MUST BE ABSOLUTELY PERFECT, ANYTHING LESS THAN TOP QUALITY WORK WILL BE REJECTED!!
*Not even 2 days into the new project*
Manager: Ok that’s good enough, we can fix it later. Can you go quicker on the next feature? Just sacrifice a bit of quality so we get these tickets closed as fast as possible. I said we can fix it later. Getting tickets closed asap is top priority.
Dev: …3 -
I gave resignation so am on my last weeks. The top priority is suddenly an authentication service that is completely unfamiliar, proprietary, requires me to RTFM, and requires contact with a slothful vendor about details for our specific instance. Can you do it on a 10 day deadline?
“Are you sure this wouldn’t be a better fit for someone that has implemented this authentication system before? Someone with existing relationships with contacts that manage the authentication service? Maybe I should be the one transferring my understanding of the other 60k lines of code that I singlehandedly wrote? I’m starting from zero here. Maybe it would be good for the guy who isn’t leaving to do this one so that he can retain the knowledge of the authentication system for next time you need to implement it?”
They just plug their ears now because they clearly don’t trust me due to my resignation state. Just do it. Wow.11 -
Team quarterly capacity planning:
- Confluence document created with a big table (+100 rows) by product / business. Each row is something that needs to be worked on for the coming quarter.
- Row 1 could be an Epic with 15 tickets attached. Row 2 could be adding a single log to our analytics. No consistency.
- For each row, we create a separate confluence document with the "technical details". 75% of the time these remain blank. 1% of the time there is something useful, the rest its a slightly longer version of the description from the bigger document.
- Each row gets a high level estimate by the leads. 50% of the time without sufficient background info to actually do get it accurate.
- These are then copied into the teams excel spreadsheet, where it will calculate if we are over/under capacity.
- We will go backwards and forwards between confluence and excel until we are "close enough" to under capacity without being too much.
- Once done, we then need to copy them into the org/division's excel spreadsheet. This document is huge, has every team on it and massive 50pt text saying "Do not put a filter on this document".
- Jira tickets + Epics will now be created for each one, with all the data be copied over by hand, bit by bit, by product. Often missing something.
- Last week, at the end of this process for Q2 (2 weeks late), 6 of the leads were asked to attend a 30 minute meeting to discuss how to group the line items together because we had too many for the bigger excel spreadsheet.
- This morning I was told business weren't happy with one of our decisions to delay one line item. Although they were all top priority (P0), one of them was actually higher than that again (P-1?) and we need to work it back in.
... so back to step 1
- Mid way through Q2, a new document will be created for Q3. Work items that didn't make the cut will be manually copied from one to the other. 50/50 whether anything that didn't get done on time in Q2 will make its way to the Q3 doc.
- "Tech excellence" / "Tech debt" items (unit/UI tests, documentation, logging, performance, stability etc) will never be copied over. Because product doesn't understand them and assumes therefore that they are unimportant.
==================
PS: I'd like to say this was a rare event for Q2, but no. Q4 and Q1 were so bad, we were made assurances from the director of engineering that he would fix this process for Q2. This is the new and improved process (I shit you not) that has resulted in nothing tangible.7 -
Manager: *taps dev on shoulder* Hey I noticed a minor bug I think
Dev: Sigh…. So then create a ticket for it
Manager: Can’t you just fix it right now?
Dev: I can but I’m currently working on that other issue you told everyone was “top priority” at the morning status meeting. Should I switch to actioning this minor bug instead?
Manager: Don’t switch just multitask and work faster!
Dev: …8 -
Management: Feature X is your top priority. Dont work on anything else because this needs to be ready for next Monday.
Me: *works furiously*
Management: *monday* Oh yeah we dont need that now. Why are you behind on your other work?3 -
This happened via mail thread today.
Boss: we need this new brilliant feature I just made up and running asap! Top priority, it has to be done well, for my reputation is on the line!
Me: *looks at the specifics* 'kay, looks easy enough, this evening max and it will be ready. I just nees some extra info about what kind of data validations (I speak no accountant) are needed, and some other details (a total of 3 questiona).
B: Sure! Remember, it needs to be perfect, as my reputation is at stake. Call me on the phone and I'll give you the details!
M: Can't you answer via mail? Thua way both me and the other devs will have clewr guidelines
B: Just call me! Why do you need it to be written down? It's faster this way!
...Fine. I'll keep asking until you're ready to give me a written answer to my questions. No way I'll take security details via phone for something you want in production this evening. No chance in Hell I'll take responsibility for "misunderstanding" what you said on the phone. Why does it always has to be like that?8 -
Rawrrrr
People need to understand that prioritisation is not saying everything is top priority. That means they're all the *same* priority and therefore none are a priority! Gah5 -
I never understood the appeal of Steve Jobs to other people, and had never bought an Apple product until about six years ago.
However, after buying a couple of Macbooks - including ones, circa 2012/2013, on eBay - it's very obvious that the quality has shrivelled into oblivion after his passing.
If I was to credit him with one thing, Jobs was the ultimate QA guru with long lasting products as his top priority.
Now, Apple sells glue machines and Steve Jobs would be clean slating the entire list of employees - from the top, down - if he was alive to notice how little the company seemed to care about what he had planted as the seed, many years ago.23 -
So, you are in middle of something urgent and top priority? In the meeting just displaying the business plan for 1000 people? Fixing a bug that needs the release in 30min or otherwise small babies will start to burn?
Update. Why not? It's like driving down the motorway, someone stops you and tells you that they're going to remove your steering wheel now. For no reason.
9 -
(Warning: kinda long && somewhat of a political rant)
Every time I tell someone I work with AI, the first thing to come out of their mouth is "oh but AI is going to take over the world!"
No.
It was only somewhat recently that it started being able to recognize what was in a picture from over 3 million images, and that too it's not that great at. Honestly people always say "AI is just if-else" ironically, but it isn't really that far from the truth, we just multiply an input by weights and check the output.
It isn't some magical sauce, it's not being born and then exploring a problem, it's just glorified-probability prediction. Even in "unsupervised" learning, the domain set is provided; in "reinforcement learning" which has gotten super popular lately we just have the computer decide which policy is optimal and apply that to an environment. It's a glorified decision tree (and technically tree models like XGBoost outperform neural networks and deep learning on a large number of problems) and it isn't going to "decide" to take over the planet.
Honestly all of this is just born out of Elon Musk fans who take his word as truth and have been led to believe that AI is going to take over the world. There are a billion reasons why it can't! And to top it off this takes away a lot of public attention from VERY concerning ethical issues with AI.
Am I the only one who saw Google Duplex being unveiled and immediately thought "fraud"? Forget phone scammers, if you trained duplex on the mannerisms of, for example, a famous politician's voice, you could impersonate them in an audio clip (or even video clip with deepfakes). Or for example the widespread use of object detection and facial recognition in surveillance systems deployed by DoD. Or the use of AI combined with location tracking and browsing analytics for targeted marketing.
The list of ethics breaches are endless, and I find it super suspicious that those profiting the most off of unethical AI are all too eager to shift public concern to some science fiction Terminator style takeover that, if ever possible, would be a long way out and is not any sort of a priority issue right now.11 -
We are rebuilding an internal web app our company uses and this is how the meeting went down
Me: since this is a big undertaking so we should all work on this as a team and divide the work load
Boss: I can't afford the internal costs to have you all on this * assigns the part timer to the task*
Three months later after launch
Boss: this is not at all what I expected! I want the entire team on this now! It's a top priority!3 -
Refactored an authentication library a while back and teams are now getting around to updating their nuget packages.
It is a breaking change, but a simple one. The constructor takes a connection string, application name, and user name.
A dev messages me yesterday saying ...
Tom: "I made the required changes, but I'm getting a null reference exception when I try to use the authorization manager"
Odd because the changes have been in production for months in other apps, so I asked him to send me a screen shot of how he was using the class (see attached image below).
Me: "Send me a screenshot of how you are using the class"
<I look at what he sent>
Me: "Do you really not see the problem why it is not working?"
<about 10 minutes later>
Tom: "Do I need to pass a real connection string? The parameter hint didn't say exactly what I should pass."
<not true, but I wasn't going to embarrass him any more>
<5 minutes later>
Tom: "The authorization still isn't working"
Me: "Do you still have 'UserName' instead of the actual user name?"
<few minutes later>
Tom: "Authorization is working perfect, thanks!"
A little while later my manager messages me..
B:"I'm getting reports from managers that developers are having a lot of problems with the changes to the authorization nuget package. Were these changes tested? Can you work with the teams to get these issues resolved as soon as possible? I want this to be your top priority today."
Me: "It was Tom"
B: "Never mind."
11 -
Alright, this my fucking rant right here. Distraction? This whole company is a distraction! Boss decided to throw us all in an open work environment doing jobs that require careful concentration. Straight outta college I'm getting handed vague ideas, (make a desktop app that helps our customers put data on the internet, make an iPhone app) with out so much as an inkling of what technologies to use, just make it work.
Ok I will but when you hit a roadblock with very little resources to draw in it's hard to stay focused.
On top of that since I worked in support for a year I'm our senior support person! But sometimes support just doesn't use their brains and I'm using my time to solve very basic problems.
That brings me to my next point, the goddamn piece of shit that is our telephone. Fuck that thing when it rings it's never good. Moreover, since I don't want to get roasted for not being responsive I have the motherfucker forward to my personal cell. So I answer every fucking call and I get so many spam calls!
Not to mention I'm mainly running the hardware show around here. Shits broke I'm the one fixing it. Need new shit I'm putting the order together.
Tried to get a new guy to be the sys admin, ordered a 6th gen board with a 7th gen proc, had to pull 3 machines apart to get that sorted. Then he left bc family issues, and has been gone for weeks.
The other devs are also slam up busy, and the main product is about 15 people's piss on a plate of garb age spaghetti. (I got a lot of shit going on but at least I'm the only one pissing in my spaghetti) it's a constant run around if who does what with a code first plan later mentality causing confusion and delay.
Nobody wants to help anybody because they are also annoyed with this setup and are getting bitched at by customers or management.
Sales is mostly composed of a bunch of crackhead yes men and women who just want a commission and only half know the shit we sell and have sold 15 new features that had not been discussed. But management always says make it happen. In what priority? It's all a priority they say! Wtf.
So yea, then it brings me to me, dealing with this much chaos at work makes it seem like a high amount of chaos in my life is normal. I'm just now learning to control this.
I've had to do a lot of growing up as a person and as a developer. I've went from being the most junior to about the 3rd most seniors and I've no doubt my efforts have contributed to the growth of the company.
I'm a big believer in coding flow, and that it takes at least 15 mins to get in that flow and about 5 seconds to break it. There is no do not disturb on the company chat, everything always on fire it seems.
So fuck a lot of this, but I've done the research and where I'm at is the best opportunity in a 100 mile radius. So I am thankful for this job. Plus I usually win the horror story contest.
So TL;DR the biggest distraction is every fucking thing in this god forsaken place.5 -
I am the sole frontend developer in my project. I have only 6 months of professional coding experience. Just got a call from a person who used to lead me (she is still my lead, technically, but not very much involved in the dev process (management’s decision, not hers)).
She said that a concern has been raised that there have been large number of frontend issues which they (she didn’t specify, I am guessing management) haven’t seen before.
What do you think is the “large number”? Let me tell you. It’s 4.
2 of which are minor CSS issues that couldn’t have been anticipated while coding. They are runtime issues.
One of the 4 is a both frontend and backend issue.
And the last one is a fucking change request!
1 player, many responsibilities, slight issues, RAISE CONCERN - That’s management for you.
Fuck them, I guess.
On top of that, a concern I raised in front of the management regarding the management is not so much of a priority for them. I have a feeling that the concern they raised is just them being a jerk because I raised a concern in the first place.
Fuck them, again!
And again!5 -
I have been creating mods for Skyrim and Fallout for a few years now. One day another modder wanted to make his own game using Unreal Engine 4. I wanted to learn UE4 anyway and the other members have made many mods before, so I joined in.
Well, it turned out I was the only one with a professional programming background (this is where I should have run). The others were all modders who somehow got their shit working. "It works, so it's good enough right?" On top of that UE4 has a visual scripting system called Blueprint. Instead of writing code you connect function blocks with execution lines. Needles to say that spaghetti code gets a whole new meening.
There was no issue board, no concept, no plan what the game should look like. Everyone was just doing whatever he wants and adding tons of gameplay mechanics. Gameplay mechanics that I had to redo because they where not reusable, not maintainable or/and poorly performing.
Coming from a modding background, they wanted to make the game moddable. This was the #1 priority. The game can only load "cooked" assets when it got packaged. So to make modding possible, we needed to include the unpacked project files in the download. This made the download size grow to 20+ GB. 20 GB for a fucking sidescroller. Now, 1 year after release we have one mod online: Our own test mod.
Well we "finished" the game eventually and it got released on Steam. A 20 GB sidescroller for $6.99. It's more like a $2.99 game in my opinion. But instead of lowering the price they increased it to $9.99, because we have spent so much time creating the game. Since that we selled less than 5 more copies. And now they want to make it work on mobile. Guess who will definetly NOT help them.
I have spent ~6 month of my freetime for this project, my rev share is < 100€ and they got me a lot of headaches with all their dumb decisions. Lesson learned. But hey, I am pretty good with UE4 now.4 -
Oh man. I have been waiting for this one. Gather round lil' chil'rens it's story time.
So. I was looking for a new project because my old one was wrapping up and that's what my company does. So I was offered some simulation type stuff. I was like "sure why not, I want to make a computer pretend it isn't a computer no more." Side note I should not be a psychiatrist.
So, prior to coming on to this job I felt stifled by my old job's process. This job was a smaller team so I thought the process would be a little smoother. But it turned out they had NO process. Like they had a bug tracking system and they held the meeting to add things to the system, but that was just fucking lip service to a process.
First of all, they used the local disk on the test box as their version control. and had no real scheme as to how they organized it. We had a CM tool but gods forbid they ever fucking use it. I would be handed problem reports and interface change requests, write a bug to track it, go into the code and about 75% of the time or more it had already been worked. However, there was no record of it being worked and I would have to fucking hunt that shit down in a terribly shitty baseline (standardize your gods damned indentation for fuck's sake) and half the time only found out it was done because when I finally located the piece of code that needed changing, the work was already done.
Then, on top of all that, they ask me what time I want to come in. I said 10am, they said okay. One day I roll in at 10 and my boss is mad. Because I missed a meeting. That was at 9. That I wasn't told about. He says I can keep coming in at 10am though (I asked and volunteered to help get him up to speed on the things I was working he said it wasn't necessary) so I did, but every time I missed a 9am meeting he would get pissed. I'm like PICK ONE!!! They move the meeting to 9:30am (which is not 10am).
This shit starts affecting my health negatively. Stress is apt to do that. It triggered an anxiety relapse that pushed me back in to therapy for the first time in 7 years. On top of that the air quality in the office is so bad that I am getting back to back sinus infections and I get put on heavy antibiotics that tear up my stomach along with the stress and new meds tearing up my stomach. So one day as I am laid out in pain, I call out sick. Two days in a row. (Such a heinous crime right.) Well I missed a test event, that I wasn't even the primary or secondary on.
So fast forward to the most pissed off I have ever been. I get called in to a meeting with my boss's boss. As it turns out, my coworkers are not satisfied by the work that I'm doing (funny because I thought I was doing pretty good given that my only direction was fix the interface change reports and problem reports. And there was no priority assigned to any of them).
And rather than tell me any of this, they go behind my back to the boss and boss's boss. They tell me I need to communicate (which I did) and ask for help when I need it (I never did). That I missed an important event (that I played no part in and gods forbid I be sick) and that it seemed like I didn't want to be there (I didn't but who WANTS to work a corporate job).
They put me on a performance improvement plan and I jumped to another project. I am much happier now. Old coworkers won't even say hi, not even those I was friendly with, but fuck them anyway.5 -
It's sad that there's always a market, especially for what should be absolutely top priority to be kept private.
btw: sorry to OCDs, it is indeed not centered, my mail client zoomed in a little so that happened itself
8 -
Apple... Isn't it obvious?
They once built machines and software that were tested and ready for customers but they went into a direction where saving money and generating more income has the highest priority.
The more recent the version (hard- and software) the more unstable it became. On top of that the crap they produce gets more expensive each iteration. I do own a 2015 MB Pro, that's it. I used to own:
- iPhone X
- MB Pro 2017
- Apple Watch
- Apple TV
- iPad Pro
... All at the same time ... But I sold everything and switched (back) to Android and Linux and no tablet at all. The MB Pro I own is just my travel notebook because of battery life.
I'm very disappointed of Apple's strategical direction and that's why I'm boycotting it as good as I can.13 -
FUCK!
After submitting a registration form I noticed the site is served over plain HTTP. Their marketing site is served encrypted, but login and register are not! What the fuck!!!
Fuck everyone who does this stupid fucking shit with disregard to basic security features! Their goddamn bullshit privacy policy is bragging about how it's top priority to protect their customers' information and shit like that. Get the fuck out, cunts!!
I contacted them so I might have a continuation to this rant if I'm not satisfied with their answers.
Goddamn it!4 -
Just closed a TOP PRIORITY ticket with "as designed"..
After a 1 minute talk with the developer who wrote this code, I found it is actually deliberate..
So I just closed the ticket..
but what really bothers me is:
That developer, is sitting right next to the QA.
HE IS SITTING RIGHT THERE..
We are a small startup company, everyone are sitting around the same table..
communicate much?1 -
Dear Client,
Mentioning "Dear Friend" in email won't make your bug as top priority.
Seriously,
Developer4 -
My current situation:
Manager: How is Project A coming? Project A is top priority. I would like to see a PR today with fixes to the current tickets.
Me: Project A is priority! Sure!
*after 2hours*
Manager: How is project B coming along? I did not see any PR’s coming in?
Me: I am working on project A as it is priority.
*after 1 hour*
Manager: How is project C coming? There is one ticket pending. We need a fix for it today asap!
Me: Starts project C as project A would take more time. Starts Work on project C.
*after 1 hour*
Boss: How is project A coming? Where is the PR?
Me: As you said you need a fix for project C today, i started working on project C as it has only 1 ticket to be fixed.
Boss: I told you project A is priority, why are you working on project C?
Me: *doesn’t reply*
*after 1 hour*
Boss: There is a ticket pending in project D. Did you make a fix for it?
*This is my usual day at work.
*I am the only developer in my current company. It’s not a software development company.
*Note: I do complete all the work and create PR’s for all “pending” work at the end of the day for all projects and leave for home at around 10pm :)
What do you think? Lol6 -
Got informed that there is a bug in production that needs to be addressed on top priority.
Me opens Android studio to check.
Android studio: chill bro2 -
Update: https://devrant.com/rants/4676421/...
I told you all. I fucking told you. Nobody listened to me.
Good people just leave.
This dude who I look upto and is kind of my mentor in the org and has spent a decade here, just resigned.
What the fuck!!!!
And with that, the attrition in product team is insanely high, to the point that it's scary.
My manager is not responsive and is often reactive instead of being proactive.
While the leadership is super excited about the product and everyone says they are hiring more and more people in product team, the design says our product is not a priority for them and we are just left with one design resource.
I was conversing with my colleague and we both are super scared that they shouldn't scrap the product and fire us.
This seems unlikely with all the logical calculations that we did but in a capitalist system we have to be prepared for anything.
I am shit scared right now because there is no clarity on what could happen next.
On the other hand, my skip level manager is taking a lot of interest in my work and is working very closely with me and taking more ownership of our product than my direct manager.
Everyone says our product is a top priority and tech is super agressive about it.
One thing that could happen is my manager leaving and not telling us about it upfront.
In which we would just report to our skip level manager and growth chances would be even better.
But at this stage, this seems super scary to me.3 -
them: welcome new project members, this is our CI/CD pipeline which is completely different from the rest of the company, there won't be any great knowledge transfer, we just expect you to be able to know and use everything. but also, we expect you to work on your tasks and don't waste any time.
me: okay, so my tasks aren't going as fast as expected, because I need to invest some learning so i can set up my project correctly.
later: some help would be nice, i'm stuck right now
coworker: *helps me to fix my problems, which were partly due to misconfigured build servers* i know it's a lot, and unfortunately, for this topic sources on the web aren't so good. i can really recommend this book, this will give a deeper understanding of the topic.
me: okay, yeah i mean, tbh, i'll read the book if the project invests some time for me so i can learn everything that's required, but this won't happen. also, some initial workshop on the topic or anything would have been nice.
coworker: well, i mean, i am a software developer. for me, it is normal that i learn all that stuff in my free time. and i think that's what the PM expects from us.
me: okay, that's fine for you, i mean, if i'm interested in a topic, i will invest my private time. but in this case, PM would just expect me to do unpaid labor, to gain knowledge and skills that i can use in this specific project. i'm not willing to do that.
coworker: ...
me: ...
it's not that i don't want to learn. the thing is that there isn't any energy left by the end of the day. i'm actually trying to find some work life balance, because i don't feel balanced right now, haven't felt since i started this job.
also, this is only one of several projects i'm working on. it's like they expect me this project has top priority in my life. if it wasn't so annoying on different levels, maybe i'd have a more positive attitude towards it.
also, at the moment i find it fucking annoying that i have to invest so much time in this dev ops bullshit and this keeps me from doing my actual work.
if they are unhappy with my skills, either they can invest in my learning or kick me out. at this point, either is fine for me..12 -
// Delivery manager rant part #2
When one of your many stakeholders asks "why isn't feature X built yet?"
Response: have you seen the state of production lately???? Do you really think your item is top of our priority list right now?
-
I'm so fucking frustrated with my ex company CEO, this motherfucker made everyone move to Bangalore costing is employees a good chunk of their salary and this delusional ASSHOLE knew that only half of the expected funding was coming in January 2023 itself and they'd be out of funds by July/August, they let go few folks from the team, fired the entire marketing team and expected to make the product profitable. The only reason I had stayed at that time was because the product was interesting to build and the scale I was working with was crazy like 100k request per minute peaks and avg of 10k rpm. I left the company in August...
This MOTHERFUCKER hasn't paid out final settlement after leaving for most employees and he openly says to the folks who are still working there that paying us is not his priority.
I hope your Atlas cluster gets fucking deleted, accesses revoked and entire AWS setup goes down forever, bitch.
We can't goto courts because the company law tribunal needs atleast 1 crore (1.2 million usd) of unpaid dues to declare it insolvent in a years time..
This asshole deducted taxes from our salaried but didn't pay them to the income tax department for an entire fucking financial year.
What a cheating, delusional, sick bastard. And he's still not willing to sell off the company to pay off the debts and call it a day.
Aarrghhhh on top of losing 2-3k USD I might have to pay my taxes approx 5-6k USD to the govt to keep my records well maintained.
What a grade A delusional asshole 😡
If he won't clear the dues till December, I'm gonna launch a mass of social media posts and destroy his reputation so that he doesn't get one penny of VC funds in the future I'm gonna make sure of that...4 -
When you offer to help out a fellow coworker on the top priority feature he is developing and he just sends you the branch and stops working on it.2
-
Oh,I have learned a lot, I would not say from programming but from the career as a whole
Never get peer pressured
Always show empathy
If in a leading position, taking care of people is your top priority
Overconfidence will destroy a lot of good work
People by definition will always remember your mistakes
Never get over involved in the company you are working for, it's just a job
Your health is more than important
Nobody knows everything
Always be humble
There is a lot of bullshitters out there
Success is relative
Competition is high and there is always someone with better skill set, so you will suffer if you don't accept that -
The worst type of debugging: Programming an MCU without a Serial Monitor.
Some Context: I've spendt today about 3h+ on getting an attiny 45 to read 3 digital values on 3 pins. So for every test I wanted to make, I needed to put the MCU inside a socket put this socket on a arduino and flash it. Then extract it from the socket and put it on a breadboard for testing.
After getting headaches for nothing making any goddamn sense, I ended up noticing that one input pin is a multiplexed reset pin with the reset having top priority and no way to change it. So whenever this pin should have read a low signal, it got held in reset! FML -
When you work for a week day and night to compete a feature, because top management said it's the highest priority. Then when you're about to send it off to test, they tell you it is no longer required.2
-
!Rant
CTO: "We have a project that is the top most priority get it done"
CTO: "We have some tickets logged for another project get them fixed this is of the highest priority"
CTO: "I want a new feature in another project I want this done now It is top priority!"
Next day, Client comes in CTO shows him around
CTO: "You are still working on this!"
... Arg, its as if the guy thinks giving something a top priority gets it done instantly3 -
* Gets handed additions to current software platform (web)
* Gives back estimte of time after meeting with everyone and making them understand that once the testing phase of the project is reached there will be no changes, tests should be exhaustive and focus on SAID FUNCTIONALITY of the new additions. NO CHANGES OR ADDITIONS AT THIS POINT IN TIME
* All directives, stakeholders, users etc agreed on my request and spend an additional hour thinking of different corner and edge cases as provided by me in case they can't think of them (they can't, because they are fucking stupid, but I provided everything)
* Boss looks irritated at their lack of understanding of the scope and the time needed, nods in approval after he sees my entire specification, testing cases, possible additions to the system etc
* All members of the committee decide on the requirements being correct, concrete and proper.
* Finish the additions in a couple of weeks due to the increased demand for other projects, this directly affects the user base, so my VP and Director make it a top priority, I agree with their sentiment, since my Director knows what he is doing (real OG)
* I make the changes, test inside of my department and then stage for the testing environment. Everything is ready, all migrations are in order, the functionality is working as proper and the pipeline for the project, albeit somewhat lacking in elegance is good to go.
* Testing days arrive
* First couple of hours of test: Oh, you know what, we should add these two additional fields, and it would be good if the reporting generated by the system would contain this OTHER FORMAT rather than this one.
* ME: We stated that no additions would be done during the testing environment, testing is for functionality, not to see if you can all think of something else, even then, on June 10 I provided a initial demo and no one bothered to check on it on say something.
Them: Well, we are doing it now, this is what testing is for.
Me: Out of this room, the software engineer is me, and I can assure you, testing is not for that. I repeatedly stated that previously, I set the requirements, added corner cases, tables charts everything and not one single one of you decided to pay attention or add something, actually, said functionality you are requesting was part of one of my detailed list of corner cases, why did you not add it there and then before everything went up?
Them: Well I didn't read it at the time (think of the I in plural form since all of these dumb fucks stated the same)
Then my boss went on a rampage on their dumbasses.
I fucking hate software development sometimes.
Oh well. Bunch of fucking retards.4 -
Our company doesn't have much structure. One of 4 people can have me working on a project, or all 4 at the same time. And every few hours 1 of them asks how their project is going and get huffy if I'm working on one of the other guys, claiming top priority. After 3 years, I've been able to just go with it. Half the projects have never actually made it to production. Sometimes, they'll even forget about their projects.4
-
I need a cloning machine for those days when 3 clients call support for top priority issues and each one needs it in the next 20 minutes2
-
Boss tells me every other week to "set focus" on a completely different topic without loosing a word on the "top priority" the day before. Or he asks for the other (not finished) feature to be ready "in the next few" days/hours.
Yeah. A real sunbeam in dark times.1 -
When everything you're sent gets assigned top priority and the only way you can tell the difference is by how many exclamation points are used and the occasional uppercase...
-
After a week of getting new projects thrown at me, I finally get a block of time to start one of the larger, more complicated one.
30 minutes into planning it out, prepping the workspace and diverting 90% focus to said project, someone busts in with a more complicated top priority project that needs done by end of day.2 -
Is there anything nicer than having home office Friday and meeting up Monday only to discover that you were excluded from a meeting that Friday and they decided on a bunch of things that invalidates a lot of your past weeks work, making it top priority to resolve and now exceeding deadlines…3
-
A**hole of a "Technical" Delivery Manager, who has changed orgs after at-most every 14 months, and says she can't read code or even understand technical things like Kafka.
It's been 12 months she's joined here, I bet she's again gonna jump to somewhere. Why the hell do they give these roles if there's no relevance.
Only thing she knows is to blame/assign anything to anyone without giving a f**king read.
Any random thread, she'd just ++ and say, ensure this is done on priority. There are 7 priorities already assigned, atleast reply when I ask you on mail to arrange your priorities in order so that you won't say we messed up. We've no issues ticking one thing at a time from the top.
Atleast do something God damnit!1 -
So today we had a pre-sprint-planning meeting where the POs told us about the stories currently in the backlog. They went ahead and "roughly prioritised" some of them. Their priorities were:
- normal (but asap please)
- has to be done this sprint, because the feature has to be in the next release (code freeze after this sprint)
- top priority, because this has to be in the previous release (which was released last friday)
The non-normal stories alone are about twice our normal velocity. Good job guys. Good job. -
I’d like to have a DevRant dataset so I can make some great visualizations, text analysis, etc. of the things we hate the most. This is top priority, thanks in advance.5
-
Story of my first successful project
Being part of a great team, I've shared in a lot of successes, one I am particularly proud of is my first attempt to use agile methodologies in a deeply waterfall-managment culture.
Time was June/July-ish and we applied for a national quality award where one key element in the application stated how well we handled customer complaint resolution.
While somewhat true (our customer service is the top-shelf good stuff), we did not have a systematic process in resolving customer complaints. Long story short,
the VP lied on her section of the application. Then came the 'emergency', borderline panic meeting (several VPs, managers, etc) to develop a process to better manage
complaints before the in-house inspection in December.
As most top priority projects go, the dev manager allocated 3 developers, 2 DBAs, and any/all network admins we would need (plus all the bureaucratic management that wanted their thumb in the pie).
Fast forward to August, after many, many planning meetings, lost interest, new shiny bouncing balls, I was the only one left on the project. The VP runs into the dev manager in the hallway and asks "Is my program done yet? If its not ready before December with report-able data, we will not win the award."
The <bleep> hit the fan...dev manager comes by...
Frank: "How the application coming along? Almost done?"
Me:"No, haven't really started coding. You moved Jake and Tom over to James's team, Tina quit, and you've had me sidetracked helping other teams because the DBAs are too busy."
Frank: "So, it's excuses. You really think the national quality award auditors care about your excuses? The specification design document has been done for months. This is unacceptable."
Me: "The VP finished up her section yesterday and according to the process, we can't start coding until the document is signed off."
Frank: "Holy f<bleep>ing sh<bleep>t! No one told you *you* couldn't start. You know how to create tables and write code."
Me: "There is no specification to write to. The design document is all about how they plan on reporting the data, not how call agents will be using the application to serve customers."
Frank: "The f<bleep> it isn't. F<bleep>ing monkeys could code against that specification, I helped write it! NO MORE F<bleep>ING EXCUSES! This is your top priority from now on!"
I was 'cleared' to work directly with the call center manager and the VP to develop a fully integrated customer complaint management system before December (by-passing any of the waterfall processes that would get in the way).
I had heard about this 'agile' stuff, attended a few conference tracks on the subject, read the manifesto, and thought "I could do this.".
Over the next month, I had my own 'sprints' and 'scrums' with the manager (at the time, 'agile' was a dirty word so I had to be careful of my words and what info I shared) and by the 2nd iteration had a working prototype.
Feature here, feature there (documenting the 'whys' and 'whats' along the way), and by October, had a full deployed application.
Not thinking I would get a parade or anything, the dev manager came back from a meeting where the VP was showing off the new app to the other VPs (and how she didn't really 'lie' on the application)
Frank: "Everyone is pleased how well the project turned out, except one thing. Erin said you bothered him too much with too many questions."
Me: "Bothered? Did he really say that?"
Frank: "No, not directly, but he said you would stop by his office every day to show him your progress and if he needed you to change anything. You shouldn't have done that."
Me: "Erin really seemed to like the continuous feedback. What we have now is very different than what we started with."
Frank: "Yes, probably because you kept bothering him and not following the specification document. That is why we spend so much time up front in design is so we don't waste management's time, which is exactly what you did."
Me: "We beat the deadline by two months, so I don't think I wasted anyone's time. In fact, this is kind of a big win for us, right?"
Frank: "Not really. There was breakdown in the process. We need better focus on the process, not in these one-hit-wonders."
End the end, the company won the award (mgmt team got to meet the vice president, yes the #2 guy). I know I played a very small, somewhat insignificant role in that victory, I was extremely proud to be part of the team. -
I had a complaint about a product I bought from a store a while back. I was resistant to taking into the store because the people there make you feel like you are stealing when trying to return a defective DVD. So I contacted the store via their website. I put in my first and last name and my email in the message to them. This is an excerpt of what I got back:
---
Response By Email (Triston) (12/12/2019 03:56 AM)
Hi Phuckin,
Your satisfaction is our top priority and your comments have been forwarded to your local Store. The management team there will take appropriate action and you can expect a response from them within three business days.
<store specific info>
Customer By (Phuckin Chit) (12/11/2019 03:40 PM)
<details of my complaint, etc>
---
Apparently I had created an account with this store a while back when I was angry. Hence my name being reported as Phuckin Chit. Even though I entered my name in the form it used the stored name associated with my email. At this point I am not sure they are going to help me.1 -
There is a difference between HR and CHRO, senior marketing expert and CMO, senior developer and CTO.
There is a work ethic stance of always staying in your scope and saying "that's not my job" to any extra stuff someone asks you to do. This is acceptable and perfectly normal. Any team member has a contract, and you owe your company nothing beyond that.
That stance is however only acceptable from regular workers, not a chief board members. For any acronym position that starts with a capital letter C, that stance is not acceptable anymore. That's the difference.
Board members should have a share. Board members should have the right to dictate how a company is, at least proportional to their share or more.
Only those who display T-shaped skills, ownership and interest in the whole business model, not just their scope, are eligible to graduate up to a chief position. If you're not a chief officer, but you want to get there, this is what you do. Analyze the business as a whole and come up with measurable and provable ways of making it better, because this can't be formalized, and thus can't be a part of your contract. This is the surest way to the top.
I am of course speaking of the companies where the main priority is the business and its ethics and not the founder's ego. The latter can't be saved.4 -
The DEVRANT SEARCH could be improved.
Often wrong results are on top, because the algo accepts 1 different character and tags have no priority.
Example: I clicked on the tag "hangover".
Among the top results there were rants with "handover" and "hannover" (German city).
The first rant with the tag "hangover" was at position 18
Wouldnt the search result be better with another logic?
Priority 1: Tags with exactly the same word
Priority 2: Rants with exactly the same word
Priority 3: Tags with similar words/expressions
Priority 4: Rants with similar words/expressions -
DREAM 1
(my comments look like this)
A kikiland metro system. It's extradimensional and shapeshifting. When you enter it, it adapts to your needs. The people inside (they're probably just vinyl shells), the social circumstances, all generated for you.
When you enter it, it knows where you want to go. It spawns exactly one train just for you. It will be the first, it will be the last. You have to catch it to go where you need. If you miss it, there will be no more trains, and you have to wait till the metro station closes for the night and reopens.
It's always you entering, catching the train that arrives just in time, going to where you need to go and exiting.
Because of its extradimensional nature, you cannot agree to meet someone there — every person has their own personal metro generated just for them every time, with exactly one train going exactly to the station you need.
It's used by BLA as a form of control. When they don't want you to go somewhere, the train won't spawn. Or, it might diverge and get you to some other place. It isn't known whether the map can be altered on the fly or not. So far, the consensus is that the map is persistent and is a public knowledge, and it's just the metro itself that is extradimensional. But, no one ever saw the real metro in its real form, and not the top layer that protrudes into the three-dimensional world you can interact with. It might be the case that they can make people disappear by creating ad-hoc stations that don't intersect with the real world, trapping them in places that are nowhere in particular.
(it took seeing BLA once in one dream to make all the following dreams include them. Sigh.)
Kikiland also has a school, and it always had it. I befriended a chemistry teacher there. His classroom is small — exactly as deep as other classrooms, but really narrow. There are no desks there, just his desk and some bookshelves. Chemistry isn't a priority there — his class exists only because it should. No one attends it. This is why he was so pleased to meet me. Despite his classroom being located on a busy floor, its door is overlooked by students, and NO ONE ever enters it. He just sits there, waiting for students to arrive, but they never do.
He has a secret, though, because of course he does. In the game Control, if you complete the main storyline before you complete some side quests, one of the main characters will be sitting in the C-suit hall, doing her things, waiting for you to come and talk to her. But at the same time, she will be waiting for you deep down the oldest house's mines, again, just sitting there, waiting for you to take the quest. This teacher is the same.
If you have a good relationship with him, and you attend his class, the classroom will change to a tunnel entrance, with him being the security guard. He's your friend, he'll let you in. It looks like Fallout's vault entrance. THIS is how you enter the REAL kikiland metro. (Dream 1 ends here.)
Episode 2
Tiny waterborne rat puppies whose mouth is their entire face unfolding like a piece of paper with teeth covering it as a grid. (I wrote about them already, but here they are again.) They are _tiny_, a bit like tadpoles. Also, like tadpoles, they die if you touch them out of water. As I was flying over some mountain resort (I routinely fly in my dreams, but it feels more like a very low gravity falling I can control, like using a parachute in GTA San Andreas), I dumped them to a location that resembled the garden level of Prince of Persia: Warrior Within for my cat to eat. It didn't want to. -
I love being a consultant, and I love my job. However, I’ve been working with this client for the past few months and the past few weeks have been so draining. 90% of the people at the client’s side are super nice people, and then there’s this one person that just barks orders at us whenever a tiny thing is broken. Everything is urgent, everything is top priority, and we need to drop whatever we’re doing to fix what they deem urgent. I am currently pretty much the only dev doing both support and feature development at the same time and I am getting mentally very tired.
Whenever something is broken we get shit feedback, but for all our efforts there’s never any positive feedback. Mind you, the project isn’t even publicly accessible yet, it’s in a “alpha” phase where there are only a handful of users testing the program.
How do you guys deal with people like this?3 -
Lately with our client, everything has become very "urgent" and top priority. So much so that I’m asked to drop a top priority issue to tackle a new top priority issue, and then asked to drop that one too to take on another new “even more“ top priority task. In the end they’ll all have to be dealt with but dang I’m losing all sense of continuity, I’m losing my efficiency as my flow keeps on being broken by something new I have to jump to and in the end I’m kinda losing my sanity. Fuck this!1
-
TLDR: I don't feel the need to be working at top product companies anymore.
Brief:
The craze to be a developer in top product companies has literally worn off for me in the past few months since I am working from home.
Like if I have to continue this WFH lifestyle it literally won't matter if I am working for a top product company or a startup...
The priority has shifted towards
1. A good team
2. A well-natured and polite manager
3. A flexible working culture which is better suited for remote work
4. And obviously a good salary🤑5 -
It's pretty hard to work with relatives in the family. They expect too much from you. More overtime work, no or less pay, demands are somewhat unrealistic because they want their project on top priority and the list goes on. 🤔1
-
Debugging is fine, totally part of the job!
Constantly fixing sh1t and new reports of another pile of sh1t coming every day like somebody is throwing them with shovels at us just to open the codebase that is written by the folks who aren't here anymore with some list of obscure libraries that is last maintained about 5 y ago is not ok.
It is not buggy codebase it is actually coddy bugbase!
I tried to be vocal several times to change technology to more suitable one, to make some improvements and to remove code smells(there is a ton of it, smells like organic garbage dumpster with rotten eggs) but "everything works" and there is no real "value for the customers" in that(fixing, refactoring etc.)!!!
Yea it works with sh1t ton of bugs reported every week. Nobody gives a shit, just contempt with their mediocre lives solving bug at the time while i feel like I'm wasting my time and talent on wrong people and fixing other's shit.
That is what happens when prototype becomes product and ships to production because numbers, money and sh1t!
this is why we who care about our career can't have nice things! I am not god damn pest control, I am f*ckin developer.1 -
!Dev
Fuck people using trace rifles in momentum control. How the hell am I supposed to kill someone who kills me in two rounds and also fires at 1000 rounds per minute. I was trying to get the catalyst aka upgrade for the seasonal weapon which is pretty bad and the upgrade makes it usable but I am getting ripped apart after my first kill because someone can kill me with 2 bullets wherever he shot me.
Yes momentum control is supposed to be a gunfight mode and it comes around rarely but that does not mean a broken weapon can roam around killing anybody in sight before they even know you fired a shot at them from some lane. Shotguns do the same but you need to get close. Shotguns are still a problem but at least you can dodge or counter with a shotgun since your radar tells you someone is nearby and snipers need a headshot. These weapons can fire at your toe and you are dead. Oh the devs knew that such fast firing weapons wil be op and needed their damage and made them use the same ammo as shotguns, sniper and non heavy grenade launchers. However the game mode gives all weapons a damage buff which is enough for trace rifles to be broken. Yes you can use other primaries but what are you gonna do when a auto rifles kills you with two shots to the toe. And since they burn ammo quickly and take more rounds to kill then their counterparts like shotguns which use he same ammo as them they spawn in with 50 in the mag and anybody who is using shotguns snipers or grenade launchers give them ammo and they only need two rounds to kill. Also after I kill 50 PvP opponents I need to kill a few hundred opponents in PVE or PVP to actually apply the upgrade and who you kill does not matter.
Seriously and the second weapon I want to upgrade which is able has tracking but you need to aim down sights after hipfiring the tracking shots
which dl negligible damage so they explode or aim down sights and shoot which deals more damage but I am probably not going to have enough time before some random kills me again.
And this is just the first game. From what I heard it was supposed to be a fun game mode which focused on gunfights with your primary not the infamous laser tag show of Prometheus lens which happened a few years ago but now all trace rifles can do that. Oh and I still need to get 50 kills there for a seasonal challenge so I can get the free version of the premium currency and I can only skip one challenge and I have already skipped one challenge since it requires a dlc K don't own.
Seriously why cant some actual good game come up to challenge this. All the competition seems to be third person shooters. Also most of the guns don't feel good and lore is pretty lacking but lore is not top priority. The only competition is Warframe which is not my style, Titanfall 2 but I get insane pings from here so no multiplayer so after the story nothing to do unless I want to do airtstrafing which is useless since I can't play multiplayer. Granted Titanfall 2 is not a looter shooter but the guns feel good and the movement is too good and Halo 1 - 3 since I heard 4 and 5 are pretty bad and I have only played halo 1. I might complain about jackal snipers in halo 2 but at least they have fixed spawns.
Maybe I am overreacting since it is my first game of momentum control
Top Tags
Weekly Rant
View