@cafecortado

A) Thats what i'm asking them to figure out. The same callback is being triggered multiple times. I've no idea from where because their code is a hot mess. I also can't reproduce the issue either

B) Got another response and thats not what they wanted. Despite the chat being in a long-running open telegram group between both companies, they are again asking for details on what email address we login in with to their dashboard so they can check logs for network issues tided to that accounts users

@iSwimInTheC we haven’t come back to it yet, not fully anyway, as something unrelated came up. There is a task to have a designer come up with other ideas and then we’ll pick which one we like

Extremely glad we waited 6 months for this expert in mobile design to become available ... been hugely helpful in speeding up the process

@retoor No. Its sign up and then a bunch of security related things that a user pretty much "must" do. But they want to make it semi optional now to avoid scaring first time users, by never showing it. But then plaster it everywhere that you didn't complete this action the second you get in

@Lensflare as in had the same discussion or actually built it? interested to know if you built it and got any useful feedback on it

@CruN they are all terribly subpar ways to build an app compared to native

The idea of starting a new app while ignoring the massive amounts of extra battery and memory that will be used, even before writing a single line, is just insane. They are slow, buggy, resource hogs.

AirBnb wrote a good article about why they ditched RN. Udacity posted a statement they had the same experience. Uber dropped it. Walmart dropped it. Teamwork.com dropped it. Facebooks own messenger team, who had inside access to the best RN devs in the world, still couldn’t get it to perform the way they needed it too

For these companies all to spend millions re-writing everything to get rid of it, speaks volumes to how terrible and problematic it is. Can’t be justified. It’s all marketing BS and hype

Flutter is “better” but it’s not hard to be better than terrible. I’ve read articles online that say flutter uses 50% more resources than native

Native is the only realistic option

@thebiochemic it is an unpopular opinion because the other option is to not be an asshole

I’m a dev, I write code all day long, I’m busy from the beginning of the day until the end. I keep myself off do not disturb so that I can help someone who needs it. I ask in return, don’t waste my time. Fair offer

Neither, ever

I have worked with many people who need to read that link.

They send a message "Hi", I switch over to the chat app within a few seconds and i'm left staring at:

xxxxx is typing ...

For a long time, I eventually go back to reading/writing whatever I was and then I get cut off again with a second message, which is only 20% of the full message they want to send.

It is the bare minimum of respect to your colleagues to not not waste their time, and compose the full message you want to send, and then click enter. Sending people multiple distracting notifications for a single point, and then leaving them waiting in-between is extremely rude

@darksideofyay now is not the time for rational, clear headed responses. Pfft

@darksideofyay this is like the 9th infuriating issue this company has caused. Mostly for completely BS reasons. I am fighting the urge to rewrite their code to make my own SDK, at least at the minute, because they are promising new features in the near future and I have no idea how those will work with their server, because they document nothing

Spent a good 20-30 minutes today staring at their code trying to justify doing it like “if I rewrite it all, and they add new stuff, I can just read their new code and add that too right? Cause it’s all open source”

The urge to do it is slowly getting stronger, but could massively back fire

Thank you for contacting terraform support. Our offices are now closed

@NoMad @electrineer i'm glad my rants can serve as a testbed for your issues

@RexGalilae when someone is looking for a job, I can assure nobody wants to be spammed with irrelevant job posts

Rather than upskill on something new to make myself more appealing, or work on a take home challenge, or search for myself. I’m spending an entire day a week reading specs and explaining to recruiters how they’ve fucked up, in the hopes they’ll leave me alone next time. Nobody wants that while looking at their bank account drip down

@AvatarOfKaine there are a lot of evangelists ruining it tweeting very pie in the sky crap. And promoting NFT projects that are way over priced.

Behind all of that is a platform that makes it a lot easier to build a secure and stable application much easier. Also systems that allow the users to vote on changes. And the entire thing is open source allowing people to put forward changes

Take away all the nonsense and it’s a very powerful platform. Devs have built lending systems like banks, but with a fraction of the fees

There are also many chains not as power hungry as Bitcoin and Ethereum. That problem will hopefully go away in the future

@AvatarOfKaine no, selling cocaine is sssssooooo last year.

We sold digital native, decentralised cocaine tokens, whose price is pegged against the real thing! Whenever the supply increased, decreasing the the price, our dedicated team of snorters would reduce the supply to ensure an always upwards trend.

This was going to be a game changer for institutional investors, who previously had no access to the lucrative cocaine market

@Charmesal Yeah I got another new job summer time this year. Last place was a startup that lost its funding. I will probably rant about that at some point in the future.

I can see myself working here a good while. The entire leadership are developers, so we all think the same about how the company should run. Meetings are rare because everyone understands that you need time and space to actually get the thing done, before having a meeting to discuss it.

They also have me working on lots of meaty technical challenges, which I like. So it probably all worked out for the better ... but i'll still moan about how I got here ha

@Charmesal trying to remember which "new" job you know about. Pretty sure i'm not there anymore haha.

My new new job is great, in terms of what i'm doing and the people inside the company I have to deal with. Have to deal with many external people that bring back warm fuzzy (suicidal) memories. And a bunch of partially abandoned open source projects that are super critical to what we are doing

... so yeah, varying degrees of fun. I do have plenty to rant about, just too busy to write it down. Need to work on that.

Re: devrant itself. I only ever followed a small handful. I mainly used it to rant about my stuff, wasn't in the right mindset to listen to others lol. I have noticed less eye catching content over the past while. But I still see it as a nice place to moan anonymously, so i'll probably be popping in/out for a long time

... but he can reverse a binary tree on a whiteboard. So its all cool

@nitnip I am very pro “test the actual code”. But there are many situations where that’s not possible or practical.

My use case is a third party library that has an embedded social media login feature. I have to put a lot of logic around this and want to test that. But I can’t have my unit tests logging into Twitter accounts. So I need a way to mock that and just return a dummy object from this SDK

This library has a shit tonne of classes and constructors marked as private or final so I can’t subclass or touch them. And the networking code is hidden away so I can’t stub that either

Omg yay! Woop woop

@Nanos in no way shape or form does "these days" equate to 50 years. "These days" as a term means "the present". 50 years ago is not the present

@Nanos that’s not true at all. Getting fired for writing shit code is just something that barely ever happened at any point.

Worked for large multi nationals with over 100k staff. Extremely common to find people with +30 years in the company who’ve not got a clue. Because they’ve never fired people, shit devs just decide to just become “lifers” and coast through their days.

One of these lifer guys was put on our team after his previous team shut down. He had no relevant experience of any kind for our team. He couldn’t figure out modern IDE’s or text editors and refused to do anything other than write code in Microsoft word!!! He produced about 1% of the code that everyone else did.

He couldn’t be fired, so they just found somewhere to put him, regardless of what impact that has.

You working for IBM? Used to work for IBM and they still had IE6 in their browser support matrix for a bunch of divisions. I think because they had old products that a handful of companies were still using and they didn't want to invest in completely updating them so only do patches every now and then

@Charmesal only thing missing to make it an SO post was a generic cry for help like:

"Before posting this I did try everything already, but nothing worked. Please help"

@bzq84 oh I have a degree in recruiter-bullshit-ology, from the national institute of “Get the fuck outta here”.

Fully aware it’s BS, fully aware he’s way out of his depth. But the company’s product sounds interesting and they don’t have jobs posted anywhere else. All I’m looking for is confirmation it is an iOS role and a contact to get passed him. I’ll take it from there. This is unfortunately the dance that must be done in this area for some reason lol

Update:

Recruiter said he accidentally screwed up the iOS developer spec by merging it with the full stack spec (what ever that means). Has promised it is an iOS developer role and will get back to me.

Interesting that this is a second time this week that something similar has happened.

Stay tuned

@mundo03 specifically for iOS / Mac, there are several advanced networking tools available.

Overview:
https://developer.apple.com/documen...

Low level network debug logging:
https://developer.apple.com/documen...

Setting up a packet trace:
https://developer.apple.com/documen...

This is all quite time consuming and cumbersome to setup, wait for a random occurrence of the issue, and view all the logs to verify that its all fine.

Thats why its so frustrating when server side team doesn't have a means to check how long responses are taking, and inflict all this work on client side, when the error specifically says the connection is fine.

@mundo03 again, if I have a log on my side saying I did a handskahe and it went fine, I sent a request and the server acknowledged it, the server has a log showing it was received, server has a log showing it processed at least a piece of the request, the client continued to receive keep alives but no payload .... then it is a performance issue on the server.

I have been through this dozens of times in different companies. The obsession with backend folks to dismiss client side timeouts, as client issues, is staggering. Never once has this been a client side issue, or a connection issue. Because this error means the connection is fine, but the server is taking too long.

As the second comment highlighted, log response times, and spend 15 seconds checking did it take too long. Or spend 6 days arguing about all the possible things it could be

@mundo03 this was iOS, so there’s only 1 back button.

Returning to where you left off during on boarding is quite common. Our app is complicated and has a decent sized on-boarding process. Some of it requires the user to leave the app and come back. Low end devices can have a lot of issues with this. Without state restoration, users could be put into an infinite loop of getting to screen 3, leaving app, coming back to the first screen, getting to screen 3, having to leave again, returning to screen 1 again etc ...