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
Search - "nike"
My university organised a series of shitty seminars and due to shortage of registration it was going to be made mandatory. Registration was a simple google form without sign in, so i wrote a python script and filled the google form with characters of Game of Thrones , Breaking bad and Narcos series. Now the seminar is cancelled.6
Found this one in Facebook 😂 This one seems quite popular and IDK if someone's posted it here yet.6
While setting up a very complex development environment I asked my colleges, why are certain configuration steps needed. They replied only "Just do it!". I see, that they may be Nike fans or deeply inspired by the Shia LaBeouf motivation speech, but I still feel like:2
Italian schools are by far the worst in the world.
I'm in a IT oriented school, where we should learn to code.
We spent the first year writing in Word and "programming" in Excel.
In the second year we started learning Visual Basic, a total waste of time.
In the third year we finally got rid of most of the useless subjects we had and started learning C++.
Sadly we had a teacher who wasn't able to properly speak and teach to students who never really programmed.
We didn't even know what a class was at the end of the year.
In the fourth year, the current one, we didn't have a teacher for the first 3 months.
Now we are learning Java, but just the basics.
Next year, the last one, we will do PHP and SQL.
Maybe also C#, the most pointless programming language in the world.
What a beautiful country.22
Any task that starts with 'just' is one of these:
1, An underestimated problem not understood well.
2, An order to complete a task without considering the points of the developer.
3, Nike advertisement.3
3 Years into coding and I still have no fucking clue on what 99% of the lines in a sample code means. And I'm already 18 Years Old... Beginning to think this line of work isn't for me T_T12
Asshole-Driven development (ADD) – Any team where the biggest jerk makes all the big decisions is asshole driven development. All wisdom, logic or process goes out the window when Mr. Asshole is in the room, doing whatever idiotic, selfish thing he thinks is best. There may rules and processes, but Mr. A breaks them and people follow anyway.
ARRRGGHHH! When the person sitting next to you produces nothing but shit and you know it's shit but, your boss doesn't because he's never written single byte of code in his life!2
>> On the phone talking to someone
>> Describe an ad taken out in the NY Times where Skechers roasted Nike for a recent fuck up in a basketball game
>> Sees same ad 15 minutes later on Instagram3
That feeling when the CEO gives a really positive pep talk about his future plans for the company but, deep inside you know your just caught up in a monkey shit fight that can never achieve the goals he’s laid out.
CK's nike deal
Eminem's diss shit and MGK killing it with Rap Devil
Wife free from work this weekend
Made a rather large project with Pharo and Seaside to see if I dig it(i did, but it ain't replacing my other tools anytime soon, shit requires reading far too much code and digging around dark corners of the net for it)
Finished 2 projects for work and got ahead of 2 others for this week.
Shit b, this is one interesting weekend indeed.
i'm fuking sick of you human ass fuks ruining everything -.-
minimalist shoe, a few years ago, meant a specific kind of shoe with certain specs
now nike and new balance, and who-ever the fuk else, just adds it as a term for their shoes and i can't find anything
go fuk yourselves and die in a fire because you tripped over your bent up toe box into lava you simple mother fukers
I'm just fed up with the industry. There are so much stupidity and so much arrogance.
My professional experience comes mainly from the frontend and I feel like it's not as bad on the backend but I'm still convinced it's not really different:
I'm now about to start my 3rd job. It's always the same. The frontend codebase is complete shit. It's not because some juniors messed up not at all. It's always some highly paid self-proclaimed full-stack developer that didn't really care somehow hacked together most of the codebase.
That person got a rediculous salary considering the actual skill and effort that went into the code, at some point things became difficult, issues started to occur and that person left. If I search for that person I find next to the worst code via gitlens on Linkedin it's somebody that has changed companies at least two times after leaving and works now for a lot of money as tech-lead at some company.
There's never any tests. At the same time the company takes pride in having decent test coverage on the backend. In the end this only results in pushing a lot of business logic to the frontend because it would just take way to long to implement it on the backend.
Most of the time I'm getting told on my first day that the code quality is really high or some bullshit.
It's always a redux app written by people, that just connect everything to the store and never tried to reflect about their use of redux.
Usually it's people, that never even considered or tried not using redux, even if it's just to learn and experiment.
At the same time you could have the most awesome projects on github but people look at your CV, sum up the years and if you invested a lot of time, worked way harder to be better than other developers with the same amount of experience, it's totally irrelevant.
At the same time all companies are just the worst crybabies about not being able to find enough developers.
HR and recruiters are generally happy to invite somebody for an interview, even if that person does not have any code available to the public, as long as that person somehow was in some way employed in the industry for a couple of years. At the same time they wouldn't even notice if you're core contributor for some major open-source product if you do not have the necessary number of years in the industry.
I'm just fed up.
By the way, I got my first real job about two years ago. Now I'm about to start my third position because my last job died because of the corona crisis. I didn't complain for some time because I didn't want to look like I'm just complaining about my own situation. With every new job I made more money, now I'm starting for the first time at a position that is labeled "lead" in the contract.
So I did okay. But I know that lots of talented people that worked hard gave up at some point and even those that made it had to deal with way too much rejection.
At the same time there are so many "senior" people in the industry, that don't care, don't even try to get better, that get a lot of money for nothing.
It's ridiculously hard to get a food in the door if you don't have any experience.
But that's not because juniors are actually useless. It's because the code written by many seniors is so low quality, that you need multiple years of experience just to deal with all the traps.
Furthermore those seniors are so busy trying to put out the fires they are responsible for to actually put time into mentoring juniors.
It's just so fucked up.3
I can't help it sounding bitter..
If you work some amount of time in tech it's unavoidable that you automatically pick up skills that help you to deal with a lot of shit. Some stuff you pick up is useful beyond those problems that shouldn't even exist in the first place but lots of things you pick up over time are about fixing or at least somehow dealing or enduring stuff that shouldn't be like that in the first place.
Fine. Let's be honest, it's just reality that this is quite helpful.
But why are there, especially in the frontend, so many devs, that confuse this with progress or actual advancement in their craft. It's not. It's something that's probably useful but you get that for free once you manage to somehow get into the industry. Those skills accumulate over time, no matter what, as long as you manage to somehow constantly keep a job.
But improving in the craft you chose isn't about somehow being able to deal with things despite everything. That's fine but I feel like the huge costs of keeping things going despite some all the atrocities that arose form not even considering there could be anything to improve on as soon as your code runs. If you receive critic in a code review, the first thing coming back is some lame excuse or even a counter attack, when you just should say thank you and if you don't agree at all, maybe you need to invest more time to understand and if there's some critic that's actually not useful or base don wrong assumptions, still keep in mind it's coming from somebody that invested time to read your code gather some thoughts about it and write them down for you review. So be aware of the investment behind every review of your code.
Especially for the frontend getting something to run is a incredibly low bar and not at all where you can tell yourself you did code.
Some hard truth from frontend developer to frontend developer:
Everybody with two months of experience is able to build mostly anything expected on the job. No matter if junior or senior.
So why aren't you looking for ways to find where your code is isn't as good as it could be.
Whatever money you earn on top of your junior colleagues should make you feel obligated to understand that you need to invest time and the necessary humbleness and awareness of your own weaknesses or knowledge gaps.
Looking at code, that compiles, runs and even provides the complete functionality of the user story and still feeling the needs do be stuff you don't know how to do it at the moment.
I feel like we've gotten to a point, where there are so few skilled developer, that have worked at a place that told them certain things matter a lot Whatever makes a Senior a Senior is to a big part about the questions you ask yourself about the code you wrote if if's running without any problems at all.
It's quite easy to implement whatever functionality for everybody across all experience levels but one of your most important responsibilities. Wherever you are considered/payed above junior level, the work that makes you a senior is about learning where you have been wrong looking back at your code matters (like everything).
Sorry but I just didn't finde a way to write this down in a more positive and optimistic manner.
And while it might be easy to think I'm just enjoying to attack (former) colleaues thing that makes me sad the most is that this is not only about us, it's also about the countless juniors, that struggle to get a food in the door.
To me it's not about talent nor do I believe that people wouldn't be able to change.
Sometimes I'm incredibly disappointed in many frontend colleagues. It's not about your skill or anything. It's a matter of having the right attitude.
It's about Looking for things you need to work in (in your code). And investing time while always staying humble enough to learn and iterate on things. It's about looking at you
Ar code and looking for things you didn't solve properly.
Never forget, whenever there's a job listing that's fording those crazy amount of work experience in years, or somebody giving up after repeatedly getting rejected it might also be on the code you write and the attitude that 's keeping you looking for things that show how awesome you are instead of investing work into understanding where you lack certain skills, invest into getting to know about the things you currently don't know yet.
If you, like me, work in a European country and gathered some years of industry experience in your CV you will be payed a good amount of money compared to many hard working professions in other industries. And don't forget, you're also getting payed significantly more than the colleagues that just started at their first job.
No reason to feel guilty but maybe you should feel like forcing yourself to look for whatever aspect of your work is the weakest.
There's so many colleagues, especially in the frontend that just suck while they could be better just by gaining awareness that there code isn't perfect.6
Web development has become nothing but a big shit show. Worse than Android development with all the packages and frameworks people keep stuffing into projects.1
Reading devRant and new job postings is leaving me with less time to write any code in this shit hole.
A degree from an accredited university and thousands of dollars spent on continuing education so some nitwit can ask me if I know a bunch of obscure syntactical features of programming language during a phone interview.2
Fuckin twats at Nike.
How the fuck did you manage to accept a non existent email as a valid email for the fuckin accounts you suckers
Last 2 runs were unable to sync so i had to logout before seeing that the account mail i used when i created the account has a misspelling which I didn’t notice until now but yet, the account was created.
Suckers i lost all my runs the last years which were about 300+ K km.1
Just finished another run. First time running in proper Nike running shoes. Before that I ran in Adidas training shoes that was designed for the gym, not outdoors.
The easiest run I’ve ever done. Same distance, same everything, even the same heart rate, but it feels like a walk in the park. I didn’t even feel thirsty.
It probably means that conditions of the exact moment your foot touches the ground somehow makes a huge difference in energy required to run. I knew that but I didn’t knew how huge its role was.6
When I first got started in web development I had to think really hard to write code to solve real world problems. It was rewarding and creative process. Nowadays most of my time is spent just trying to get bloated frameworks and plugins to play nice with one another! I hope the pendulum swings back at some point.
Is it just me or has a company run out of ideas when their keynote is more about their partners and vendors than them self? ** Caugh Apple **
(I'm an Apple user myself)