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 - "it's ours!"
-
Today the inconceivable happened at the office. A rather attractive female colleague of ours asked if anybody could help her with a Java related issue.
Of course the majority of guys were more than willing to help.
A victor finally emerged. He went on to claim his prize by helping the fair maiden.
After a few seconds..."This is not Java. It's javascript'
I shit you not we just exploded in laughter 😂7 -
"Why we can't install SilverLight on Windows 10?"
"Because Windows drop support for it in the 2015? And SilverLight is a crappy software?"
"But we have a HUGE software who use it!!!! We kneed to REBUILD SilverLight!!!"
And now we can't get the GPS of all ours boats because the "beautifull software" is only for SilverLight and nobody can update the software because it's outsource "somewhere over the rainbow" or something like this...9 -
Dev Badass Rant
There are two occasions really:
1) For our C++ project in the third semester, we had to build any kind of C++ application. Guys in team of 4-5 built record keeping systems and calculators and one even made a Tic-Tack-Toe app. My friend and I, just the two of us, made a simple program that plays Rock Paper Scissors with you. With the power od OpenCV, it used the camera to track your hand movement, predicts your next move using contours, and displays the winning move as the computer's move.
For example, if you play Rock, the computer would predict that you were gonna play rock and display paper as it's move. It wasn't perfect, but it was ours, right from scratch. When it worked at the presentation, I was swell with pride. 😂
2) I was interested in game dev so I started Unity. The first tutorial in Unity you find is the web series by Unity about rolling a ball. You simply make a platform and control the ball with your keyboard and the camera follows your ball. You also make pick ups and get points based on that. So I started there, finished the tutorial, added a few walls, made edible and non edible pick ups, dimmed the entire scene, adjusted the camera angles, transferred controls to mobile gyroscope and added a few other things and voila! MazeBall was born. It has only one level and I thought it was pretty shit.
I decided to show it to a friend and when I showed it to my mate (the one who I worked with in the C++ project), my other classmates saw it and were impressed. Like so impressed a couple of them transferred it to their phone and took home with them. 😂 Was inspired to improve.4 -
Recently, one of our passwords was accidently published on a public page for a few minutes before it was noticed and removed. Unfortunately, this password opens nearly every locked account so it's a pretty big deal.
Management was informed of this mistake and told that we should change the passwords as well as implement a few other protocols to make sure this doesn't happen again including things like unique passwords, more secure passwords, using a password manager, etc.
Their response? It wasn't online long, probably no one saw it. There will be no changes in how we handle ours or our clients' secure passwords.6 -
Woooo! Closed on a new home today, and it's ours. 2500 Sq ft, 4 bedrooms, huge farm kitchen. Five minute walk from a trailhead for a trail that runs along the shore of Lewisville Lake. Same commute to work. I'm happy.6
-
there is another team in our company that has its site in the US. we haven't been working with them for very long, but we do have some common topics on which we work loosely together and exchange some information from time to time. i have met the guys only once in person when they visited Germany.
PM asked one of the devs of this team if he could move to another time zone, so it would be easier for us in Europe to arrange meetings with him.
move to another timezone. within the US. to the other side of the country where there's noone he knows. also, no site of ours.
only so it's easier for PM to arrange fucking meetings with him.
can you believe that? i cringed so hard when PM told me about that. (of course the guy refused, shocked pikachu)
and when he thought aloud that maybe he should ask the guy to move to Germany, i told him that the colleague wouldn't do that and that this was a terrible idea. he was really surprised and asked "hmm, you think?"
dafuq, hell yeah i think?!3 -
My first job was actually nontechnical - I was 18 years old and sold premium office furniture for a small store in Munich.
I did code in my free time though (PHP/JS mostly, had a litte browsergame back then - those were the days), so when my boss approached me and asked me whether I liked to take over a coding project, I agreed to the idea.
Little did I know at the time: I was supposed to work with a web agency the boss had contracted to build their online shop. Only that he had no plan or anything, he basically told them "build me an online shop like abc(a major competitor of ours at the time)"
He employed another sales lady who was supposed to manage the shop (that didn't exist yet). In the end, I think 80% of her job was to keep me from killing my boss.
As you can imagine, with this huuuuge amout of planning and these exact visions of what was supposed to be, things went south fast and far. So far that I could visit my fellow flightless birds down in the Penguin's republic of Antarctica and still need to go further.
Well... When my boss started suing the web agency, I was... ahem, asked to take over. Dumb as I was, I did - I was a PHP kid and thought that Magento, being written in PHP, would be easy to master. If you know Magento, you know that was maybe the wrongest thing I ever said.
Fast forward 3 very exhausting months, the thing was online. Not all of it worked yet, but it was online and fairly secure.
I did next to everything myself, administrating the CentOS box the shop was running on, its (own) e-mail server, the web server, all the coding required for the shop (can you spell 12 hour day for 8 hour pay?)
3 further months later, my life basically was a wreck, I dragged myself to work, the only thing I looked forward being the motorcycle ride home. The system worked though.
Mind you, I was still, at the time, working with three major customers, doing deskside support and some admin (Win Server 2008R2 at the time) - because, to quote my boss, "We could not afford a full time developer and we don't need one".
I think i stopped coding in my free time, the one hobby I used to love more than anything on the world, somewhere Decemerish 2012. I dropped out of the open source projects I was in, quit working on my browser game and let everything slide.
I didn't even care to renew the domains and servers for it, I just let it die without notice.
The little free time I had, I spent playing video games and getting drunk/high.
December 2013, 1.5 years on the job, I reached my breaking point and just left, called in sick at least a week per month because I just could not see this fucking place anymore.
I looked for another job outside of ALL of what I did before. No more Magento, no more sales, no more PHP. I didn't have to look for long, despite what I thought of my skills.
In February 2014, I told my boss that I quit. It was still seven months until my new job started, but I wanted him to know early so we could migrate and find a replacement.
The search for said replacement started in June 2014. I had considerably less work in the months before, looks like he got the hint.
In August 2014, my replacement arrived and I got him started.
I found a job, which I am still in, and still happy about after almost half a decade, at a local, medium sized ISP as a software dev and IT security guy. Got a proper training with a certificate and everything now.
My replacement lasted two months, he was external and never really did his job - the site, which until I had quit, had a total of 3 days downtime for 3 YEARS (they were the hoster's fault, not mine), was down for an entire month and he could not even tell why.
HIS followup was kicked after taking two weeks to familiarize himself with the project. Well, I think that two weeks is not even barely enough to familiarize yourself with nearly three years of work, but my boss gave him two days.
In 2016, the shop was replaced with another one. Different shop system, different OS, different CI. I don't know why and I can't say I give a damn.
Almost all the people that worked at the company back with me have left for greener pastures, taking their customers (and revenue) with them.
As for my boss' comments, instructions and lines: THAT might not be safe for work. Or kids. Or humans in general. And there wouldn't be much left if you put it through a language filter...
Moral of the story: No, it's not a bad thing to leave a place if you're mistreated there. Don't mistake loyalty with stupidity!
And, to quote one of my favourite Bands: "Nothing matters when the pain is all but gone" (Tragedy + Time by Rise Against).8 -
The other day, I customer of ours asked me to try to improve the performance of an application of his in a particular method. The method in question taking more than 5 minutes.
I took a look at what it did in the profiler, and it shocked me. More than 100k selects to the database, to retrieve 116 records...
I took a look at the code... Scores of selects in nested loops inside other nested loops inside of... That seemed normal to them...
At the end after we improved it's performance it took 3 seconds...
What shocks me the most is that the customer is a developer himself, really knowledgeable and has an order of magnitude more experience than I do. Am I too anti "worthless database round-trips"? Is that normal? :S1 -
Did a bunch more cowboy coding today as I call it (coding in vi on production). Gather 'round kiddies, uncle Logan's got a story fer ya…
First things first, disclaimer: I'm no sysadmin. I respect sysadmins and the work they do, but I'm the first to admit my strengths definitely lie more in writing programs rather than running servers.
Anyhow, I recently inherited someone else's codebase (the story of my profession career, but I digress) and let me tell you this thing has amateur hour written all over it. It's written in PHP and JavaScript by a self-taught programmer who apparently discovered procedural programming and decided there was nothing left to learn and stopped there (no disrespect to self-taught programmers).
I could rant for days about the various problems this codebase has, but today I have a very specific story to tell. A story about errors and logs.
And it all started when I noticed the disk space on our server was gradually decreasing.
So today I logged onto our API server (Ubuntu running Apache/PHP) and did a df -h to check the disk space, and was surprised to see that it had noticeably decreased since the last time I'd checked when everything was running smoothly. But seeing as this server does not store any persistent customer data (we have a separate db server) and purely hosts the stateless API, it should NOT be consuming disk space over time at all.
The only thing I could think of was the logs, but the logs were very quiet, just the odd benign message that was fully expected. Just to be sure I did an ls -Sh to check the size of the logs, and while some of them were a little big, nothing over a few megs. Nothing to account for gigabytes of disk space gradually disappearing.
What could it be? I wondered.
cd ../..
du . | sort --sort=numeric
What's this? 2671132 K in some log folder buried in the api source code? I cd into it and it turns out there are separate PHP log files in there, split up by customer, so that each customer of ours (we have 120) has their own respective error log! (Why??)
Armed with this newfound piece of (still rather unbelievable) evidence I perform a mad scramble to search the codebase for where this extra logging is happening and sure enough I find a custom PHP error handler that is capturing (most) errors and redirecting them to these individualized log files.
Conveniently enough, not ALL errors were being absorbed though, so I still knew the main error_log was working (and any time I explicitly error_logged it would go there, so I was none the wiser that this other error-catching was even happening).
Needless to say I removed the code as quickly as I found it, tail -f'd the error_log and to my dismay it was being absolutely flooded with syntax errors, runtime PHP exceptions, warnings galore, and all sorts of other things.
My jaw almost hit the floor. I've been with this company for 6 months and had no idea these errors were even happening!
The sad thing was how easy to fix all the errors ended up being. Most of them were "undefined index" errors that could have been completely avoided with a simple isset() check, but instead ended up throwing an exception, nullifying any code that came after it.
Anyway kids, the moral of the story is don't split up your log files. It makes absolutely no sense and can end up obscuring easily fixable bugs for half a year or more!
Happy coding.6 -
I miss old times rants...So i guess, here it goes mine:
Tomorrow is the day of the first demo to our client of a "forward-looking project" which is totally fucked up, because our "Technical Quality Assurance" - basically a developer from the '90-s, who gained the position by "he is a good guy from my last company where we worked together on sum old legacy project...".
He fucked up our marvellous, loose coupling, publish/subscribe microservice architecture, which was meant to replace an old, un-maintainable enormous monolitch app. Basically we have to replace some old-ass db stored functions.
Everyone was on our side, even the sysadmins were on our side, and he just walked in the conversation, and said: No, i don't like it, 'cause it's not clear how it would even work... Make it an RPC without loose coupling with the good-old common lib pattern, which made it now (it's the 4th 2 week/sprint, and it is a dependency hell). I could go on day and night about his "awesome ideas", and all the lovely e-mails and pull request comments... But back to business
So tomorrow is the demo. The client side project manager accidentally invited EVERYONE to this, even fucking CIO, legal department, all the designers... so yeah... pretty nice couple of swallowed company...
Today was a day, when my lead colleague just simply stayed home, to be more productive, our companys project manager had to work on other prjects, and can't help, and all the 3 other prject members were thinking it is important to interrupt me frequently...
I have to install our projects which is not even had a heart beat... not even on developer machines. Ok it is not a reeeeaaally big thing, but it is 6 MS from which 2 not even building because of tight coupling fucktard bitch..., But ok, i mean, i do my best, and make it work for the first time ever... I worked like 10 ours, just on the first fucking app to build, and deploy, run on the server, connect to db and rabbit mq... 10 FUCKING HOURS!!! (sorry, i mean) and it all was about 1, i mean ONE FUCKING LINE!
Let me explain: spring boot amqp with SSL was never tested before this time. I searched everything i could tought about, what could cause "Connection reset"... Yeah... not so helpful error message... I even have to "hack" into the demo server to test the keystore-truststore at localhost... and all the fucking configs, user names, urls, everything was correct... But one fucking line was missing...
EXCEPT ONE FUCKING LINE:
spring.rabbitmq.ssl.enabled=false # Whether to enable SSL support.
This little bitch took me 6 hours to figure out...so please guys, learn from my fault and check the spring boot appendix for default application properties, if everything is correct, but it is not working...
And of course, if you want SSL then ENABLE it...
spring.rabbitmq.ssl.enabled=true
BTW i really miss those old rants from angry devs, and i hope someone will smile on my fucking torturerant marshall_mathers worklife sugar-free_tateless_cake_decorant_figure_boss missolddays oldtimes_rants5 -
At the first company I worked for out of college, the CEO was a bit like a child. Whenever he came up with a new feature he wanted to add to the product, it had to be done asap otherwise we were going to "miss the boat." Every single time.
So rewind to a few years ago. It's a normal day at work and then suddenly my team lead and the CEO call my team into the conference room. The CEO starts telling us about this industry conference (we were in online dating) that was happening and this flashy new company dating company was going to be showing off this awesome search feature.
Naturally, our CEO concocted a Hail Mary plan of how our company was going to upstage this company and get all of the press to write about us instead. Basically, the "plan" was for us to build a brand new search feature of our own, in the week before the conference, and then he stated that the press would "have to write about us because ours will be better."
Everyone on my team knew it was ridiculous but we were pretty young and naive so we busted our asses to get this search feature out the door in the short week. The Friday before we stayed until like 2 AM. It was a little bit fun because the people on my team were cool, but the whole situation was absurd and no one, except the CEO, thought this had any chance of working.
Annnnddd in the end we didn't get an ounce of press, the search feature was pulled from our site, and the "awesome" company that we were so worried about getting all the press is out of business. But hey, we did get it done!1 -
I once had a PM who would consistently ask us to fix one off "bugs" (read little design tweaks). He wouldn't even bother to write them down anywhere. He once came over and asked why we hadn't fixed one of his bugs. We had no idea what he was talking about. According to him, we were supposed to organize and prioritize according to his whim. He never logged into our task management system.
When it finally came time to sell off our work to some of the business owners, we showed some of the "bug fixes" we did because that's all we ever heard we were supposed to do. The business owners were mad that we hadn't done anything they had asked us to do. PM throws us under the bus saying that we didn't know how to do our jobs and that we never listened to him. I was so glad when he moved to be lead of the QA department. Then I wasn't so glad.
He would have bug quotas that his team would have to meet. He pitted the entire QA team against all of the devs saying things like, "All the devs suck at coding. It's our job to save the company and the world from their buggy software." He got the only good QA guy fired because he faked a bunch of documents stating that they had had performance reviews and no improvement was made (these meeting never actually took place), and that he hadn't been meeting his big quotas. He was outside of our department and was buddy buddy with one of the C-levels, so his word trumped ours.
Then one glorious day, after I had already left the company, his department was absolved into the technology group. That same day was the day he was fired.
I kind of pity him. I didn't know if he had a family, but how can a man such as that support his family? Perhaps he doesn't have a good relationship with his wife and that's why he sucked at his job?1 -
One of our customers asked us (a while back) to create a nice interface for their label printer (preferably integrated in their web cms)
So we started developing and after two weeks (we were almost done) they canceled the request, payed for the worked ours and said that another company was willing to do it faster (even though we were almost done)
So that was about half a year ago, meanwhile I've migrated to Ubuntu
Today I heard we have to do it again because the other 'faster' company wasn't faster, and didn't live up to the expectations
I do not have the code anymore... My colleagues also do not have the code anymore... It was removed to keep our coded clean, not sure if it's on git (the guy who workers on the part that's has a repo doesn't always commits...)
I've worked on on a standard node js script (which I didn't create a repo for because the project was canceled)
... Amazing4 -
When I wrote my first algorithm that learns...
So in order to on board our customers onto our software we have to link the product on their data base to the products on ours. This seems easy enough but when you actually start looking at their data you find it's a fuck up of duplication's, bad naming conventions and only 10% or so have distinct identifiers like a suppler code,model no or barcode. After a week or 2 they find they can't do it and ask for our help and we take over. On average it took 2 of our staff 1-2 weeks to complete the task manually searching one record of theirs against our db at a time. This was a big problem since we only had enough resources to on board 2-4 customers a month meaning slow growth.
I realized when looking at different customers databases that although the data was badly captured - it was consistently badly captured similar to how crap file names will usually contain the letters 'asd' because its typed with the left hand.
I then wrote an algorithm that fuzzy matched against our data and the past matches of other customers data creating a ranking algorithm similar to google page search. After auto matching the majority of results the top 10 ranked search results for each product on their db is shown to a human 1 at a time and they either click the the correct result or select "no match" and repeat until it is done at which point the algo will include the captured data in ranking future results.
It now takes a single staff member 1-2 hours to fully on board a customer with 10-15k products and will continue to get faster and adapt to changes in language and naming conventions. Making it learn wasn't really my intention at the time and more a side effect of what I was trying to achieve. Completely blew my mind. -
I have a serious question.
I particularly address Italian ranters.
It's about time to decide what faculty/"subject" I should go to, and I'm uncertain between "Informatics" and "Informatic Engineering".
Does someone know what the differences between the two are, and, given that I want to do as much programming (and so practical stuff instead of theorical stuff) as possible, which of these two faculties should suit me best?
If you're not from Italy, but from other countries, of course that shouldn't stop you from posting a response, if you want to.
How do Universities work there?
Are they like ours, in Italy, or does it work differently?
Thanks for your patience. 💙9 -
So, I work in a game development studio, right?
We're trying to launch the title on as many platforms as reasonable, because as a social VR app we're kinda rowing upstream.
So far, Steam and Oculus have been fairly reasonable, if oddly broken and inconsistent.
Enter store 3.
Basically no in-game transaction support (our asking prompted them to *start* developing it. No, it's not very complete). No patch-update system (You want an update? Gotta download the whole fsckin' thing!). No beta-testing functionality for most of their stuff ("Just write the code like the example, it will work, trust us!"). No tools besides the buggy SDK (Wanna upload that new build? Say hello to this page in your web browser!).
So, in other words: Fun.
We've been trying to get actively launched for two months now. Keep in mind that the build has been up on Steam and Oculus for over a year and half a year (respectively), so the actual binary functionality is, presumably fine.
The best feedback we get back tends to be "Well, when we click the Launch button it crashes, so fail."
Meanwhile we're going back and forth, dealing with other-side-of-the-world timezone lag, trying to figure out what is so different from their machines as ours. Eventually we get them to start sending logs (and no, Windows Event logs are not sufficient for GAMES, where did you even get that idea????) except the logs indicate that the program is getting killed so terribly that the engine's built-in crash handler can't even kick in to generate memory dumps or even know it died.
All this boils down to today, where I get a screenshot of their latest attempt.
I just can't even right now.5 -
I'm currently the only dev that works with a client's dev team. That's not really how we usually work, usually it's a whole team of ours.
Three aspects why this sucks:
1) the client's dev team is made up of juniors and junior to intermediate devs. All of them are new to scrum. I therefore have to constantly support (dev & agile workflow), check all the PRs and have to think of everything in Refinement meetings.
2) the client's based in another timezone and the PO is super busy because we're the only agile team in their company. Therefore this is going to be the third Friday in a row where I have meetings until 6pm.
3) I also have a specific time frame I have to start working for my company, so I constantly work extra hours due to the time difference.
I'm just tired.4 -
PMs... be wary working for sales people. They are are really good at getting you to say "Yes" to a simple project, then piling on new scope as an "upsell".
It's a skill in their domain. It's a trap in ours.2 -
Me and my friends decided to start a film company, much like roosterteeth. Throughout high school we had a talented group, actors, musicians, writers etc and those of us behind the scenes editing and shooting footage, graphic design and web development. My best friends passion is film, he's a good director and editor and wanted to start this company and was blessed enough to have a group of friends with all of these talents.
Naturally I was the teams web developer/designer.
Well this morning he texts me saying he's sending an old friend of ours my way to help on the website. My first thought is "why?". I code alone, I've never made a website as a team, that just seems like a mess.
Well the friend of ours texts me shortly after saying he was LEARNING to code and wanted to know if he could be in the dev team. I am the dev team. It's not a group to be joined. I don't want my first team experience to be one where I'll have to be teaching along the way, bc I may as well do it alone at that point. I haven't responded to either person yet as I was waiting to share with devRant 😂3 -
After one year working part time (10%) as new consultant in the company, the consultant calls the technical director in the evening and asks: "hey, how much do you think it will cost to rewrite a SaaS platform somewhat similar to ours from scratch in outsourcing and scaling from the actual 500 customers to 500 thousands? I need to know by tomorrow morning, as we have a pitch with investors. Do you think it's ok to ask for 500K$? Actually, I can only ask for 500K$."3
-
Today it took me *five* commits and nearly 2 hours to tidy up a module before doing a tiny 5-minute change.
I could have just done my change but that thing was so messy, I first had to straighten things up.
It's not that I didn't expect that, the module was mainly done by my dearest co-worker who's code usually causes me anaphylactic shocks.
But I'm always amazed how hard it can be to follow a style guide, and ours is really small anyway.2 -
It seems that my barometer for whether I would stay long in a company is roughly 1.5 years. Because apparently that's how long it takes to gauge if:
(a) The work I'm doing is fulfilling or self-satisfying
(b) My colleagues make work a fun and challenging experience
(c) My bosses are people I can be proud to work for.
Right now, the tally thus far:
(a) The work is half crap, supporting old code (fuck Swig and Architect, by the way) or fixing bugs on old projects. New projects are always mismanaged, and I mean ALWAYS (let's do Agile and create tickets but hey the requirements are still in progress so do start anyway and we'll file everything as bug tickets until they're done)
(b) I'm sure it's an effect of going remote working for the last few months, but I'm feeling detached from my team. It's fine I guess.
(c) My manager is okay, he's a good guy who listens and is also technical so we get along. But his boss (who oversees several teams. including ours) is a total prick who loves to insult people at their expense as a joke. He knows nobody's gonna talk smack back so he just does it without repercussions.
I'll probably see if I can move around internally to a different division since the pandemic makes it difficult to find work externally. I'm grateful I have a job, but I shouldn't have to feel like I owe the company for that at the cost of my personal happiness.
Just gotta #survive2020 I suppose.