Details
-
SkillsFull stack dev who prefer to work on the front end side of the force or IOT. Nowadays my stack is js / python. I love Vue. If you touch my Vue I get aggressive :D
-
LocationBudapest
-
Github
Joined devRant on 2/7/2017
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
-
Why would someone in their right mind change a piece of code that was working fine (and it wasn't a complete mumbo jumbo in styling, logic, transparency, was in line with how the project was coded etc..) to use dapper just to call a stored procedure?! Dafaq is wrong with people!?
Or is it just me & I'm overreactig again?!
I hate when people add more stuff to projects that are already overbloated with fw/techologies to do something so trivial.. like adding 6827646 js fw so you can use one function in each (or are simply still there because they didn't know how to use it and left it in project) which could easily be achieved with our own fw we use...wtf?! O.o
// me cringing, cussing etc..4 -
Hi everyone,
I am working in a company where the pay is not that great but i am learning newer technologies here. And now I am getting a offer from a company where the pay will be decent but not so sure that I will learn that much.
Need advise which one should i choose.7 -
Girlfriend (art student): “You’re in CS. Why don’t you use Windows? Macs are terrible for programming.”
Me: “macOS is better for doing command line compilation and shit because it supports Unix terminal commands and stuff with a reliable OS that’s better-supported than most Linux OSes. I also have Windows on my laptop too, for Visual Studio.”
Girlfriend: “Only like 1% of people use command line stuff. Windows is better for programming. I’ve seen a lot of CS majors use Windows.”
Me: “Uh. You watch me use my computer every day. The stuff I do in Terminal takes forever on Windows.”
Girlfriend: “Yeah, but Windows is just better for programming though.”
Help.46 -
Today's the day I realized my branch was better off if I just restarted from master and cherry-pick the commits I liked from the old one. This is what I get for the branch hanging around so long.
Lesson of the day: Merge early, and merge often. -
My mother lives and works overseas, and she'd complain about her IT department all the time.
Wish I could get work permit to work there, but I'd have to serve in 'their' military for 2 years...
Yeah, totally makes sense. Nope.5 -
In previous company I was a backend developer. All the frontend ones were on vacation so it was up me to redo the whole frontend because of design chance. So i thought it couldn't be that bad. Little did i know was that designs were just jpg files with no info about margins or font sizes or anything really and everything was supposed to be pixel perfect. Fuck. That. Place.
-
In a meeting, we made some pretty major adjustments to a dev server. We broke it. Under pressure, I cracked and I randomly forgot the syntax for a sql update statement that might’ve at least got it back semi-online. To be fair, it’s been several years since I’ve needed any sql. Thank goodness I grabbed a snapshot as soon as I realized things were about to get edited. Saved. 😁2
-
So I’m looking at a senior dev role, and wondering what kind of coding challenges to expect, what have some of you more senior devs had to face in the past?9
-
http://mindprod.com/jgloss/...
Skill in writing unmaintainable code
Chapter : The art of naming variables and methods
- Buy a copy of a baby naming book and you’ll never be at a loss for variable names. Fred is a wonderful name and easy to type. If you’re looking for easy-to-type variable names, try adsf or aoeu
- By misspelling in some function and variable names and spelling it correctly in others (such as SetPintleOpening SetPintalClosing) we effectively negate the use of grep or IDE search techniques.
- Use acronyms to keep the code terse. Real men never define acronyms; they understand them genetically.
- Randomly capitalize the first letter of a syllable in the middle of a word. For example: ComputeRasterHistoGram().
- Use accented characters on variable names.
- Randomly intersperse two languages (human or computer). If your boss insists you use his language, tell him you can organise your thoughts better in your own language, or, if that does not work, allege linguistic discrimination and threaten to sue your employers for a vast sum.
and many others :D -
I had an interview with a company that works offshore (works for a big silicon valley company) for an internship program. I liked their bosses vision and how he treats his coworkers. After 1 hour technical interview I asked how much they pay for internship and they told me they are not paying anything. And they said hey we are teaching you how things works. Wait... What? Atleast you can pay my transport and food fees. Fuck you and fuck your company. If you don't pay me a single fucking penny, I am not working with you. There is local laws to pay me some money. If you don't care about laws, I wont care about your fucking company. Burn in hell.5
-
Worst exp. on a collab/group project?
Had a few, here is one.
Worked with a dev team (of two devs) in Norway to begin collaboration on providing a portal into our system (placing orders, retrieving customer info, inventory control, etc)
They spoke very good English, but motivation was the problem. Start the day around 10:00AM...take a two hour lunch...ended the day at, if I was lucky, 4:00PM (relative to Norway time). Response time to questions took days, sometimes weeks. We used Skype, which helped, but everything was "Yea...I'll do that tomorrow...waiting on X....I have a wedding to go to, so I'll finish my part next week."
I didn't care so much, I had other projects to do, but the stakeholders pounded me almost everyday demanding a progress report (why aren't you done yet...etc..etc.)
The badgering got so bad I told the project owner (a VP) if he wanted this project done by the end of the year, the company would have to fly me to Norway so I personally push things along.
When real money was on the line, he decided patience was warranted.
A 3 month project turned into 9, and during a phone meeting with the CEO in December
O: "Thanks guys, this project is going great. We'll talk again in February. Bye."
PM: "Whoa...what! February!"
<sounding puzzled>
O: "Um..yes? It's Christmas time. Don't you Americans take off for Christmas?"
PM: "Yes, but not until Christmas. Its only December 12th. Your taking the whole month of December and January for Christmas?"
O:"Yes, of course. You Americans work too hard. You should come over here and see how we celebrate. Takes about a month so we can ease back into the flow of things."
<Jack is the VP>
PM: "Jack wanted this project completed by the end of the year, that is what everyone agreed to."
O:"Yes, I suppose, but my plane is waiting on me. Not to worry, everything will be fine."
<ceo hangs up>
PM: "Oh shit..oh shit..oh shit. What are you going to do!?"
Me: "Me!?..not a darn thing. Better go talk with Jeff."
<Jeff is the VP>
J: "This is unacceptable. You promised this project would only take a few months. I told you there would be consequences for not meeting the deadline."
PM:"But..but...its not our fault."
J: "I don't care about fault. I care about responsibility. I've never had to fire anyone for not meeting a deadline, but .."
Me: "Jeff, they are in Norway and no one is working this project for the next two months. You've known for months about them dragging their asses on this project. We're ready to go. Services have been tested and deployed. Accounting has all the payment routing ready. Only piece missing is theirs."
J: "Oh. OK. Great job guys. I guess we'll delay this project until February."
<leave the office>
PM: "Holy shit I'm glad you were there. I thought I was fired."
Me: "Yea, and that prick would have done it not giving a crap that it's Christmas."
<fast forward to Feb>
O: "Our service provider fell through, so I'm hosting with another company. You guys know PHP? Perl? I don't know what they called it, but it sounded so cool I bought the company."
PM: "You bought what? Are we still working with Z and B?"
O:"Yea, sort of. How's your German? New guy only speaks German."
PM: "Um, uh... no one here speaks German"
O:"Not to worry, I speak German, French, and Italian. I'll be your translator."
PM: "What? French and Italian?"
O: "On my trip to France I connected with a importer who then got me in touch with international shipper in Italy. I flew over there and met a couple really smart guys than can help us out. My new guy only speaks German, J only speaks French, and R speaks Italian, Russian, and a little English. Not to worry, I'm full time on this project. You have my full attention."
We believe the CEO has/had some serious mental issues, including some ADD. He bailed within the first month (took another vacation to Sweden to do some fishing) and left me using Google Translate to coordinate the project. Luckily, by the end, the Norwegian company hired a contractor from England who spoke German and hobbled together the final integration.3 -
Client: why hasnt anything been done for the new site?
Me: because you never paid for the last one thats been put into production
Client: yeah but that was a smaller simple site. I need this one up and done already
Me: it'll be worked on when I get paid for my previously worked time for you.
Client: but that was a month ago. I don't understand why you are asking for payment now
Me: because you never paid me for last months work!!
Client: but its may now
Me: holy shit, -clients name-, I know very well what month it is and dont need a lesson. I also know better than to work for free. I have bills to pay just like you and everyone else so until you have paid the last invoice, I'm not lifting a finger for you. That includes answering your calls
Client: oh well why didnt you just say that to begin with
Motherfucking fuck people are horrid and dumb and make me violent6 -
I’m a full-stack Dev, but my job description restricts me to backend - app logic and databases - but the frontend Dev makes crappy markup templates and I have to keep closing unclosed tags and replacing ID css selectors with classes.7
-
I had a coworker that was a real asshole. I noticed that often, during git merges, he removed part of the code I wrote.
So I had to spend a lot of time copying and pasting my code from git history in order to restore it.
I complained about that but he answered it happened by mistake. In reality that happened so often that he had to done it deliberately.
Btw, I did a little revenge. One day I discovered he didn't feel very comfortable using recursion. Thereafter, every time I needed a small loop I created a recursive function doing the same thing.
Fortunately, after some months I found a better job. I hope he is still debugging that code.4 -
Ya go ahead. Touch my screen. The next thing I would do is get that same fingerprint from my screen, unlock your phone and fucking factory reset it. Or worse, message all the girls in your contact that you have a tiny dick. Go ahead. I dare you to touch my screen.8
-
Ignore the official start/finish times. Instead, sync your office ours to that of someone in your team you respect.4
-
other team: accidentally deploys app to staging with incorrect config file
app: gets 401 response from our API due to bad credentials
other team: opens ticket claiming our API is broken and whining that it's holding up their release
me: (⌐■_■) -
I love TDD.
It's so relaxing to know that your fix didn't fuck up anything else when the tests pass. -
I inherited some code today. I am in the process of reworking it to drop into my framework so I can use it with our product. I am seeing this throughout the code...
try:
\do something\
except:
pass
Ahem... HANDLE YOUR DAMN EXCEPTIONS!!! DON'T JUST PASS THEM INTO THE BLACK HOLE OF NOTHINGNESS! FFS!!! Using pass like this means "Fuck it. I don't care if this fails and I want NOTHING to tell management when it does. I want to blindly look into their frustrated eyes and say ..duhh, I don't know why it failed... Fuck troubleshooting. You know what, this job isn't meant for me anyways." My outer voice is politely saying "There is a better way to do this. Please allow me to show you." Meanwhile my inner voice is flipping tables and clubbing baby seals. /rant -
"Don't try to memorize everything, after you've coded for a while you'll start remembering it, even the best devs Google shit ALL THE TIME."3
-
TL;DR: A new "process" for collaboration between teams was created in order to stonewall requests from my team.
A couple months ago, we created a new Dev team that specializes in writing internal tools. This team was staffed with internal developers, and got a separate manager. The whole point of this team was to collaborate with my dev team so we can both help each other develop tools that the company needs.
One of the developers that was on my team went over to this team while he and I were still working on a big application. For a few weeks, he still worked on this application as he normally would, and we'd sit with each other and work through features together whenever we needed a fresh set of eyes.
Well, eventually his new team got protective of him and created a new "process" for our teams to request assistance from one another. So now instead of just popping over to someone's desk to ask a quick question, you have to send an email to the team and request that you can borrow that particular developer for a question, and then the entire team sits down and discusses whether or not they're going to allow that person to answer your question. Then after a week of discussion, if they decide to allow it, they schedule a meeting for a week later, in which you will get the question answered.
So instead of just spending 2 minutes to ask and answer the question, you have to spend weeks in order to request assistance, and then schedule a meeting.
It's ridiculous, and it's all because his team got protective that he was working with another Dev team. Dev teams collaborate all the time, and work together. My team is constantly helping other teams, and we don't have this ridiculous process. We get asked a question, and we answer it. Simple as that.
Last week, I sent an email for assistance in completing a feature, and didn't hear back. I talked to the Product Owner for the team, and he said "Just send an email," to which I responded that I did and hadn't got a response. He said "Oh....." I then told my boss that this is an enormous bottleneck, and he seemed surprised hearing that this is a bottleneck.
A week passed and today I still hadn't got a response, so my boss reached out to the Product Owner to push him. Finally, I got a response and they scheduled a meeting to answer my question 3 days down the road. So it's going on 2 weeks to get this simple question answered.
Normally I'd just have the other developer come over and help, but apparently they yelled at him the last time he did that.
The issue is that the process was created with the assistance of our "senior" developers, who never work with this other team in this capacity, so they just nodded and smiled and let them put this ridiculous process in place.
Like, get off your high horses. You don't "own" him, he's allowed to collaborate with other teams. This question would've taken literally 10 minutes, but because of your new "process" you've turned it into a 2 week debacle and you've effectively delayed the app launch with your pettiness.
They say that this process isn't intended to prevent us from getting assistance, and that might not have been the original intention of the Product Owner/manager, but it's very clear that the developers on the other team are taking advantage of it and using it as a big stonewall so they can beat around the bush and avoid providing assistance when it's needed.
If this becomes a trend, I'm going to schedule a meeting (which apparently they love to do,) and we're going re-work this entire process, because it's extremely counterproductive and seems to only exist in order to create red tape.3 -
Never update prod stuff on a Friday afternoon.
After the team lunch.
With cheese fondue and white wine.1 -
Why do Pokemon masters love JavaScript?
Because you gotta, try/catch them all
Haha. No laughs? Okay
*curls into a ball7 -
New to full time front end development from designing. Can you give any tips that would save my time and make life easier3