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 - "i'm back baby"
The first time I realized I wasn't as good as I thought I was when I met the smartest dev I've ever known (to this day).
I was hired to manage his team but was just immediately floored by the sheer knowledge and skills this guy displayed.
I started to wonder why they hired outside of the team instead of promoting him when I found that he just didn't mesh well with others.
He was very blunt about everything he says. Especially when it comes to code reviews. Man, he did /not/ mince words. And, of course, everyone took this as him just being an asshole.
But being an expert asshole myself, I could tell he wasn't really trying to be one and he was just quirky. He was really good and I really liked hanging out with him. I learned A LOT of things.
Can you imagine coming into a lead position, with years of experience in the role backing your confidence and then be told that your code is bad and then, systematically, very precisely, and very clearly be told why? That shit is humbling.
But it was the good kind of humbling, you know? I really liked that I had someone who could actually teach me new things.
So we hung out a lot and later on I got to meet his daughter and wife who told me that he had slight autism which is why he talked the way he did. He simply doesn't know how to talk any other way.
I explained it to the rest of the team (after getting permission) and once they understood that they started to take his criticism more seriously. He also started to learn to be less harsh with his words.
We developed some really nice friendships and our team was becoming a little family.
Year and a half later I had to leave the company for personal reasons. But before I did I convinced our boss to get him to replace me. The team was behind him now and he easily handled it like a pro.
That was 5 years ago. I moved out of the city, moved back, and got a job at another company.
Four months ago, he called me up and said he had three reasons for us to meet up.
1. He was making me god father of his new baby boy
2. That they created a new position for him at the company; VP of Engineering
3. He wanted to hang out
So we did and turns out he had a 4th reason; He had a nice job offer for me.
I'm telling this story now because I wanted to remind everyone of the lesson that every mainstream anime tells us:
Never underestimate the power of friendship.21
"devRant has changed" "I'm so fed up with this site" "Its a bunch of hate and memes, it was so much better before"
devRant is approximately the same as it was when it was just a newborn. Remember the days of semicolon jokes being unironically funny?
Look at the top rants of all time, for fucks sake. #2 ever is:
"A different error message! Finally some progress!"
Posted three years ago. That's the second most upvoted rant in history (Remember, this was a "rant" because the joke/meme category didn't exist back then), it made it's way into the app store screenshots, and was a welcome post.
Now imagine that posted today. It would probably go over okay, in fairness, but it's certainly at risk of any number of pretentious pricks complaining about how this is "devRANT not 4chan" or how they had seen the joke before and it's a shitty repost.
And sure, the repost bullshit is fair. I'm not saying that all the reposts are good content. What I'm saying is devRant has always been full of reposts - they just weren't reposts in the early days. The quality of content is the same.
There's also the common misconception that your posts need to be directly related to tech to post on devRant. This is a myth propagated by 0 IQ heathens that don't read any further than the name of the application. Your posts can be anything that isn't prohibited, like porn, spam, and, importantly, politics (commonly overlooked rule)
"All the memes are just too much". Oh you poor fucking baby, let me pour you a healthy serving of pity juice. First of all, you can turn off the memes category, and while they will still find their way to your feed, the concentration will be much lower and it will once again be bearable for your pitiful, weak little soul. Do you seriously get annoyed that severely by shitty posts that you need to leave the app altogether, or do you just want the attention of being a "cool hipster that hates on xyz"?
"This place is just filled with hate! Why can't you just respect xyz technology, it isn't actually that bad!"
This is probably the most stupid fucking thing you could possibly ejaculate from your fingers into whatever device you are using to type. Welcome to devRant, we hate on shit. That's at our core. No, xyz technology ISN'T actually that bad, you're correct. But we're here to tear it apart because it probably has frustrated us in the past. I fucking hate JS because it was my first language and it confused the shit out of me. JS is a great language. But I still talk shit about it, and that's what we're here to do.
Like seriously, I know a lot of people post stuff they're proud of here, and then they're met with "Would be great if you didn't use xyz tech", and that hurts, but holy shit, this is devRant. If you're sensitive to criticism, or even just straight up being made fun of, don't post shit that you're proud of. You won't have a good time. It's just not what we do here.
Quick interlude before the conclusion, "My girlfriend dumped me after I named a class after her. She felt I treated her like an object." is also on the first page of all-time most popular posts.
In conclusion, devRant has not changed. Reposts have been a nuisance since day 0, and just because reposts look different these days doesn't mean the quality of content has decreased in any manner. The two main sources of your frustration are the volume of low-quality posts (Mind you, not the concentration of them, but the volume of them) and your own prejudices about the platform. You're looking back with rose-tinted glasses.
Here are some tips for a more enjoyable experience:
-Make sure you have the "Hide reposts" setting ENABLED in settings. Any posts marked as repost will be hidden in your feed, pulling down the concentration of low-quality posts.
-Keep to the algo sorting method. Obviously, algo is a bot, and there's still gonna be some shit content in there anyways, but if you're in recent, you are absolutely guaranteed to see low-quality posts. It's unfiltered.
-Keep in mind that what you consider a "quality" post is not what others consider a "quality" post. Just because you don't like memes doesn't mean memes are poor content. There are people here who have never seen the bobby tables comic. And they deserve the same experience we got when discovering dev humor.
-Don't be a prick. And if you cannot help yourself, leave. Ironically, you're making the site worse by complaining about how bad the site is. You can always come back if you aren't a prick anymore. And you can leave permanently if you choose as well.
-Downvote and move on. You're not doing anything but making yourself more aggravated by leaving a shitty comment about how shitty the shitty post is.
-Think critically. Obviously optional, and I know not many people like to use their brain when a phone is suspended between their hands, but if you want a better experience, remember to use your head and not to lose it.23
> Root struggles with her ticket
> Boss struggles too
> Also: random thoughts about this job
I've been sick lately, and it's the kind of sick where I'm exhausted all day, every day (infuriatingly, except at night). While tired, I can't think, so I can't really work, but I'm during my probationary period at work, so I've still been doing my best -- which, honestly, is pretty shit right now.
My current project involves legal agreements, and changing agent authorization methods (written, telephone recording, or letting the user click a link). Each of these, and depending on the type of transaction, requires a different legal agreement. And the logic and structure surrounding these is intricate and confusing to follow. I've been struggling through this and the project's ever-expanding scope for weeks, and specifically the agreements logic for the past few days. I've felt embarrassed and guilty for making so little progress, and that (and a bunch of other things) are making me depressed.
Today, I finally gave up and asked my boss for help. We had an hour and a half call where we worked through it together (at 6pm...). Despite having written quite a bit of the code and tests, he was often saying things like "How is this not working? This doesn't make any sense." So I don't feel quite so bad now.
I knew the code was complex and sprawling and unintuitive, but seeing one of its authors struggling too was really cathartic.
On an unrelated note, I asked the most senior dev (a Macintosh Lisa dev) why everything was using strings instead of symbols (in Rails) since symbols are much faster. That got him looking into the benchmarks, and he found that symbols are about twice as fast (for his minimal test, anyway), and he suggested we switch to those. His word is gold; mine is ignorable. kind of annoying. but anyway, he further went into optimizing the lookup of a giant array of strings, and discovered bsearch. (it's a divide-and-conquer lookup). and here I am wondering why they didn't implement it that way to begin with. 🙄
I don't think I'm learning much here, except how to work with a "mature" codebase. To take a page from @Rutee07, I think "mature" here means the same as in porn: not something you ever want ot see or think about.
I mean, I'm learning other things, too, like how to delegate methods from one model to another, but I have yet to see why you would want to. Every use of it I've explored thus far has just complicated things, like delegating methods on a child of a 1:n relation to the parent. Which child? How does that work? No bloody clue! but it does, somehow, after I copy/pasted a bunch of esoteric legacy bs and fussed with it enough.
I feel like once I get a good grasp of the various payment wrappers, verification/anti-fraud integration, and per-business fraud rules I'll have learned most of what they can offer. Specifically those because I had written a baby version of them at a previous job (Hell), and was trying to architect exactly what this company already has built.
I like a few things about this company. I like my boss. I like the remote work. I like the code reviews. I like the pay. I like the office and some socializing twice a year.
But I don't like the codebase. at all. and I don't have any friends here. My boss is friendly, but he's not a friend. I feel like my last boss (both bosses) were, or could have been if I was more social. But here? I feel alone. I'm assigned work, and my boss is friendly when talking about work, but that's all he's there for. Out of the two female devs I work with, one basically just ignores me, and the other only ever talks about work in ways I can barely understand, and she's a little pushy, and just... really irritating. The "senior" devs (in quotes because they're honestly not amazing) just don't have time, which i understand. but at the same time... i don't have *anyone* to talk to. It really sucks.
I'm not happy here.
I miss my last job.
But the reason I left that one is because this job allows me to move and work remotely. I got a counter-offer from them exactly matching my current job, sans the code reviews. but we haven't moved yet. and if I leave and go back there without having moved, it'll look like i just abandoned them. and that's the last thing I want them to think.
So, I'm stuck here for awhile.
not that it's a bad thing, but i'm feeling overwhelmed and stressed. and it's just not a good fit. but maybe I'll actually start learning things. and I suppose that's also why I took the job.
So, ever onward, I guess.
It would just be nice if I could take some of the happy along with me.8
I feel like this is my first actual rant in that it's a monologue possibly showcasing my emotional baggage. No TL;DRs, so grab a coffee and enjoy.
Hey entrepreneurs and people who write about entrepreneurs, can you stop glorifying life-ending risk and workaholism? It's unhealthy and it goes to ridiculous lengths.
Going on about how you maxed out all of your credit cards, nearly lost your marriage, and still ended up rich should not be seen as inspiring. Impressive, sure, but not inspiring. In a fair world, your story should be seen as part of the self-congratulatory silicon valley gold rush culture where people actually believe that lottery tickets and following their own destiny should involve putting up their chance to ever find peace as collateral.
If you made it with hard work and at great risk, then fantastic! I'm still happy for you. I just wish your success didn't buy you the credibility that it does, because you still didn't discover a formula for success or life in general. You took a plunge and survived, which is fun to watch! It's like seeing someone skydive without a chute onto an unclaimed island and keeping that island. I'm just saying that if your story makes a whole bunch of people start skydiving without chutes because they think they'll land on their own island, then we went from hearing an amazing story to everyone just being retarded.
I'll avoid throwing the baby out with the bathwater: If you want financial health and a sense that you are not letting life pass you by, definitely maintain that course and accept risks along the way. Just be reasonable about risk!
I saw an article that started by saying "To start and support your own business, you’ll have to put your career, personal finances and even your mental health at stake." ...Yeah, maybe if you want exponential growth in 5 years because of some kind of cosmic terminal impatience or dysfunctional belief that your moral worth as a person equals the rewards you shoot for.
For people like me who are okay with using a steady paycheck to feed conservative growth and gigs for side income, putting all personal finances and mental health at stake is not an inferior life choice. I strive for flexibility in the event I lose income, and to me the ability to adapt and achieve financial independence is far more valuable than entering into all-or-nothing arrangements in the startup lottery. I won't be filthy rich or stupid famous, but that's okay. I don't need to be.
To those of you on the fence about entrepreneurship, my advice is not to focus on getting rich or famous or even feel the pressure to do so. And it's definitely not to take more risk than necessary. Ask real questions about what lifestyle would make you happy. If it's having a 9000 foot square house, a pool and worldwide admiration, then fine, make the leap. But if you think you're SUPPOSED to have the huge house and worldwide admiration, then I'm telling you that you don't. You are just as important and valuable as a person even while millions salivate over Elon Musk and walk around with inflated aspirations.
And if it helps, good budgeting, wise investments and careful risk management can still get you ahead on lower salaries. Someone making $30k a year but is cautious about savings and staying out of debt can end up just as free and flexible as someone making and blowing $800k a year on luxuries. As for acceptance, having just one person love you for the impact you make on their life is infinitely better than having millions adore you for the (possibly bullshit) image and dream you are forever expected to show them.
To close this out, I'll speak back to the entrepreneurs out there again again: I'm not judging you for making your own life choices. I AM judging your shitty, egotistical need to showcase how great you are for your success when what you did would probably bankrupt the next person to try the exact same thing. And I'm DEFINITELY judging telling people that working 100+ hours a week or risking everything is a necessary part of making dreams come true.
Entrepreneurship is great. Entrepreneurs are full of shit.28
rant.GetType() == typeof(long)
I have voiced my unhappiness to the powers that be regarding having to sit in traffic for over an hour to get to work and an hour to get back home, in the hopes that some sort of resolution and compromise can be reached.
The response basically was, "We've never had anyone work from home before and this is very new to us, so we wouldn't know where to start and how to manage this."
Firstly, from what I've heard along the grapevine, someone has worked from home before. In fact, it was a developer... wouldn't you fucking know!
Secondly, you're the manager... FUCKING MANAGE! Yes this is perhaps "new" territory for the company, but it's certainly nothing new to the world. Or maybe I'm wrong?
How's about, rather than fucking "ummm-ing" and "ahhh-ing" about the working from home being a good idea or not, perhaps try saying, "You know what, let's try something for the next 3 months and see how it goes. We sit down and hash out when and how we are going to communicate regarding the work that needs to be done, and when you will need to come in for meetings and the like." If it doesn't work after 2 weeks, oh well... we tried. And if we're still going strong after month 4, I think we have a winner!
Perhaps it's a generational thing, seeing as management are Baby Boomers and I'm a Millennial? Then again, I could be wrong.
The point is that I see a potential solution to my problem that may actually work and benefit both parties, but they're either to fucking set in their old ass ways and stubborn to allow this. Or perhaps it's a thing of "if we do this for you, we have to do it for everyone", which they don't want to do.
But more importantly, they don't seem to get the whole notion of "a happy employee is a productive employee".6
Uggg..... I'm trying to encode a binary file in Python which may be an image or may be an executable, and then decode it back into a file (I plan on editing it in the middle, but baby steps for now..) but nothing is working!!
My plan is to:
Open binary file.
Decode as base64, or something else that could easily handle binary.
Convert byte data to string (for editory perpousos - I won't be editing bytes, I'll be doing custom encoding but that's irrelevant for this test)
Convert back to a byte string/array (with .encode(), probably)
Write to file.
I do this, yet the output has been altered... Though I haven't touched anything..
It's so enfuriating.. x.x18
var _self = Object.create(Rant);
Hello devs I'm back
A few months ago I joined a software development company and I was pretty specific that I wasn't going to do support or maintenance only feature development, well, this past 3 months I've been doing dev helping stablish good practices and a better architecture for the app, but guess who is joining a support team tomorrow, they sold me the idea of a refactor team, I was trilled and accepted, now they tell me it's a legacy bug fixing team, damn I hate this crap, hope y'all doing better5
A few days after the vacation, daddy (me) finally finished copying all the photos from the digital camera to the big external hard drive. Left it lying in the living room, in the corner where all the tech stuff frequently lies. In come my boys, and I'm not sure why, they start plugging power supplies around. Unfortunately the one from the laptop fit into the hole on the external disk, but had a different (higher) voltage. Result: 1 fried hard drive, containing all the baby photos and videos of said boys up that time.
I still believe that it's only the circuit board that is fried, and the data is still all there. I still have the hope to find a used disk, replace the board and all will be back.5
I still do exist, long time no see, fellow Devs! How is it going?
Didn't posted here in long time. Anything new relevant? I just started studying at an university. Hoping to post again here.12
Debugging WebRTC is pure hell.
Solution: ask the marketing department or even the execs to video chat with you to test it on a staging server. So I push my changes to the server, wait for them to build, call my lab rat, check all the bugs, clean the code, push the changes back up. No fancy breakpoints. I'm doing the old style like my great uncle did. Oh wait no, he was pretty intelligent, but my lab rat isn't. They probably don't know what a console is. So no baby I'm not only talking about console logging the problems, I'm talking `alert` the heck out of the bugs - okay no, I'll just display the objects in the middle of the screen. The screen is my console.1
Browsing through an old project of mine which let you make 3D scans of a person with a Kinect and easily add it to a game.
I worked on it during my minor in Japan. It's such a clusterfuck of code and different pieces of software glued together. But man, I had _so_ much fun making it. Funny enough it brings back great memories of the time I spent there.
I'm amazed I was able to finish it in time, or at least something that resembles "finished". Literally the day before I went on a three week round trip I had to demo it. And it worked reasonably well. I'm so glad the professor didn't screw me over on that one. Then again the other person working on a project there only made a simple raspberry pi space invaders. Haha. What a lazy cunt. We were literally told we could do _anything_ we found interesting.
I don't blame him though, he wanted to spend (and did spend) most of his time partying and socializing while he was there. Good for him :)
I should post this baby up on Github, even though it's a shit stain of a project. I want to improve on it when I have time. Who knows, someone might actually view/use it once. That would make me so happy, even if he doesn't do anything with it.1
i hate it when comedians smile too much.
it's like they are trying to pander or something. Or compensate the lack of material or humor
God it's so awkward because they smile as if implying that they are funny.
It feels like they are trying to hypnotize the audience into thinking they are funny.
Or as if they were your friends, I don't know what it is, but it's fucking awful.
Isn't smiling back is an evolutionary trait? Marketing folks like to brainwash people with their smiles so there has to be some truth to it.
But the last damn thing I want marketing to corrupt is stand up humor.
Just count how many times jerrod carmichael smiles. Or kate mckinnon.
God fucking dammit, let me decide if you are funny.
You can have good material with meh delivery, but not the other way around, I'm not a fucking baby laughing as a reflex, I can understand sentences.12
I keep seeing two philosophies bash heads at work.
1. "Hey, use these tools according to idioms and best practices for that tool. We worked hard getting this to work predictably, and it depends on you doing things consistently."
2. "Go pound sand, I want to do what makes sense for the project. To hell with your nazi conventions."
They're both right, and they're both idiots.
#1 is right because precedents exist for a reason. People did a bunch of stuff with their tools and got things to behave reasonably well, showing mastery over a stack. There could also be actual legal- and infosec- related reasons to following a protocol for changes, and ignoring those precedents invites disaster.
#1 is an idiot because there's a fine line between enforcing consistency and micromanagement. If the idioms they confuse with architecture are making it harder for other people to work, then they need to back off and let context, not ego guide the conversation. Good architecture should enable and encourage people to change the software in radical ways.
#2 is right because Context. Is. King. No project should shape around a tool. Tools should simply and objectively obey their users through good and bad use alike in service of the project. A culture that would oblige you to change for the sake of a tool is not an engineering-driven culture, it's a culture driven by self-anointed thought leaders who learned everything they know about software from Medium.com and Smashing Magazine. To enforce idioms and consistency blindly is turn the best practices found so far into the status quo that prevents change.
#2 is an idiot because there's a baby in the bathwater, which is some of that context they so treasure. By getting defensive with #1, they forget that the more they change, the more the team has to re-learn to adapt. The worst case is the cowboy that rewrites the implementation from scratch, causing QA to re-do ALL WORK and causing engineers to drop everything for one person's way of doing things.
The compromise is hard, but here's what I think it entails:
- Context really is king, but frame your changes in terms understood by how the team already thinks about the project; and
- Make those changes work independent of the tech stack on which they sit.
Doing this requires a solid understanding of, well, SOLID, and lots of patience dealing with ego and red tape.
This may seem obvious to you, but I'm so tired of watching the arguments at work about this degrade software quality and the end-user's experience.1