Here's a recent interview I had for an Android Developer job:
I: Interviewer, M: Me

I: hello, welcome
M: hi, thanks

I: do you know Kotlin?
M: yes, I've been working with it for 1.5 years and have written 3 projects in it

I: do you know RxJava, Dagger, Retrofit, and how to make Custom Views?
M: yes, I'm comfortable with them *explains*

I: do you know Room?
M: yes I do, I've done a lot of practices in it, but unfortunately have never needed to use it in production

I: what architecture do you use? Do you know MVP?
M: I'm currently using MVVM, but not MVP. I've debugged projects in it so I know what's going on in it

I: ok, do you have any questions for us?
M: how did I do?

I: I'm sorry sir, but you're not even a junior here
M: what? Why is that?

I: well you don't know Room and MVP?
M: I said I know them, just haven't used them in production.

I: well you have 3 years of experience but you dont even know Kotlin!
M: Kotlin was your first question and I said I have 3 projects in it. Did you even check the samples you asked for in the job posting?

I: SIR YOU'RE NOT A GOOD FIT FOR US, THANK YOU FOR COMING.

:/

Me: Oh I see were using a non-standard architecture on this app. I like this bit but what is this doing? never seen it before.

Him: Ah we use that to abstract the navigation layer.

Me: oh ok, interesting idea, but that means we need an extra file per screen + 1 per module. We also can't use this inbuilt control, which I really like, and we've to write a tonne of code to avoid that.

Him: Yeah we wanted to take a new approach to fix X, this is what we came up with. Were not 100% happy with it. Do you have any ideas?

**
Queue really long, multi-day architecture discussion. Lots of interesting points, neither side being precious or childish in anyway. Was honestly fantastic.
**

Me: So after researching your last email a bit, I think I found a happy middle ground. If we turn X into a singleton, we can store the state its generating inside itself. We can go back to using the in-built navigation control and have the data being fetched like Y. If you want to keep your dependency injection stuff, we can copy the Angular services approach and inject the singletons instead of all of these things. That means we can delete the entire layer Z.

Even with the app only having 25% of the screens, we could delete like 30+ files, and still have the architecture, at a high level, identical and textbook MVVM.

Him: singleton? no I don't like those, best off keeping it the way it is.

... are you fucking kidding me? You've reinvented probably 3 wheels, doubled the code in the app and forced us to take ownership of something the system handles ... but a singleton is a bad idea? ... based off no concrete evidence or facts, but a personal opinion.

... your face is a bad idea

I once had a manager who would, at every stand up, ask everyone if there was a better way to solve their problem. She did this even if the team had already decided on a solution or even if there was no problem at all. She wouldn't let us continue the stand up until we had proposed a new 'solution' that was close to her 'suggestions'.

Some of my favorite suggestions were: "Are you doing everything you can to not make it too 'spiffy' ?". If you said yes the follow up was always: "can you tell me how?"

Then when you said you hit a bit of a bump yesterday due to something unexpected she always demanded that you pair programmed today. Now I don't have anything against pair programming, I even think it's useful from time to time, but being forced to sit next to someone or have someone sit next to me every time someone encountered something unexpected annoyed the shit out of me. Needless to say no one had any problems to speak of during stand ups after a while.

Whenever I was sparring with one of my colleagues she would always join in and start proposing 'solutions' about technical problems she didn't even understand. Again, she wouldn't back down until we had accepted her 'solution'. We would then go to a different room and hope she wouldn't find us there.

This went on for months, until several people had disagreed with her so much that it ended in shouting matches.

It still makes me angry when I think of one person crippling a team that much. I took my issues to her, to HR and finally to the CEO directly, but no one did anything about it.

Finally one of my colleagues decided to quit. After he handed in his two weeks notice our manager came to me and asked if she could talk to me in private.

She told me that she didn't understand why our colleague quit and she thought everything was going great. This was after just about everyone had told her that they hated how she acted and that if she wouldn't stop they'd quit. I had told her that myself twice.

She then proceeded to tell me that I was the most valuable employee and that the company couldn't go on without me. As a gesture of their appreciation for my invaluable effort, she was so generous to offer a salary increase of 50 euro, before taxes.

I laughed, said no and handed in my two week notice the next morning.

I vowed never to work with fucktards again, and I haven't since.

Imagine, you get employed to restart a software project. They tell you, but first we should get this old software running. It's 'almost finished'.
A WPF application running on a soc ... with a 10" touchscreen on win10, a embedded solution, to control a machine, which has been already sold to customers. You think, 'ok, WTF, why is this happening'?
You open the old software - it crashes immediately.
You open it again but now you are so clever to copy an xml file manually to the root folder and see all of it's beauty for the first time (after waiting for the freezed GUI to become responsive):
* a static logo of the company, taking about 1/5 of the screen horizontally
* circle buttons
* and a navigation interface made in the early 90's from a child
So you click a button and - it crashes.
You restart the software.
You type something like 'abc' in a 'numberfield' - it crashes.
OK ... now you start the application again and try to navigate to another view - and? of course it crashes again.
You are excited to finally open the source code of this masterpiece.

Thank you jesus, the 'dev' who did this, didn't forget to write every business logic in the code behind of the views.
He even managed to put 6 views into one and put all their logig in the code behind!
He doesn't know what binding is or a pattern like MVVM.
But hey, there is also no validation of anything, not even checks for null.
He was so clever to use the GUI as his place to save data and there is a lot of parsing going on here, every time a value changes.
A thread must be something he never heard about - so thats why the GUI always freezes.

You tell them: It would be faster to rewrite the whole thing, because you wouldn't call it even an alpha. Nobody listenes.
Time passes by, new features must be implemented in this abomination, you try to make the cripple walk and everyone keeps asking: 'When we can start the new software?' and the guy who wrote this piece of shit in the first place, tries to give you good advice in coding and is telling you again: 'It was almost finished.' *facepalm*
And you? You would like to do him and humanity a big favour by hiting him hard in the face and breaking his hands, so he can never lay a hand on any keyboard again, to produce something no one serious would ever call code.

full stack web development in 2017: mvvm model, api for backend, parsing on frontend

me: <?php echo "<div>hello".$name."</div>" ?>

My first actual rant on devRant:

Fuck corporate companies. Fuck agile development.

In the last 8 months I’ve been with this company, I’ve 1) made the app layout (which was super fucked) compatible with iPad. 2) reduced the apps size by 1/3 of the original size. 3) improved memory usage by double the efficiency, nearly eliminated all memory leaks. 4) gotten employee of the quarter for some of the above mentioned.

After all of this I got a talking to from product manager that “he knows I am a good developer but needs more consistency” after I spent a sprint on one story trying to consolidate front end validation logic and make a “validatableTextField” actually do some validation. So much for the MVVM you promised me.

Also, was promised I’d get some experience with Android, and with a team of 8 devs 6 of which have droid backgrounds and other two are juniors, guess whose only even built the droid project once in 8 months? You guessed it. This company has drained me of all of my knowledge, went against most of its promises to me, and values pushing features to the point of adding tech debt faster than I can solve it.

Unfortunately my personal life relies on this job or I’d quit right away. But you bet your ass I’m passively looking for something and I can’t wait till I get a job offer and quit on these ungrateful hypocrites.

I shit you not. This this a job qualifications qualifications entry level on LinkedIn.

7+ years working as part of a development team and with the following technologies:
Node.js Typescript and Java-based, microservice-driven applications using Spring Boot or similar framework
RESTful API design / microservice architectures
MongoDB or any other NoSQL DB
Message queues e.g. RabbitMQ, Kafka etc.
Modern MV*(MVC, MVVM, etc..) frameworks e.g. React, Angular, Vue etc.
JavaScript and design patterns, CSS and HTML
Modern CSS and view libraries e.g. RxJS, Angular Material, Typescript, JS ES6 etc.
Unit and UI testing using third party tools e.g. Jest, Cucumber, Groovy & Spock, etc.
Bachelor's degree in computer science or related field

Refactored and upgraded a web app from 2013 in a week. Long days and nights of changing horrible jquery selectors I'd written when I was new to coding into nice a nice MVVM structure. Finally shutting down my laptop, beer in hand and sat out in the sunshine.

Only people reading this will know the feeling of relief I am feeling now!

I think I might change my middle name to "I told you so"

Couple of weeks ago I proposed integrating a daily process job into an existing WPF application (details of what+why would be too long to explain) and the manager suggested I make the changes

Me: "I can do it, but Jay has the most experience with that application. I don't have his WPF skills"
Mgr: "How hard can WPF be? If it uses the MVVM pattern, it should be a snap."
Me: "Its nearly an 8 year old WPF project with several chefs in that kitchen. I pretty sure I could figure it out, but that is a difference between 2 weeks and 2 days. Integration is pretty straight forward, Jay could probably do it in a day."
DevA: "WPF is easy. MVVM makes it even easier. I worked on the shipping app."
Me: "That's was a brand new, single page app, but yea, it should be easy."
DevB: "WPF has been around a long time and the tools have really matured. I don't understand what is so difficult."
Me: "I didn't say anything would be difficult, I know with that application, there is going to be complexity we need to figure out."
DevB: "It uses the MVVM, so all we need is the user control, a view model, controller, and its done."
DevA: "Sounds easy to me."
Mgr: "If you need more time to work on the vendor project, I'll have DevB work on the integration."

<yesterday>
Me: "How is the integration going?"
DevB: "This app is a mess. I have no idea how they got the control collections to work. If I hard-code everything, I can get it to work. This dynamic stuff is so confusing. Then there is the styling. Its uses dark mode, but no matter what I do, my controls show up in light mode."
Me: "The app uses Prism, so the control configuration is in, or around, the startup code."
DevB: "That makes sense. Will it fix the styling too?"
Me: "I have no idea. When I looked at it, some controls loaded the styles from the main resource, other's have it hard-coded. Different chefs in the kitchen, I guess. How far have you got?"
DevB: "I've created invoice button. That is as far as I got"
Me: "I'm finished with the vendor project and I'll be wrapping up the documentation today. I can try to help next week."
DevB: "Thanks. I think we might have to get Jay to help if we can't figure this out."
Me: "Good idea"

Two weeks and only a button. A button? I miss Delphi.

I quite like Unity.
It's a good engine, BUT....

I despise doing UI in it, it's just so tedious to make everything work and show up.
In the past I didn't mind but then I learned about XAML in WPF, UWP and Xamarin. XAML works very nice with the MVVM pattern (even if you do that lazily) with the data binding.

So now I'm working on my own data binding, which is both fun and saddening (because it's not in there already)

Ahhhh.. the great feeling of starting a new project at work after the stresses and health deterioration of maintaining old code bases.

!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.

Story time:

I worked at a firm that had an infernal off the shelf CRM system that they collaborated with the dev company to customise.

They were seriously behind the competition, and didn’t have any app or web presence for interacting with their system, instead relying on people calling (fine for the nature of the business, but competition was leaving them in the dust).

They decided that they needed to redevelop it in-house, with a focus on supporting the web and apps.

I was hired for this purpose.

It was me and one other dev, who was also the head of IT.

He’d built a small prototype, and was new to the whole WPF / MVVM thing for the in-house app, so with my previous experience it was clear it needed to serve as an example only, and that it would need redeveloping.

I was only there three months.

In that time I singularly (he was pulled away to troubleshoot their VOIP installation - yes, for three months as other companies kept dropping the ball) built:

- A WebAPI with JWT auth
- An MVC skeleton frontend
- A WPF desktop app

It had all sorts of cool shit in it, 2FA, Reactive UI, Reactive extensions, server push to desktop, a custom workflow and permissions system.

It was pretty dang cool.

End of the three months rolled around, and the non-technical managers were concerned about time to market, so they decided to drop me as I’d “not made enough progress”.

I’d also had a bit of absence which they were aware of and were supposedly supporting me through.

But MFW three months is assumed to be enough time to build such a system with one dev.

On Friday I was planning on working on getting the MVVM pattern down in C# and WPF. Today I watched episodes of Smallville all day. I seem to have a lack of motivation, but I guess it is the weekend. 😜

Curious interview process for a job I was denied for. I was told to create an app for a "case study" I was given a week it was supposed to be a single activity sports app written in MVVM with a specific API. I turned in a single activity, 3 fragment application, that made queries and displayed results from that specific API as well as told the weather and in quirky quotes told you whether or not it was a good idea to go tailgating. When I got to the interview after turning it in a day early they said they loved the application, hounded me on code (all questions in which I answered) and they told me that I would get word on next steps within the next few days. Obviously I didn't get that job as earlier stated however, does this not seem weird?

Been depressed and bored for the past two days, wish I'm always like this. why?
I learned how to MVVM in WPF and Android.
If only Apple creates something similar to what Microsoft and Google did for data binding.
If it exists please let me know :)

Really appreciating MVVM in android. It's doing wonders in my latest project as I double up on learning kotlin.

Started my first private App project using all the goodies of 2017 android development like TDD, Android architecture components (hence MVVM), kotlin (which I yet have to learn), RxJava2 (if I need it additionally to AAC) and maybe try to set up a CI environment.

Wish me luck guys and girls 😁

I need some opinions on Rx and MVVM. Its being done in iOS, but I think its fairly general programming question.

The small team I joined is using Rx (I've never used it before) and I'm trying to learn and catch up to them. Looking at the code, I think there are thousands of lines of over-engineered code that could be done so much simpler. From a non Rx point of view, I think we are following some bad practises, from an Rx point of view the guys are saying this is what Rx needs to be. I'm trying to discuss this with them, but they are shooting me down saying I just don't know enough about Rx. Maybe thats true, maybe I just don't get it, but they aren't exactly explaining it, just telling me i'm wrong and they are right. I need another set of eyes on this to see if it is just me.

One of the main points is that there are many places where network errors shouldn't complete the observable (i.e. can't call onError), I understand this concept. I read a response from the RxSwift maintainers that said the way to handle this was to wrap your response type in a class with a generic type (e.g. Result<T>) that contained a property to denote a success or error and maybe an error message. This way errors (such as incorrect password) won't cause it to complete, everything goes through onNext and users can retry / go again, makes sense.

The guys are saying that this breaks Rx principals and MVVM. Instead we need separate observables for every type of response. So we have viewModels that contain:

- isSuccessObservable
- isErrorObservable
- isLoadingObservable
- isRefreshingObservable
- etc. (some have close to 10 different observables)

To me this is overkill to have so many streams all frequently only ever delivering 1 or none messages. I would have aimed for 1 observable, that returns an object holding properties for each of these things, and sending several messages. Is that not what streams are suppose to do? Then the local code can use filters as part of the subscriptions. The major benefit of having 1 is that it becomes easier to make it generic and abstract away, which brings us to point 2.

Currently, due to each viewModel having different numbers of observables and methods of different names (but effectively doing the same thing) the guys create a new custom protocol (equivalent of a java interface) for each viewModel with its N observables. The viewModel creates local variables of PublishSubject, BehavorSubject, Driver etc. Then it implements the procotol / interface and casts all the local's back as observables. e.g.

protocol CarViewModelType {
isSuccessObservable: Observable<Car>
isErrorObservable: Observable<String>
isLoadingObservable: Observable<Void>
}

class CarViewModel {
isSuccessSubject: PublishSubject<Car>
isErrorSubject: PublishSubject<String>
isLoadingSubject: PublishSubject<Void>

// other stuff
}

extension CarViewModel: CarViewModelType {
isSuccessObservable {
return isSuccessSubject.asObservable()
}
isErrorObservable {
return isSuccessSubject.asObservable()
}
isLoadingObservable {
return isSuccessSubject.asObservable()
}
}

This has to be created by hand, for every viewModel, of which there is one for every screen and there is 40+ screens. This same structure is copy / pasted into every viewModel. As mentioned above I would like to make this all generic. Have a generic protocol for all viewModels to define 1 Observable, 1 local variable of generic type and handle the cast back automatically. The method to trigger all the business logic could also have its name standardised ("load", "fetch", "processData" etc.). Maybe we could also figure out a few other bits too. This would remove a lot of code, as well as making the code more readable (less messy), and make unit testing much easier. While it could never do everything automatically we could test the basic responses of each viewModel and have at least some testing done by default and not have everything be very boilerplate-y and copy / paste nature.

The guys think that subscribing to isSuccess and / or isError is perfect Rx + MVVM. But for some reason subscribing to status.filter(success) or status.filter(!success) is a sin of unimaginable proportions. Also the idea of multiple buttons and events all "reacting" to the same method named e.g. "load", is bad Rx (why if they all need to do the same thing?)

My thoughts on this are:

- To me its indentical in meaning and architecture, one way is just significantly less code.
- Lets say I agree its not textbook, is it not worth bending the rules to reduce code.
- We are already breaking the rules of MVVM to introduce coordinators (which I hate, as they are adding even more unnecessary code), so why is breaking it to reduce code such a no no.

Any thoughts on the above? Am I way off the mark or is this classic Rx?

My coworker, whom I attempt to mentor when I am not frustrated and impatient, is refactoring one of our smaller programs. It uses modern MVVM practices, unlike the dilapidated crap we inherited from my predecessor and the lazy asshole that was me 3 years ago. I am excited to see what he learns and what he can teach me, maybe he will finally understand my shortcomings as a mentor.

today's lesson:
one does not simply open a new window with mvvm pattern

Guys, do you know any good source to learn MVVM to android (kotlin would be nice). I know MVVM theory and practice (I used it in WPF, C#). But i have hard times understanding how it work with android. I watched reso coder, but his tutorials are even harder to understand. Thanks

How do you actually structurize _big_ projects and still use js components?

_big_ = more than 300 pages. Seriously. Not addtodo, listtodos and thats it. A huge fucken amount of pages.

Can any one explain to me the mvvm pattern ?

The MVP vs MVVM debate is making me have an object oriented crisis.

Using a 3rd part library to manage drag/drop in wpf and then have to use router events because it doesn't natively manage commanding for mvvm pattern, then you write a commanding behaviour which works perfectly for everything else except drag drop because it's not part of the visual tree so binging is a nightmare!! 😡😡😡😡😡😡😡😡

MVP MVVM RxJava, y u so complex? You supposed to make everything simple!

From HTML CSS javascript to some voodoo WPF xaml and c#, mvvm and databinding dependency inject cluster bomb to my brain god Microsoft just put a tutorial out like a normal group of people. where you do examples of projects. I'm 2 weeks in and this still makes no sense

It started when i was about 10 old.
My uncle showed me how to display something in dos-prompt using the echo command in a custom batch-file.
A few commands later, i was able to "program" a flip-book of an ascii ski-driver. Each ascii picture was separated by pressing any key and cls ^^
Aaaaah. Sweet childhood memories!

Later on i used a programming-language for beginners in windows.
This language gave you control of a triangle called "turtle".

My first high-level programming language was Delphi.
Since i had no idea of databases, i created a pseudo database of magic the gathering play-cards. Each card had it's very own windows formular filled up completely with an uncompressed image object displaying the chosen card modally. *sigh*
I scanned each card by using a feed scanner.
Finally, my application consisted of 200 cardimages and forced my PC to swap the required memory from my harddisk.
Boy o boy. I was such a noob! ^^

Over the years i discovered and felt in love with a lot of languages (jsp, java (script), c#, php, ...) and concepts (mvvm, mvc, clean-architecture, tdd, ...)! ;)

I've actually already discussed this one on here I believe

I see this job looking for an android developer for Kotlin with UI experience with XD & Figma and experience with Firebase. I have all of these qualifications so I throw my resume into the fray within an 2 hours the recruiters contact me. they have an offer of 76,000 and I'm looking for junior so I'm like, eh whatever, I give them a copy of my resume and we hold discussion for a few days and then radio silence. I then see a job posting EXTREMELY similar but with a "different company" so I throw my resume in and again within 2 hours I get a call only THIS TIME ITS THE INTERNAL HR. She sounds interested we have a good conversation and sets me up for 96,000 and they schedule me for my first interview within the week. Interview goes great, next I meet with the CTO and we have a pretty good conversation, I'm expecting a technical exam but it doesn't happen instead they give me a case study. they send me requirements for an app API to use, architecture, and a week time span to do it. I finish the app with extra features within 6 days, in my understanding of MVVM and I was excited and happy about this app because its JUST NICE. a week goes by and I meet with the tech team. They grill me on my application, scalability, use cases, how would I advertise or place advertisement and I'm answering everything they love the UI (I included mockups I made on XD), they say everything sounds good everyone leaves with smiles they say they have to find out on what team to place me because they have multiple apps and that HR will be in contact with me in the next few days... A WEEK GOES BY and I randomly get the declination email that next Friday. When I asked for feedback they said it wasn't true MVVM. I was devastated until the next week when I was accepted for a higher paying job that didn't require me to move. After I accepted this job guess who calls? THE FIRST RECRUITER and for this long I was wondering if this was the same job due to the very similar job description so I ask "is your client XXXXXXX?" it was I just told him "I'm good" and hung up

ok this may look like a lazy ass beginner crying out for spoon feeding( which it kinda is), but i want some real industrial training in non documented Android coding.

For last 2 years i have been reading tons of Android articles and documentation on "how to use this library", "how to add this feature", "what this function of this class does", but not much about how to use it efficiently, like the way its used in industry.

When I interned with a startup, all they wanted from me was to push new design changes, fix layout bugs and work as fastly as i could. I had no time to understand their core code, which had so many things that i could have learned : those mvp/mvvm design/architecture patterns, dependency injections, kotlin , coroutines, state management designs, data bindings, eventbuses and handling, and VIPER,RIBS (I mean, not everything was particularly in their code, i picked up a few keywords from here n there)... a lot of stuff that is used by many apps for their codebase.
I can read up these stuff by myself, but i always end up feeling bored coz frankly, i got no big/valuable project to implement it upon and feel excited about it. I feel that open source projects from OSS companies could be my window, but their chat spaces are also mostly empty to discuss/get some guidance.

I want some specific training about these. Can you guys provide any online/offline course/company training/books in this subject, the best practices?

My colleague got cycled. I asked him whether he had any previous experience with MVVM in C#. Response went something like: What is that? Another model view view view......controller? I sent him for another cup of coffee...

Some Coworker - developing about 20 years with WinForms and very ugly code.

Me - Junior Dev about 4 years now started with WPF and not long ago with MVVM.

Me trying to teach him some MVVM... Just frustrating. Like talking against a Wall..

Getting a headache now. I need a stressball -.-

Can you give me some tips on how to debug a massive app? (Android app running on android studio which is basically intellij idea).

For example I need to fix a bug where a certain action results in unexpected behaviour.

But oh my god the codebase is so large (mainly architecture is MVVM and rxjava) that searching for the specific place is like searching for a needle in haystack.

For example I added a breakpoint in few places, but I can see only like 4 or 5 last frames in the stack that led to the current action, last frame is a lambda which doesnt help me so frankly Im unable to even track where current event started. I am loosing my mind. I cant even find where the buttonclick action started because everything is reactive and done with observables which can be anywhere.

Any tips on debugging will be appreciated

If you could explain mvvm to me in what sentence. How would you explain it?

Copying files

Okay so there are a lot of things that are left by us students as "this would be taught to us on job, why bother now?" So i have many questions regarding this:

- is it a safe mentality? I mean University is teaching me, say a,b,c and the job is supposed to be like writing full letters, than am i stupid to stick to just a,b,c and not learning how to write letters beforehand?

- what is even "taught" on job? This is especially directed towards people in Big firms. I mean i can always blame that small ugly startup who treated me badly and not gave me any resources, but why do i feel its going to be same at every other company?

I guess no one is gonna teach me for 6 months on how to write classes with java, or make a ml engineer out of me when i don't know jack shit about ml.... That's the task for college, right?

I feel that when these companies say they "teach", you they mean how to follow instructions regarding agile meetings, how to survive office politics and how to learn quickly and produce an output quickly. I don't think that if i don't know how MVI works, then they are gonna teach me that, would they?i guess not unless they already have someone knowledgeable in that topic

- what about the things that are not taught in our colleges and we wanna make a career in it? Like say Android. From what i have experienced , choosing a career in a subject that's not taught you in grad school immediately takes away some kind of shield from you, as you are expected to know everything beforehand. So again, the same questions bfrom above

i did learned something from job life tho, and that too twice. Once it was when i first encountered an app sample for mvvm and once when i found out a very specific case of how video player is being used in a manner that handled a lot of bugs.

Why i didn't knew those approaches when i was not in job? Well, the first was a theoretical model whose practical implementation was difficult to find online that time and the second was a thing that i myself gave a lot of hours, yet failed to understand. However when i was in the company , i was partnered with a senior dev who himself had once spent 30 days with the source code to find a similar solution.

So again , both of above things could have been done by me had i spent more time trying to learn those "professional tools" and/or dwelve deeper into the tech. And i did felt pretty guilty not knowing about those...

When i code a prototype, am i supposed to code it in a strong e.g. MVVM architecture or to code it however i know possible?

Actually an IT company took my interview and gave me an assignment and it had to be submitted in 24 hours.. i submitted 50% of it..
And i thought many time but that task was not a work of 1 day.. any suggestions please..

!rant

Question: I am working on learning MVC/MVP/MVVM/MVPVM and I have read a bunch of articles and done some tutorials but I need some help relating it to n-tier (I think that's what they're called) systems.

I have worked on and I am used to the Presentation (ui) layer > BAL > DAL > DB pattern. How does MVC (and others) relate to the different tiers in a tiered system? I have read that model == DAL, controller == BAL, and view == presentation layer, but I have also read that MVC is meant to extract the presentation layer and that business logic and data logic should be used elsewhere. Can I get some clarity?

At first I got this crappy project which 400 users HAVE TO use but NO ONE WANTS to use - with ASP.Net MVC, ASP.NET MVVM (Yes, both!), KENDO MVVM, KENDO UI, JQUERY and not a single line of typescript or modern web framework...

After I told them, that was not why I was hired and not what I was promised, they told me in summer I will get this brand new project, not a single line of code written.

Every new project of my company in the last 2 years was in React / Redux / Typescript and ASP.Net Core WebAPI - So I invested a bunch of weekends to get into it to be able to lead such a new project!

Today I recieved a Email from my boss, that because "we have to be on the same stack as the sister-project" we will use jquery and kendo mvvm....

What the fuck...

I'm doing my final project for apprenticeship with mvvm. I hate all the preparation I have to do before I can start the real work.

Xamarin vs Flutter

I already know c# but I’m thinking it’s better to learn Dart + Flutter than carry on with Xamarin (only ever worked on the back end parts of Xamarin so not familiar with the layout syntax and the ui side of it).

Xamarin seems to be so clunky (to be fair more the dev environment than the end result), even on a powerful machine it’s a pig to work on.

Our project uses Xamarin forms, without any extra MVVM framework such as Prism and it just seems a bit shit from what front end code I’ve seen (could be the devs).

So given that I’m not sure that holding out for MAUI and expecting it to be a silver bullet is a good idea.

Is the UI code for Flutter any cleaner?
Is the dev environment more reliable?

Or is another option better, such as ReactNative or Ionic ?
(Particularly if one of those would let you develop an iOS version without access to a Mac)

Has anyone (good/bad) experience with knockoutjs? I am playing around with it now and i think it's a nice framework especially if you are familiar with the MVVM model.

FFS what is the standard with dependency injection with Android. Is it dagger2 or kodein. Last 2 days googling about and it seems like it's dagger2 yet others say it's kodein. Kodein is newer I guess so less written about it. Seems like every 2 weeks it's something new. No wonder I can't pick this up. It changes faster than Trump can fricken tweet.

Like first mvc then mvp then mvvm then mvi what's next mve? 😵

So flustered. As last post I feel like giving up. Every time you try to learn some new "standard" creeps out from CS major ass crack. Is it the same for IOS. Maybe I should sell a kidney for a Mac book.

Any good resource on how to create NuGet from wpf custom control with behaviors? I cant find anything thats somewhere near readable.... I want to make NuGets of CC and behaviors so i can easily implement in my exams and save time during developing 👍

I have recently learned to use data binding with recyclerView in android. I need to make some network calls on the click of a button at the recyclerView, and based on response I need to update my UI. All my code for the view is in my ViewHolder. Bt all the code for my network calls are in repository which is accessed by my viewModel. how can I make the network calls from the viewHolder?

Does anyone has experience with the VIPER architecture pattern on iOS and Swift? Or has a more experienced example project than a simple two views app? I’m currently using MVVM-C with router. I would like to still keep the concept of the coordinates in VIPER, is it a redundancy? A bad choice? or do I missed a part?