Details
-
AboutAn Apple developer since 1984, disenfranchised and pissed at Apple for turning from excellence to a bunch of fuckups.
-
SkillsAny assembly (I piss machine code). Any communications system. C, C++ Objective C, Fortran if pressed, AppleScript for fun, FileMaker because other databases suck dick.
Joined devRant on 4/11/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
-
Girl: we need to talk
Me: OK
Girl: you seem to have more time for your computer than me. I want to know how important I am to you.
Me: You are the number 1 in my life.
Girl: *smiles and hugs me*
Me: (thinking)...Just that I start counting from 033 -
Looking for a job as a deveoper be like:
Job title: car driver
Job requirements: professional skills in driving normal- and heavy-freight cars, buses and trucks, trolley buses, trams, subways, tractors, shovel diggers, contemporary light and heavy tanks currently in use by NATO countries.
Skills in rally and extreme driving are obligatory!
Formula-1 driving experience is a plus.
Knowledge and experience in repairing of piston and rotor/Wankel engines, automatic and manual transmissions, ignition systems, board computer, ABS, ABD, GPS and car-audio systems by world-known manufacturers - obligatory!
Experience with car-painting and tinsmith tasks is a plus.
The applicants must have certificates by BMW, General Motors and Bosch, but not older than two years.
Compensation: $15-$20/hour, depends on the interview result.
Education requirements: Bachelor's Degree of Engineering.42 -
*Now that's what I call a Hacker*
MOTHER OF ALL AUTOMATIONS
This seems a long post. but you will definitely +1 the post after reading this.
xxx: OK, so, our build engineer has left for another company. The dude was literally living inside the terminal. You know, that type of a guy who loves Vim, creates diagrams in Dot and writes wiki-posts in Markdown... If something - anything - requires more than 90 seconds of his time, he writes a script to automate that.
xxx: So we're sitting here, looking through his, uhm, "legacy"
xxx: You're gonna love this
xxx: smack-my-bitch-up.sh - sends a text message "late at work" to his wife (apparently). Automatically picks reasons from an array of strings, randomly. Runs inside a cron-job. The job fires if there are active SSH-sessions on the server after 9pm with his login.
xxx: kumar-asshole.sh - scans the inbox for emails from "Kumar" (a DBA at our clients). Looks for keywords like "help", "trouble", "sorry" etc. If keywords are found - the script SSHes into the clients server and rolls back the staging database to the latest backup. Then sends a reply "no worries mate, be careful next time".
xxx: hangover.sh - another cron-job that is set to specific dates. Sends automated emails like "not feeling well/gonna work from home" etc. Adds a random "reason" from another predefined array of strings. Fires if there are no interactive sessions on the server at 8:45am.
xxx: (and the oscar goes to) fuckingcoffee.sh - this one waits exactly 17 seconds (!), then opens an SSH session to our coffee-machine (we had no frikin idea the coffee machine is on the network, runs linux and has SSHD up and running) and sends some weird gibberish to it. Looks binary. Turns out this thing starts brewing a mid-sized half-caf latte and waits another 24 (!) seconds before pouring it into a cup. The timing is exactly how long it takes to walk to the machine from the dudes desk.
xxx: holy sh*t I'm keeping those
Credit: http://bit.ly/1jcTuTT
The bash scripts weren't bogus, you can find his scripts on the this github URL:
https://github.com/narkoz/...59 -
A group of wolves is called a pack.
A group of crows is called a murder.
A group of developers is called a merge conflict.28 -
Interviewer: Welcome, Mr X. Thanks for dropping by. We like to keep our interviews informal. And even though I have all the power here, and you are nothing but a cretin, let’s pretend we are going to have fun here.
Mr X: Sure, man, whatever.
I: Let’s start with the technical stuff, shall we? Do you know what a linked list is?
X: (Tells what it is).
I: Great. Can you tell me where linked lists are used?
X:: Sure. In interview questions.
I: What?
X: The only time linked lists come up is in interview questions.
I:: That’s not true. They have lots of real world applications. Like, like…. (fumbles)
X:: Like to implement memory allocation in operating systems. But you don’t sell operating systems, do you?
I:: Well… moving on. Do you know what the Big O notation is?
X: Sure. It’s another thing used only in interviews.
I: What?! Not true at all. What if you want to sort a billion records a minute, like Google has to?
X: But you are not Google, are you? You are hiring me to work with 5 year old PHP code, and most of the tasks will be hacking HTML/CSS. Why don’t you ask me something I will actually be doing?
I: (Getting a bit frustrated) Fine. How would you do FooBar in version X of PHP?
X: I would, er, Google that.
I: And how do you call library ABC in PHP?
X: Google?
I: (shocked) OMG. You mean you don’t remember all the 97 million PHP functions, and have to actually Google stuff? What if the Internet goes down?
X: Does it? We’re in the 1st world, aren’t we?
I: Tut, tut. Kids these days. Anyway,looking at your resume, we need at least 7 years of ReactJS. You don’t have that.
X: That’s great, because React came out last year.
I: Excuses, excuses. Let’s ask some lateral thinking questions. How would you go about finding how many piano tuners there are in San Francisco?
X: 37.
I: What?!
X: 37. I googled before coming here. Also Googled other puzzle questions. You can fit 7,895,345 balls in a Boeing 747. Manholes covers are round because that is the shape that won’t fall in. You ask the guard what the other guard would say. You then take the fox across the bridge first, and eat the chicken. As for how to move Mount Fuji, you tell it a sad story.
I: Ooooooooookkkkkaaaayyyyyyy. Right, tell me a bit about yourself.
X: Everything is there in the resume.
I: I mean other than that. What sort of a person are you? What are your hobbies?
X: Japanese culture.
I: Interesting. What specifically?
X: Hentai.
I: What’s hentai?
X: It’s an televised art form.
I: Ok. Now, can you give me an example of a time when you were really challenged?
X: Well, just the other day, a few pennies from my pocket fell behind the sofa. Took me an hour to take them out. Boy was it challenging.
I: I meant technical challenge.
X: I once spent 10 hours installing Windows 10 on a Mac.
I: Why did you do that?
X: I had nothing better to do.
I: Why did you decide to apply to us?
X: The voices in my head told me.
I: What?
X: You advertised a job, so I applied.
I: And why do you want to change your job?
X: Money, baby!
I: (shocked)
X: I mean, I am looking for more lateral changes in a fast moving cloud connected social media agile web 2.0 company.
I: Great. That’s the answer we were looking for. What do you feel about constant overtime?
X: I don’t know. What do you feel about overtime pay?
I: What is your biggest weakness?
X: Kryptonite. Also, ice cream.
I: What are your salary expectations?
X: A million dollars a year, three months paid vacation on the beach, stock options, the lot. Failing that, whatever you have.
I: Great. Any questions for me?
X: No.
I: No? You are supposed to ask me a question, to impress me with your knowledge. I’ll ask you one. Where do you see yourself in 5 years?
X: Doing your job, minus the stupid questions.
I: Get out. Don’t call us, we’ll call you.
All Credit to:
http://pythonforengineers.com/the-p...87 -
!rant
After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:
1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.
2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)
3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.
4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.
5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.
6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.
7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.
8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.
9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)
10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...
These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!232 -
I’m making an iOS app "WTF Meter", which tracks the amount of phrases like "what the fuck", which you say to your rubber ducky while you review code or any other pieces of work.
It’s supposed to be a gag app for entertainment but it also accurately measures the "WTFs per minute" value, which we all know to be the only true indicator for code quality ;)
Phrases can be customized and there is a history of sessions for later review.
If you are interested, I’d be glad if you could test the current TestFlight version and give me any kind of feedback.
I’m particularly interested in what you think about the design and how intuitive the app is.
Gif showing the app in action:
https://gifyu.com/image/b33tJ
TestFlight:
https://testflight.apple.com/join/...30 -
Fuck, its 2025 and we still cant shake away the "you work with technology, you must know how to fix my microwave" stereotype.
Seriously, I have fewer apps in my phone and access fewer websites and even spend less time on my devices than the HR old hags, and yet im the one who has to come and "explain to them how to print a PDF".
Holly fucking crap. I haven't used a printer in MONTHS. With the cost of the time I will take to figure out how to communicate with those mummies that is 'just click the print button', they could hire ChatGPT to do it for a decade.
Fuuuuuck, that is the reason those stupid AI chat bots exist! To endlessly toil at the repetitive and predictable task of saying 'hi there! Have you clicked "print"?'
Imma gonna leave work early and get pissed. Luckily, I've already done a couple hours of OT for the day, so it won't seem so out of the ordinary.11 -
OK, Started to work on iOS app few months ago. Had to deal with so many xcode and swift problems that it is driving me nuts. How any sane person can code this shit language? I never seen such an idiotic syntax in my life. I worked with so many languages in past 12 years: C++, Java, Python, PHP, Ruby, JavaScript. So many code editors & IDE's: Subline, Notepad++, Eclipse, Jetbrains, VSCode, Atom. But after working XCode and Swift for few months I want to burn down my MacBook that I only had to get to work on this iOS app with this shitty XCode IDE.4
-
FOUR DAYS
Tomorrow will be the FOURTH FUCKING DAY spent trying to get this piece of shit iOS simulator to not crash the app.
I’VE TRIED EVERYTHING.
FUCK APPLE. FUCK XCODE. FUCK IOS😠😤😠😤😠😤😠😤😠😤
Steve Jobs was a twat, and the IPhone X garbage piece of technology10 -
Dear Apple,
We've sent you a new message regarding your app, Xcode. To view or reply to the message, go to the Resolution Centre.
----------------------------------
We noticed that your app did not fully meet the terms and conditions for reasonable fucking update size. Your latest app update requires over 40 GB of free fucking disk space. Please bear in mind that many of your own fucking laptops only have 120 GB of disk space. For optimum user experience, it would be best if the user didn't have to uninstall other apps from their system just to run your shitty update system.
Next Steps:
To resolve this problem, we recommend that you fix your shit. If you are unable to fix your shit, we recommend that you don't take 30% of all iOS developer's income so that you can make giant fucking glass donut buildings, and instead use that ridiculously disproportionate monopoly-abusing cut and invest that money in fixing your shit, to lighten the load of developers on whose backs you have become the most cash-rich company in human history.
Resources:
There are plenty of resources such as Stack Overflow to take advantage of, in order to learn how not to create a bloated piece of shit IDE.
Once you've completed all required changes, please upload a new binary to the App Store.7 -
Do you believe in Spanky? I hope so, because Spanky is the one and only true being that made the universe and all of us.
If you don‘t believe in Spanky you will go to hell and will be tortured for all eternity.
Spanky loves you and has a personal relationship with every one of you.
The evidence for the existence of Spanky is everywhere and completely undeniable.
Just look at the trees. Aren’t they great?
Also We have the Spanky Bible, written by Spanky himself which says that Spanky exists. That is historical evidence right there.
Spanky is completely invisible and can’t be heard or touched, but you need to believe anyways.
Spanky chose to be hidden, even though he has made himself apparent to his people in the past, as it says in the Spanky Bible, which is true. Spanky wants to test your faith, so that you believe in him without evidence. Believing without evidence is a virtue and the requirement for being a good person.
Speaking of good person, if you don’t believe in Spanky, you not only go to hell for your sins, you also are a very evil person without morality. Because morality can only come from Spanky.
So, please, for the sake of your eternal soul, believe in Spanky.14 -
Thank you, appstore, for showing me an ad for the app that I was searching for, right above the search result for this app! 🤦♂️
5 -
The junior dev I've been unofficially mentoring for the past 6 months has now been assigned to me officially. On top of that, I got myself a second junior everybody neglected and was tasked to whip him in shape.
Next step is going to make a developer out of this fucker or die trying. And then I'm going to call several tech leads a cunt for hiring a junior dev and letting that person down for months.
Every junior deserves a stern, dedicated mentor, a thick affectionate whip on their back to correct their juniorly mistakes and all the support they deserve to grow into the merciless professionals you need to handle complex features beyond recoloring a button.
If you, as a tech lead, are unwilling to teach a junior, you shouldn't take the position of a tech lead, nor the salary.16 -
i earnestly believe it to be a fact that it doesn't matter if you have a team of monkeys or elite 100x "super rockstar ninja coders" (whatever that means). in the end the retard management will kill the project with their poor planning and watergile practices that will force even the toughest devs to pull their hair out and have a breakdown regardless of their skill level
we as devs have been complaining for years but management is either deaf or simply refuses to listen
the worst part is that we get blamed when inevitably the project does fail because of managerial stupidity smh7 -
"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"
So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.
First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.
So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.
Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?
I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.
Did you run the code I gave you to do this update?
"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"
So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.
More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!
I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.
And this, my friends, is the part I will never forget.
"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."
You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!
"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."
I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.
So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.
You just cannot make this kind of stuff up.106 -
GOD ALMIGHTY I HATE SWIFT & XCODE...
Why the fuck does it take a horrendous amount of time to muck about with layout constraints. Why the heck does xcode choose to add constraint layouts to elements that already have pissing constraints! Why does dealing with something as trivial as tables have to be so god damn fucking involved when HTML and CSS let me create and style tables in fuck all lines.
And what the hell is up with how pissing long xcode takes just to figure out that 1 extra line of code I've just added. You jump to another file and xcode finally decides to be an ide again and bitch at the fact that you've forgotten to add some parameter or that they've decided to rename paramter "x" since version fuck nows what.
Working with abstract classes is fun, lets use protocols (because interfaces are too old school) and then lets tack on something we call extensions and then lets make people piss about with convenience initializers.
And lord almighty, what the fuck is up with casting, what all this ?! BS. What's wrong with just checking if the value is null in the first place, or whats wrong with giving something an initial value, oh because having to unwrap shit is more elegant right??
And good god, I need to own a fucking cinema screen just to have the storyboard open, there's less fucking panels on the Sistine Chapel ceiling
then there is in xcode.2 -
I do love u ranters
.
.
.
.
.
.
.
.
Whenever I feel like I’m not good enough at my trade, I come here to read a few rants. While I am a failure, it’s so nice to know there are even more disappointing devs around.9 -
Short rant: I hate xcode, I hate Swift, I hate Apple.
After 3 weeks of intensive work (I'm an apprentice, part-student, part-worker), I was happy to go back to school and was like "Oh we're going to learn iOS, sounds cool !".
It is now friday, I have homicidal tendencies growing inside me, I want to cry whenever I hear xcode or swift.
Why in the hell I can't use a string argument when I'm calling a function NEEDING a string arg ?
Why do xcode take so long to tell me that there is a problem, why is the error message not explicit AT ALL ?
Why dictionaries so hard to manipulate, EVEN IN JAVA IT'S SIMPLIER.
Why putting our API call in specialized files make them run AFTER EVERYTHING ELSE and the solution that is given to us is deprecated since 5 years ?
Why is a classic c-style for loop is now deprecated ?
These are just a drop in the ocean of WHAT THE FUCK IS THAT that we came across this week.
Fuck Swift, fuck xcode.
7 -
Gene Hackman and his wife and dog all found dead.
He was like 95 or something. She was 63. Daughter said she suspects a gas leak.
Much sad, RIP to the legend, the OG Lex Luther6 -
Instead of arguing about whether the table should be called Users or User, just call it UserTable. Problem solved6
-
I've just received news that Microsoft are to release a brand new search engine in China.
It will be called "Bing Bong".2


