Skip to main content
19 events
when toggle format what by license comment
Nov 8, 2019 at 0:10 comment added Daniel @JoeStrazzere, sounds good. I was not planning to be defensive, more educational than anything. Like their team is always commenting in JIRA, that it works on React web, which sounds to me like they assume Reactjs and React Native are exactly the same, otherwise I am unclear the constant need to compare apples with oranges. I guess I will leave out the education on third-party libs, but my partner suggested otherwise. I guess we shall see. As far as what I am going to do, no problem explaining that, when, well I thought the estimate was for that, seems to me they just don't like the estimate.
Nov 7, 2019 at 23:36 comment added Daniel @JoeStrazzere, yes.
Nov 7, 2019 at 13:19 comment added Daniel @Kilisi, yeah so React Native is fast evolving, breaking changes project. Just to use React Native is asking for bugs without the poor code quality and unmaintained third-party libs. I upgraded the project to 60.4 when it was brand new, that was a month ago maybe, RN is now on version 61.x. Newcomers ask me why did you only upgrade to 60 when its on...dude, when the upgrade was done, 60.4 was the newest version. I believe the hard conversation was never had by the original authors who charged big bucks. "I know you want this feature now, but it will cost you later" type of conversation.
Nov 7, 2019 at 13:18 comment added Kilisi Way out of my field..... hope it works out for you
Nov 7, 2019 at 13:17 comment added Daniel @Kilisi, No I did not make it worse. Are you familiar with React Native at all? Their application was only going to get worse with time. Not sure if you are familiar with the recent changes where everyone had to get compliant with Androidx. It has deprecated lifecycle methods, logic inside of constructor functions that have no business being there. So an upgrade with an RN project that major, there was going to be bugs, on top of code quality and unmaintained third-party libs.
Nov 7, 2019 at 13:15 comment added Kilisi was the purpose of the upgrade to fix the app? Sounds like you made it worse
Nov 7, 2019 at 13:12 comment added Daniel @Kilisi, well I inherited the project with bugs due to code quality, the application was also due an upgrade. Some of the old bugs are gone, but there are some new bugs due to an upgrade, from RN 53.3 to RN 60.4, yeah there was going to be bugs, especially with so many third-party libs that are not maintained, one of the authors admitted to me he knew nothing about RNs autolinking and then proceeded not to update his documentation at all. Two other libs I submitted PRs so my customer and nobody else would have future problems, never merged, never reviewed.
Nov 7, 2019 at 13:09 comment added iLuvLogix @Kilisi There are no such things as bugs - they are called 'unfinished features'..
Nov 7, 2019 at 12:51 comment added Kilisi Why are there a lot of bugs?
Nov 7, 2019 at 12:27 comment added iLuvLogix How to prepare for a meeting about lots of bugs: Bring a fly-squatter and a can of raid.. ;)
Nov 7, 2019 at 11:47 answer added gnasher729 timeline score: -1
Nov 7, 2019 at 5:55 review Close votes
Nov 7, 2019 at 13:42
Nov 7, 2019 at 2:38 comment added Nelson @Daniel As a software developer, significant majority of users have zero comprehension of why bugs exist, and none of them will accept responsibility of contributing to the problem (What do you mean I can't keep 500 tabs opened in Chrome and play 15 YouTube videos at the same time? What do you mean the requirements are changed every week? I am the customer, I'm always right! etc., etc.)
Nov 7, 2019 at 2:24 answer added Cameron Roberts timeline score: 5
Nov 7, 2019 at 0:17 comment added Daniel @Keltari, an explanation of why there are so many bugs.
Nov 6, 2019 at 23:59 comment added Keltari Imagine you are the client. What do you think they are going to want?
Nov 6, 2019 at 23:56 vote accept Daniel
Nov 6, 2019 at 23:48 answer added ChrisFNZ timeline score: 10
Nov 6, 2019 at 23:39 history asked Daniel CC BY-SA 4.0