Joined devRant on 4/26/2018
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
If your manager asks you to write a raw algorithm based on raw data in order to properly structure, sort and filter that data, how long do you take on average to complete said task?
Here's a text file with a bunch of continuous data like: john doe 5555 my street 123 karen wiscott 12347 her street 22 peter wright
..and then you first have to start identifying boundaries for each data entry (which is a task on its own, with comparators and shit), solve its bugs.. then you have to make sure it's properly getting sorted.. sort those bugs.. Yeah, it just takes a long time for me to figure all that out.
It takes me 4-5 days on average since I'm a junior but managers expect it to only take 1-4 hours.. madness..4
You give out your e-mail address at a conference and they start abusing it for all sorts of marketing purposes..
An annoying type of colleague: the kind that refuses to cooperate and insists on doing shit their own way because they have done it that way for years and they become little crybabies whenever someone new tries to work with them.
Somehow managers accept their baby-like behavior because they've been producing output. However, like my Business Processes professor said: "Don't focus on output".
It's just annoying trying to work with these guys.
How often do you write code in a raw text editor, without any tools whatsoever (no IDE, no colors, no syntax highlighting,..)? :P
I'm doing that now.13
I hate data structures. I try to work out their algorithms in my head but they're completely counterintuitive. lol.7
Stop trying to fucking nose into my life and find out what I'm doing with it at this moment.
Aah, ooh-ooh-ooh-aah-aah-ooh-aah.. Aah-aah-aah-ooh-ooh-aah-aah..! Ooh-ooh-ooh-ooh-ooh-ooh.. Ooh-ooh-ooh-ooh-ooh-ahh.. ahh..
Warghl! -squeaky alien sound-
Worgblh! -big alien sound-
Trained in all weapons.. both human and alien..3
In reply to:
Okay, we must first establish common ground here. What do we understand about "showing"? I understand you probably mean displaying/rendering, more abstractly: "obtaining". Good, now we move on.
What's the point of a front-end? Well, in the 90's that used to be an easy answer: to share information (not even in a user-friendly way, per se). Web 2.0 comes, interaction with the website. Uh-oh, suddenly we have to start minding the user. Web 3.0 comes, ouch, now the front-end is a mini-backend. Even tougher, more leaks etc. The ARPAnet was a solution, a front-end that they had built in order to facilitate research document-sharing between universities. Later, it became the inter(national) net(work).
First there was SGML to structure the data (it's a way of making it 'pretty' in a lexicographical way) and turn it into information (which is what information is: data with added semantics) and later there was HTML to structure it even further, yet we all know that its function was not prettification, but rather structure. Later came CSS, to make it pretty. With its growing popularity, the web started to be used as a publishing device.
If we are to solely display JSON data in a pretty way, we may be limiting ourselves to the scenario of rendering pretty web pages using aesthetic languages such as CSS. We must also understand that if we are only focusing on making a website pretty with little to moderate functionality, we aren't really winning. A good website has to be a winner in all aspects, which is why frameworks came into existence, but.. lmao, let's leave that to another discussion.
So, my college notes say:
"Presentation layer: this is the UI.
In this layer you ask the middle tier for information, which gets that information from a database, which then goes back to middle tier, back to presentation. In the case of the headset, the operators can confirm an order is ready. This is essentially the presentation tier again: you're getting information from the middle tier and 'presenting it' as it were.
The presentation layer is in essence the question: how do I bring my application data to my end users in a platform-and solution-independent way?"
What's JSON? A way to transport data between the middle tier and the presentation tier. Is that what frontend development is? Displaying it in a pretty way? I don't think it is, because 'pretty' is an extra feature of obtaining and displaying data. Do we always have to display data in a pretty way? Not necessarily. We could write a front-end script (in NodeJS perhaps) that periodically fetches certain information from a middle-tier is serves a more functional role rather than a rendering one.
The prettification of data was a historical consequence of the popularity of the web (which is a front-end) (see second paragraph with link). Since the essence of a front-end is to obtain information from the back-end (with stress on obtaining), its presentation is not necessarily a defining characteristic of it, but rather an optional and solution-dependent aspect, a facet.4
- being sat at an office that didn't have chairs with proper back support. It would kill my back every day. Like sitting on a bar stool coding.
- not having access to basic resources (cafeteria, salary bonuses)
- being seriously underpaid ($200 under)
- not having an IT process pipeline (yeah, this is a huge one): no JIRA, no git, no VCS, no continuous integration, etc. I fucking spend 45% of the time fixing coding-unrelated shit.
Second company (very aggravating):
- dumb frontend bitch and privileged colleague who both kept telling me months on end to shut up and who wouldn't listen to my advice on anything, while my advice would actually help the company advance in productive ways. The key here is being told to shut up while stagnating. i.e. dead end job.
- people advancing in the company based on nepotism and favoritism, based on having tits and ass, rather than skills and independence.
- pointlessssssssss meetings where decisions are made solely based on the opinion of Mr. favorite senior dev. The rest just sits there like a bunch of sad saps and yay-nodders. Incompetent PO's who "would like to hear your input" but then when you give it, they completely dismiss you.
- pointlessssssssss monthly meetings with stakeholders, where the dev teams do nothing but clash and act like pussies in front of the PM just to get in his favor, but behind scenes continue to make the same mistakes and telling the CEO everything is fine. Goodness, how can it get more unproductive.
- completely antisocial and nepotistic 'colleagues' who won't even talk to you, let alone smile at you or be friendly. You saying good morning and them pretending you're vapor that doesn't exist. Go go company atmosphere! Especially during lunch, those are the worst times. Imagine sitting at lunch where everyone looks like you killed their dog and the rest is huddled up in little high school groups.
What else? The incessant and pointless smalltalk that makes me want to bang my head against the wall. Talking about dogs, kids, what show was on tv last night. The fuck man, do you have a brain?!
- HR bitches who think they are the shit and developers are antisocial, helpless misfits, but they work with computers and they don't even fucking know what a status bar is! The irony!
- forced socializing and stigmatization for the opposite. Imagine coming into a company and you don't say good morning. Should that be a problem? No. Instead, everyone starts dogging on you and hating you just because you didn't smile in their faces and said: hiiiiiiiiiiii how did you sleep? Did you feed your dog? Fuck you.
Elliot (Mr. Robot): "Wouldn't it be awesome if there was a mute button for life?" -boop, boop, boop, boop...- Ahh.. there.. that's much better."
- CEO's sucking up to you but when it comes to salary increase, they say shit like: "Ahhh ya know, it's kinda difficult." Yet another dead end job.2
I think the biggest bullshit about work life and beginning of a career is that at the start of your new job, colleagues and employers keep telling you that everything's gonna be fine and that things come with time and you'll learn and grow as you go on.
Not true. If you just cruise along and you don't maintain your skills, sooner or later they're going to ask you to do something you don't have the skills for, you won't be able to do it or anything remotely like it because you don't have the know-how and the result is: you get fired. I should know because I've never once not been fired; I'm up to 5 jobs now. lol
There is almost no greater example that demonstrates humans are liars.6
How many of you actually study without any sort of aiding substance such as coffee or vitamin pills? I do, for instance.
I don't use any aid but it makes it more difficult sometimes. I just eat wholesome food and work out to make my brain have enough energy to process difficult matter.35
I like making money, I just don't like the bullshit administration that goes along with it. Maintaining letters can be so annoying. Salary letters, insurance letters, bs e-mails I don't care about, bla, bla and bla.
How about: I just don't give a fuck? Yeah. I only care about the money, not about all the extra shit.
How many times have you been called an idiot for verifying the accuracy of a critical piece of information?10
Lmfao, in a book teaching Java, there's a chapter that contains a class called AddMeth to illustrate adding a method to a class.
They could have used a better name, though..4
Have you become a replacement tool doing manual and menial IT work to bridge the lack of a proper IT process and streamlining?
I've worked for such companies and it's super annoying.. companies that zip projects to Google Drive instead of using a VCS.. not even having a drawing board or proper office chairs.. not even a cafeteria.. companies using Subversion instead of Git, no project management systems nor software, no JIRA, shit written down on printed paper,.. the list goes on.
A nightmare, really. Like developing in the 90's..3
Friend: "Heyyy, I want a custom IT solution. Can you make it for me?"
Me: "Okay sure."
Friend: "Heyyy I don't want the program to do it for me, I want to learn it myself."
Me: "What the fuck.. sigh."
I ended up giving them some third-party boilerplate solution and now they're happy. Peasants..1
I'm sure every tech can relate when I say: "Do not! Interrupt! My weekend! With fucking! Tech issues! Thank you!".2
I hate it when non-devs (HR, Customer Services,..) treat developers as if they're some type of 'weird non-humans'.
Whatever gives them that pretentious right to just label people like that? There are developers with emotions and humanity too!13
lol @ doing stand-ups for the sake of stand-ups. I used to work for a company that vigorously applied them. Bro, I don't care about your development progress. You're wasting my time with your bla bla. Bunch of people just standing there rattling out their daily progress.. but no one really caring. Not useful.
I really hate being treated like a junior noob based on years of experience and timidity.
It's not because I don't express myself often that I know nothing. It's not because I haven't been working for long that I don't know sh*t.
Learning Spring is like learning Tekkit for Minecraft; it's just a whole other new confusing terminology with alien concepts. You have to get into it once to understand it.
Did you become specialized in a different field than you originally aimed for and would you like to change that in the future?
For example, in my case, I did. I wanted to be a purely Front-End developer. I entered the business as a top-tier helpdesk agent, then started out as a back-end programmer and then I was hired again as a back-end programmer.
Even though I had constantly been looking for front-end opportunities, I've ended up in back-end because the front-end positions were apparently put away for those who already had tons of previous experience while I had none.
Perhaps someday I will pick up the thread again and become a Front-End developer. Who knows - only I do, for a part. I still have tons to learn. Build your own future!11
I'm sure I speak for a lot of us when I say: LET ME HAVE A LIFE!!!
Management treating us like candy machines, wanting more and more features, learn this, learn that, learn complex material. HEY I'D LIKE TO ENJOY MY TIME AFTER WORK YA KNOW.