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
Search - "define"
-
#define f fuck
I think it's time to fing start carrying my fing phone around in a fing metal box !
f Google !
f it again !2 -
Manager: You can’t define an async function without using await.
Dev: Yes you can.
Manager: Well you shouldn’t, there’s no point!
Dev: Yes there is. It can turn blocking synchronous logic into work performed concurrently. In this case the perform—
Manager: It’s called async *await*. Async *AWAIT*! Did you hear the two parts to that? You shouldn’t ever have one without the other. THEY GO TOGETHER. Worrying about concurrency is for people who use callbacks which just goes to show how out of date your skills are. I’m reading a book on javascript and there are so many advanced techniques out there that I haven’t even seen you use ONCE!
Dev: …
*I looked at the book he’s reading, it’s from the < ES6 era… no wonder he doesn’t see me using any of those archaic patterns/hacks/workarounds…*13 -
Manager: Here's the design for the next feature, we're ready to hand it over to the consultant
FullStackClown: Uh... okay... is it spec'd out with requirements?
Manager: Huh?
FullStackClown: Well, already look at this design and user flow, did you consider what happens when <insert edge case X here>, <insert edge case Y here>, or <insert edge case Z here>? How is the consultant going to know what to put in for business logic if you don't even know or define it yourself?
Manager: Huh?
FullStackClown: Sigh... yeah, I'm too busy right now to be a kindergarten teacher, come back in a few days once you understand how your own feature is supposed to work
Manager: ...
Dev: ...5 -
Shoutout to my recent client who not only referred a friend of theirs to me for an additional project but is first making them define their project with process models before the customer interview to ensure no one’s time is wasted.
I always recommend to my customers that they define their project before taking it to me because otherwise it becomes billable consultation hours if I sit down with them and talk about the project and create the process models on my end.
This is a good customer experience and what I like to see when working 😁5 -
[CMS of Doom™]
The gift that keeps on giving...
When you think you've seen it all after 7 months in legacy hell, you get another gift:
Let's say you use PHP, but your IQ is in the zero-ish range, then it is obvious to:
- use define() for constants in all your config.*.php files
- then include said config.*.php files multiple times
- and because define() doesn't overwrite the same constant, because it's - you know - a constant, you instead of including just do a file_get_contents() to read the PHP file as string and then parse the values by Regex.
The dev who wrote this was truly one of the devs ever.12 -
Screw the Chief Technology Clown role...
I'm now officially Chief Babysitting Clown...
Skills I can teach you include the following:
- How to read JIRA tickets
- How to write JIRA tickets
- How to check colleagues' calendars
- How to define requirements in English and not some sort of technologically challenged caveman language
- How NOT to do any programming (since I don't have time for that anymore)
And many, many more! Inquire within!6 -
Im getting tired of this fucking scrum team.
First of all let me introduce our backend team which takes 3 weeks to add one fucking column to database and in the end turns out they fucked up RabbitMQ RPC implementation so the column is not syncing with our app at all so now we have to wait 2 extra weeks until that will be working. Best part is that backend fucker who fucked up doesnt even feel like hes blocking a feature and would rather sit for extra few days and do nothing until he gets reassigned his pile of shit back to him than clean up his own shit.
Then we have business analytic who doesnt know how to define tasks properly so I have to record each grooming meeting so I would know what to fucking implement because he doesnt even bother to take proper notes. Which results in not fully defined tasks, which results in unexpected behaviours and MR's stuck in limbo for weeks.
Also lets not forget QA guy who doesnt even bother writing scenarios, I as an app dev have to write them myself just to be sure that fucker will test everything thoroughly.
Then we have fucking devs from consultancy agency who apparently have 6 years of experience (I have barely 2) and these fuckers are spamming me daily with the most basic questions. After each grooming they rush to assign themselves tasks which are not even defined properly yet and not even in this sprint, but fuckers are lazy so thy want to reserve easier tasks for themselves. Pathetic.
At least I have a decent senior on my team, but sometimes he patronizes me so much that I start asking me what I am doing in this team.
Fuck this shit, I asked for a 43% raise and if Im not getting it in 2-3 weeks im outta here. Fuckers.5 -
Seriously, at what point did the good, kind, selfless souls who write tutorials and guides online turn into fucking food bloggers?
I've been an engineer about 15 years, so I still have to google most of the code I write as I write it, and this week I've been learning a new framework.
Ten years ago it'd be "here's how to..." then the thing you want to do.
Now it's "For the longest time, I didn't want to use Gradle..." followed by a summary of the last week in their life.
I really don't care about your Journey with Rust, I want to know how to define an optional parameter. I don't give a rat's fucking dick how much faster this is than that, my hands are tied by whoever started this mess - just tell me how to make it work.
I guess there's something to be said for remembering things between sessions.4 -
Imagine seeing words like developer:ess, member:esses or user:ess in artices on the web becoming more and more popular.
Pretty dumb, yes?
That’s what happening right now with the German language with something called gender-language.
It hurts my eyes reading Entwickler:innen, Mitglieder:innen and Benutzer:innen.
People argue that words like Entwickler are excluding woman by using the male form by default. But it’s just a matter of perspective. Why not just define this as the neutral form just like in english? Developer is neither male nor female. Everybody is fine with that.
Yet the Germans are messing around with this gender shit and making text unreadable for no reason at all.
It’s just bullshit!21 -
[CMS of Doom™]
Imagine creating a CMS so bad that you let the owner (who I work for) define in a simple input field what email address is used as the sender address for the welcome email of newly registered users.
Basically they filled in a personal email of the company some 3 years ago AND of course the person with said email address left the company a few months later thus for some 2-3 years newly registered users received a welcome email with a sender address of an unavailable user.
And I thought I've seen it all in this CMS...3 -
TL;DR; do your best all you like, strive to be the #1 if you want to, but do not expect to be appreciated for walking an extra mile of excellence. You can get burned for that.
They say verbalising it makes it less painful. So I guess I'll try to do just that. Because it still hurts, even though it happened many years ago.
I was about to finish college. As usual, the last year we have to prepare a project and demonstrate it at the end of the year. I worked. I worked hard. Many sleepless nights, many nerves burned. I was making an android app - StudentBuddy. It was supposed to alleviate students' organizational problems: finding the right building (city plans, maps, bus schedules and options/suggestions), the right auditorium (I used pictures of building evac plans with classes indexed on them; drawing the red line as the path to go to find the right room), having the schedule in-app, notifications, push-notifications (e.g. teacher posts "will be 15 minutes late" or "15:30 moved to aud. 326"), homework, etc. Looots of info, loooots of features. Definitely lots of time spent and heaps of new info learned along the way.
The architecture was simple. It was a server-side REST webapp and an Android app as a client. Plenty of entities, as the system had to cover a broad spectrum of features. Consequently, I had to spin up a large number of webmethods, implement them, write clients for them and keep them in-sync. Eventually, I decided to build an annotation processor that generates webmethods and clients automatically - I just had to write a template and define what I want generated. That worked PERFECTLY.
In the end, I spun up and implemented hundreds of webmethods. Most of them were used in the Android app (client) - to access and upsert entities, transition states, etc. Some of them I left as TBD for the future - for when the app gets the ADMIN module created. I still used those webmethods to populate the DB.
The day came when I had to demonstrate my creation. As always, there was a commission: some high-level folks from the college, some guests from businesses.
My turn to speak. Everything went great, as reversed. I present the problem, demonstrate the app, demonstrate the notifications, plans, etc. Then I describe at high level what the implementation is like and future development plans. They ask me questions - I answer them all.
I was sure I was going to get a 10 - the highest score. This was by far the most advanced project of all presented that day!
Other people do their demos. I wait to the end patiently to hear the results. Commission leaves the room. 10 minutes later someone comes in and calls my name. She walks me to the room where the judgement is made. Uh-oh, what could've possibly gone wrong...?
The leader is reading through my project's docs and I don't like the look on his face. He opens the last 7 pages where all the webmethods are listed, points them to me and asks:
LEAD: What is this??? Are all of these implemented? Are they all being used in the app?
ME: Yes, I have implemented all of them. Most of them are used in the app, others are there for future development - for when the ADMIN module is created
LEAD: But why are there so many of them? You can't possibly need them all!
ME: The scope of the application is huge. There are lots of entities, and more than half of the methods are but extended CRUD calls
LEAD: But there are so many of them! And you say you are not using them in your app
ME: Yes, I was using them manually to perform admin tasks, like creating all the entities with all the relations in order to populate the DB (FTR: it was perfectly OK to not have the app completed 100%. We were encouraged to build an MVP and have plans for future development)
LEAD: <shakes his head in disapproval>
LEAD: Okay, That will be all. you can return to the auditorium
In the end, I was not given the highest score, while some other, less advanced projects, were. I was so upset and confused I could not force myself to ask WHY.
I still carry this sore with me and it still hurts to remember. Also, I have learned a painful life lesson: do your best all you like, strive to be the #1 if you want to, but do not expect to be appreciated for walking an extra mile of excellence. You can get burned for that. -
JIRA life:
Project leader proceeds to put what is actually two separate issues in the title. I'm already raging. I go to take a look at it.
I read the description - ANOTHER (this makes it three now) totally seperate issue in there.
Just fuck you I'm so sick it i see it over and over again no matter where I go or what project I work on its all the same bullshit.
"wE wAnT tO cLeARlY dEfINe iSsUeS aNd MoVe RaPiDlY"
YEAH THEN F&Q*@#()#$(@)#$ DO YOUR F$*(@#(*&$ JOB!!!! I'M DOING MINE, IN ADDITION TO DOING YOURS, CLEANING UP YOUR ABSOLUTE MESS THAT YOU LEFT!!!!1 -
I'm learning Rust as a case study for my own programming language. It's funny how many approaches exist to the humble loop.
- In classic procedural languages, a loop's job is to repeat actions, and as such it provides a multitude of tools to control this repetition.
- In all languages with iterators, a for-in loop is a construct that does something with every element of a collection. In languages with both iterators and generator functions, this can even be used to define a sequence in terms of another.
- In Rust, a loop is an expression that obtains its value through repeated execution. It can also be used like a classic loop, of course, but this is the interesting part.
- My little language is a functional language, so "loop" is the Y combinator. To loop means to define the value of an expression in terms of itself. It's the only looping construct, gets special treatment from the type checker and it's also used in recursive type definitions. -
How to disconnect from work after working hours? Im working for the last 4 months as a mid level dev in this company. I mean Im able to problem-solve and do my work but sometimes I get so addicted to problem solving that I get worried and become obsessed, hyperfixated (especialy if Im stuck on something for lets say a couple weeks). It goes to the point where I work from home 12-14 hours a day just to figure out some bug in the flow.
Thing is, our codebase is large and when doing every new refactor/feature some surprises happen. I dont have a decent mentor who could teach me one on one or even do pair programming with. All i have is just some colleagues who can point me to right direction or do a code review from time to time. Thats it.
I dont know why I take this so personally. For example I had to do a feature which I did in 1 week, then MR got approved by devs and QA. After that during regression they found like 3 blockers and I felt really bad and ashamed. While in reality our BA did not define feature properly, devs who reviewed it didnt even launch the code and poke around in the app, and our team's QA tested only the happy scenario. Basically this is failing/getting delayed because of a failure in like 6-7 people chain.
However for some reason Im taking this very personally, that I, as a dev failed. Maybe due to my ADHD or something but for the next days or weeks as long as I dont find solution I will isolate myself and tryhard until I get it right. Then have a few days of chill until I face another obstacle in another task again. And this keeps repeating and repeating.
My senior colleague tells me to chill and dont let work take such a toll on my emotional/physical/mental health. But its hard. He has 7 years of experience and has decent memory. I have 2-3 years of experience and have ADHD, we are not the same. I dont know how to become a guy who clocks out after 8 hours of work done everyday. Its like I feel that they might fire me or I will look bad if I dont put in enough effort. Not like I was ever fired for performance issues... Anyways I dont know how to start working to live, instead of living for work.
I hate who Im becoming. I dont work out anymore, started smoking a lot, dont exercise. I live this self induced anxiety driven workaholic lifestyle.6 -
I have a thought
Maybe 3 dimensional beings aren’t able to comprehend the concept of “nothing”, because it’s a concept existing outside our dimension.
If we are able to understand “nothing”, then we could properly define the origin of the universe and how “from nothing came something”.
But because it’s out of our scope/dimension, there is just no hope of uncovering what it really is.
I may be wrong, let me know what you think?6 -
Tests define behaviour, if code isn't tested then there is no way of knowing what it should be doing so it therefore cannot be working correctly.4
-
you know what's good to do in example code?
( ͡° ͜ʖ ͡°) just frickin struct { someshit1, someshit2} someshits then define 'someshit' as a standalone var after it and use them all next to each other constantly instead of just having them wrapped up or seaparated1 -
Did someone already thought about how color highlight can be better? It's been 4-5 years now that I'm coding on a virtual console that run on iPad with a monochrome code editor. Despite the fact that's remind me the old days when I was 8 years old, that doesn't stop me for coding with it.
I mean, is it really important to know that strings are red and numbers are yellow? How does that help me? They are both literal and behave to the user-content categories.
I was talking with my friend, and he says he likes to know if something is a keyword or an identifier. In C++, a lot of common keywords to define stuff and control the flow are often the first word and easy to spot.
A couple of months ago, I tried Flutter, and the editor can highlight ident blocks and give them different colors, but with Flutter, it's easy to get 10 or more ident levels, Does the color help? Splitting the code does.
I think, there is so much stuff that is more important than coloring the grammar of a language. For instance: knowing if an identifier belongs to which Rust Crate because, It's easy to stack 10 or more dependencies in one file that as better chances of names collisions.
Knowing if an identifier was recognized, if it used, if it's a local, a member, a global, a compiled value or a macro seems more important.
I would like to color block of code that is important or sensible. That will help my coworker about the severity of a particular place in the code.
What do you think?1 -
1 - Correct me if I’m wrong, but in true Agile, a product owner ought to be able to interact directly with the dev team, and vice versa, in the card/conversation/confirmation process of creating, estimating, and executing the user stories, correct?
2 - If Company “A” contracts with Consultant “A” to have software developed, and then Consultant “A” then contracts with Company “B” who then contracts with Consultant “B” to do the development, who would you define as the Product Owner?
3 - If Company “B” is barring Consultant “B” from talking with Company “A” and Consultant “B”, is Agile even possible?7 -
Have an object that uses a macro to define its function bodies. I needed to interface to that object in a different way. So I wrote and object that calls functions on that object and presents a different interface. I used macros to define the function bodies...
-
I have no idea what is happening. literally. am i considered to be a human just because human beings decided to call humans, human being? are the words coming out of my thoughts, the real words that my human form is intending to convey? you! all of you! what is real for you? how do you define the right thing to do? Do you live your life according to your real self or according to what others expect of you? are you living your life truly? what is the truth? how can you consider a truth to be true if that truth has been made by the same creature that also had no idea of what the truth was and suddenly just came up with it? how?2
-
Define programmers
The mythical creatures who solve all the problems of lesser mortals without having to move from their desks. -
OOP question: Can someone fucking explain to me what does it mean to hide complex implementation behind an interface?
Also whats the point of using interfaces when you can define methods in an abstract class and just override them in subclasses in order to get class specific implementations?18 -
I have to participate in this retarded conference for 2 days and then I will have to join this fucking summer gathering on my weekend and that will take whole day. Fuck this fucking corporate bullshit. Better give me a fucking raise or better yet start fucking managing this scrum team because half of devs are not pulling their fucking weight.
Fucking BA too lazy to update issues with new details after grooming so each time I pick a new task I either have to somehow remember what we discussed weeks ago or I have to spam you with questions so you would run around like chicken without head while gathering answers to questions that were already discussed because you are too lazy of a fuck to compile notes. And even that is not enough, my merged MR's apparently dont cover all the use cases because your'e too incompetent to even figure out how our app works and define properly the task.
And then theres supposedly a techlead dev whos not taking a ticket when theres 3 days left till end of the sprint and he goes: "But a task spillover will happen!!!". Yeah so I guess just sit on your ass and wait for new sprint so you could pick yet again another low hanging fruit task and marinate it for weeks.
Motherfucker I checked your MR's in the last 6 weeks you did 1 week worth of work. You are a techlead but your only dev colleague is asking us for help daily because you dont even help him Fucking lazy and incompetent bastard.