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
-
“Yeah but you’re not a *real* developer”
Fuck. you.
I wrote 80% of this code base. I do 80% of the tickets/storyboard points. I do all of the QA. My nose is to the grindstone every fucking day honing this craft and sweating my balls off like a blacksmith staring into the red hot kiln while the sores of previous mistakes scream bloody murder from the unrelenting exposure to heat. I saw this amazing industry of opportunity, freedom and self examination and wanted in no matter what it took. I glued myself to every pithy resource I could possibly get my hands on and crawled through the muck and filth of it all until I could keep myself warm with the smallest spark of my own making. I stoked that spark until it became a fire and stoked that fire until I could set entire forests ablaze. I listened to the ungrateful people keeping warm by my combustion saying it “wasn’t hot enough” or “would have been a nicer colour if they did it” or “could have warmed up just fine jogging on the spot”. I made painstaking alterations to my ignition and watched my undeserving benefactors gradually be silenced and begin to sit quietly by the heat. I jumped into that inferno daily, was reduced to ash daily and emerged reborn daily. But you are right! I didn’t get scammed out of $40k+ studying technology in an archaic institution from instructors who don’t give a shit and answering “D all of the above” for 4+ years straight therefor my opinion doesn’t mean shit. Push your bullshit to prod and watch the server come burning out of the cloud as the apocalyptic swarm of angry tickets come flooding in why don’t you? Bet they didn’t teach you that in school. You’ve never poked around inside an open source codebase in your life. They are just a mystery boxes of magic that unless someone holds your hands with finely crafted instructions containing a 50/50 picture to word ratio you throw a hissy fit. Every problem that comes up instead of working to solve it you reflexively point to the first person in the room while thinking with your pea brain how you can possibly scapegoat them into taking the fall for whatever it is that’s come up today you couldn’t possibly understand.
Not a real developer?
Fuck. You.28 -
Manager: How long until the current set of tickets is complete?
Dev: Based on storyboard points it’ll be 1.5 weeks from now
Manager: That’s unacceptable! Let me take a look at the board and see if I can remove some low priority tickets.
*Later that day*
Manager: Oooo I found a bunch of really exciting tickets in the backlog that I forgot about. I’ve added them to the board.
Dev: Did you remove any?
Manager: Huh? Oh right. No, I looked and it all needs to get done.
Dev: With these new tickets added to the board our new estimate is 4 weeks.
Manager: WHAT?!? BUT I SPENT ALL DAY LOOKING FOR EFFICIENCIES!!
Dev: …15 -
Dev: I’m taking a vacation next week
Manager: Good you need a break! I’ve put together a list of tickets for you to action during vacation since you’ll mostly be free during that time
Dev: Do you know what vacation means?
Manager: Well I work during *my* vacation
Dev: You write non-answers to emails and interrupt devs with status questions that are easily answered by a single glance at the kanban board. Also, you’ve just assigned a month’s worth of storyboard points to me on my week long vacation. We’d get more work done if you didn’t “work” during your vacation.
Manager: Well it all needs to get done! It’s the only way we can catch up and get ahead of schedule.
Dev: Why do you exist again?15 -
Being one of the top devs (and a good student admired by most lecturers) at college, my most humbling experience was when I joined my first job. I thought I knew SQL, I thought I knew C#. I realized in the first week, the thing I didn't know was "I don't know jack".
Thanks to a couple of great mentors (it took a few of them to bring me up to speed :P), I learned that the more I learn something, the more I will realize how much more there is to learn. I used tools to create storyboard animations in WPF, and my mentor would write it all in XAML! I'd write messy SQL and the other mentor just reduces it to a couple of elegant lines. They were like tech gods to my college self, all while being humble and friendly.
They also imbibed in me a sense of responsibility to carry on the culture of mentoring my juniors, which taught me much more than just the technical side of our profession.3 -
A day of an iOS developer life:
1. XCode crashed
2. XCode freeze
3. XCode "Jump to Definition" takes me to a different file that has the exact same variable name instead of jumping to the top of the file
4. XCode Storyboard designer throwing 1000000000 as UIStackView width on a newly created UIView
5. Heart attack
6. Lots of depression
** Note:
just noticed devRant web has xcode as placeholder in the tags box lol devRant knows my pain T_T8 -
Fucking Apple products fuck xcode fuck all ishit!
Wrapped my views in a UIStackView in storyboard designer and xcode gave it a width of 8,000,000 and height of 3,000,000
6 -
Fuck you ios,storyboad,xibs,xcode. FUCK OFF!! YOU FUCKING ASSHOLES. Literally giving me migrane with your fucking ass constraints!! Fuck you xcode for not having a terminal. Ios is utterly bullshit. Has fucking all kind of devices that I have to set constraint. Fuck you macos. You are slower than a snail. How on earth do you take so much time to build!!
Width, height, constraints, my ass! What is this fucking logic bro. Fuck you apple for making so many device of different sizes and then hiring us to set constraints. Warning warning warning oh what a load of crap!
I would rather die than set your fucking ass constraints.7 -
Xcode storyboard sucks!. At least it could've had a code version of the storyboards (like android XML layouts) so that at least you could properly copy paste a layout from somewhere. Autolayouts and constraints are so flipping confusing that I almost always end up doing all the layouts in the code itself.2
-
Xcode storyboards
I can't do it justice by explaining how many times having the entire UI flow in one file has helped me.
Even for unexpected stuff, like an Android dev joining the team and needing to know the workflow of login / registration -> print screen the storyboard.
Manager asking for all the different possible paths through the app -> print screen the storyboard(s).
And then live rendering of custom components to be able to see them while playing with alignments.
While it has its bugs, and could have a few more features, it's too useful to ignore.
I know many iOS devs don't like it, and that's fine because I don't like them either and I don't hire them ;-)1 -
!rant
Need some opinions. Joined a new company recently (yippee!!!). Just getting to grips with everything at the minute. I'm working on mobile and I will be setting up a new team to take over a project from a remote team. Looking at their iOS and Android code and they are using RxSwift and RxJava in them.
Don't know a whole lot about the Android space yet, but on iOS I did look into Reactive Cocoa at one point, and really didn't like it. Does anyone here use Rx, or have an opinion about them, good or bad? I can learn them myself, i'm not looking for help with that, i'm more interested in opinions on the tools themselves.
My initial view (with a lack of experience in the area):
- I'm not a huge fan of frameworks like this that attempt to change the entire flow or structure of a language / platform. I like using third party libraries, but to me, its excessive to include something like this rather than just learning the in's / out's of the platform. I think the reactive approach has its use cases and i'm not knocking the it all together. I just feel like this is a little bit of forcing a square peg into a round hole. Swift wasn't designed to work like that and a big layer will need to be added in, in order to change it. I would want to see tremendous gains in order to justify it, and frankly I don't see it compared to other approaches.
- I do like the MVVM approach included with it, but i've easily managed to do similar with a handful of protocols that didn't require a new architecture and approach.
- Not sure if this is an RxSwift thing, or just how its implemented here. But all ViewControllers need to be created by using a coordinator first. This really bugs me because it means changing everything again. When I first opened this app, login was being skipped, trying to add it back in by selecting the default storyboard gave me "unwrapping a nil optional" errors, which took a little while to figure out what was going on. This, to me, again is changing too much in the platform that even the basic launching of a screen now needs to be changed. It will be confusing while trying to build a new team who may or may not know the tech.
- I'm concerned about hiring new staff and having to make sure that they know this, can learn it or are even happy to do so.
- I'm concerned about having a decrease in the community size to debug issues. Had horrible experiences with this in the past with hybrid tech.
- I'm concerned with bugs being introduced or patterns being changed in the tool itself. Because it changes and touches everything, it will be a nightmare to rip it out or use something else and we'll be stuck with the issue. This seems to have happened with ReactiveCocoa where they made a change to their approach that seems to have caused a divide in the community, with people splitting off into other tech.
- In this app we have base Swift, with RxSwift and RxCocoa on top, with AlamoFire on top of that, with Moya on that and RxMoya on top again. This to me is too much when only looking at basic screens and networking. I would be concerned that moving to something more complex that we might end up with a tonne of dependencies.
- There seems to be issues with the server (nothing to do with RxSwift) but the errors seem to be getting caught by RxSwift and turned into very vague and difficult to debug console logs. "RxSwift.RxError error 4" is not great. Now again this could be a "way its being used" issue as oppose to an issue with RxSwift itself. But again were back to a big middle layer sitting between me and what I want to access. I've already had issues with login seeming to have 2 states, success or wrong password, meaning its not telling the user whats actually wrong. Now i'm not sure if this is bad dev or bad tools, but I get a sense RxSwift is contributing to it in some fashion, at least in this specific use of it.
I'll leave it there for now, any opinions or advice would be appreciated.18 -
Consecutive day number 3 of "What random dumb shit is Xcode going to pull on me today?"
today it doesn't like the ".storyboard" extension name that it created itself automatically. So that's my fault again I suppose?5 -
Had to interview an iOS dev.
When I asked what was better - xib/nib or storyboard? He told me He prefers to write custom c++....
WTF?6 -
How I always feel about Xcode when compiling Swift code, opening storyboard files, or just in general.
We need to make some of these stickers. ++
-
One of the most annoying things I find about being in the field of Computer Science: you have to read thick book after thick book, just to stay ahead or on par with technology.
Oh, technology x came out. New item appears in to-do storyboard: "read book x". Oh, only 900 pages huh? Oh, deadline this week huh? There goes my weekend.
What's this? After having read book x, now I have to read book y and also read about design patterns again?
Sigh.17 -
Checking Swift UI, first thoughts: goodbye Xcode freezing from storyboard loading ....
Sadly yes that's what I like about using Swift UI 😂😂😂
Oh and that binding, finally apple showed some love 😒 -
I hate programmatic auto layout. It's such a mess! Simple shit like cells that can easily be defined in a .nib become spaghetti coded messes that violate every good programming practice ever. Want to recreate the same style of cell again? Good luck reverse engineering the hieroglyphics your teammate wrote when creating the layout by hand. Never mind a whole bunch of useless shit is done in code that could easily be defined via runtime attributes through the storyboard. But why learn a new approach? Cause job security. Or because for some reason Interface Builder tools are seen as "too hard" or "not scalable" to use.. fuck me.2
-
so I am trying to learn ios development. i have started with learning the basics of swift first. does anyone know of a platform to test my knowledge of swift like a website or something which would ask questions like how to create an array, get its 2nd item, iterate thorugh it ,etc , so i could understand it better?
also, my trainer is continuously asking me to confirm if i should go ahead in the course with swiftui or the old storyboard ui . I don't understand the choice here as i thought swift ui is the current standard and obvious choice . should i chose storyboard instead? are people and big corps using storyboard? is storyboard more robust than swoftui?2 -
xcode rant
After a long and exhausting progress that feels like it took days! (maybe a day lol). I came to the conclusion that StoryBoard is probably one of the biggest pains in the universe. I tried to center a UIImage View for an eternity to work both with landscape and portriat and continued to get vaying results with no actual pattern whatsoever.... One day I woke up and there was actually more textfields than were originally put on...... wahhhhh?
Within this eternity I decided that my only hope against losing all sanity and bashing my head against a keyboard screaming "#$%# you Xcode!" was to do the UI in AutoLayout Programmatically. Took me 1 hour.... thats it... Just one. Instant love. haha
Okay Im done now. Have a great day devRanters! -
Being an old-timer and feeling a pain in my chest when people use Storyboard for iOS. It's the fucking bane of iOS.
3
Top Tags
Weekly Rant
View