[flagged]
I feel like I made a mistake investing professionally into Flutter
11–20 of 308 posts
Re: I feel like I made a mistake investing professionally into Flutter
#12Are mobile stacks so specialised that it's difficult to switch between them? Out of curiosity, how long would it take a flutter dev to become productive in some other stack?
They are not, but HR / hiring managers are keyword based and won’t entertain the idea of hiring someone with the wrong experience. See also: https://versastudio.com/blog/if-carpenters-were-hired-like-p...
It's the same in every other stack/programing language/technology when you go through the default channels of HR/recruiters.
It's not that competent engineers can't become quickly productive in a new/stack language, it's that business don't understand that and/or don't want to risk it with switchers, and so prioritize hiring only those already experienced in that stack, creating employment bottlenecks where there's simultaneously a shortage and enough people willing to switch.
Same when talking to recruiters: "oh you only have experience in X (which is similar to Y), sorry but the hiring manager said (s)he wants someone with at least 3 years experience in Y".
Your only escape is having a solid network so you can push your resume directly to hiring managers who understand technology and your adaptability, and this way bypass the hiring shit-show.
Re: I feel like I made a mistake investing professionally into Flutter
#13[flagged]
It's the same in most of Europe too. Employers are picky with who they hire.
Re: I feel like I made a mistake investing professionally into Flutter
#14[flagged]
What does this have to do with the original post?
Re: I feel like I made a mistake investing professionally into Flutter
#15I don’t buy it. As software developers we learn technologies for breakfast. We learn them, and then we forget them. We recollect the wisdom gained and apply it in our next gig using a different technology. It works for mobile development, for frontend, for backend, for infra, for almost anything.
I have worked for years with PHP, Apache, Ansible and MySQL. Nowadays not anymore. And in 7 years I’ll be using something else. Learn the fundamentals (which is not a one-time job, btw) and you’ll be fine. If someone asks for technology X in their job offers when you know Y, but you know you won’t have difficulty in learning X, just take a few days in learning X and then put it in your CV. You’ll get pass HR screening and then you’ll have a chance to explain in tech interview that your are more of a technology-agnostic dev. You’ll do fine.
Re: I feel like I made a mistake investing professionally into Flutter
#16Obviously I feel the pain of the OP but I think he blames the wrong thing. Flutter is a ( viable ) technology that’s being growing for the last few years. A very significant percentage of new mobile apps are programmed with it these days. It seems his problems have everything to do with the local job market and not the technology. With the added bonus that you can be a single man operation and release your own apps f…
Flutter is pretty old if you think about it and still has too many rough edges and not a lot of big name adoption. The project is too ambitious, and the features seem more like PoCs than something you can rely on in production, IMO.
Re: I feel like I made a mistake investing professionally into Flutter
#17You could say this about any Google technology.
I know right? Just like Golang, Kubernetes, Chrome APIs, etc /s
They're even keeping GWT alive somehow. That was a major mistake, though. I remember building a large GWT project and the compile times just started getting into multiple minutes. Debugging was hard.
Re: I feel like I made a mistake investing professionally into Flutter
#18Are mobile stacks so specialised that it's difficult to switch between them? Out of curiosity, how long would it take a flutter dev to become productive in some other stack?
They are not, but HR / hiring managers are keyword based and won’t entertain the idea of hiring someone with the wrong experience. See also: https://versastudio.com/blog/if-carpenters-were-hired-like-p...
C’mon. HR doesn’t have a clue of what they’re asking for. Anyone with a little of experience in the IT industry knows that:
1. You’ll need to put whatever is needed in your CV to pass through HR
2. You can explain yourself to the actual tech people who interview you in the next stage. For example, if you know Ruby and RoR, but there’s an excellent opportunity to work in a cool product for a company that does Python and Django, well, apply! Obviously you’ll spend a couple of days with Python and Django and notice the similarities and differences with Ruby and RoR. You will add to your CV the keywords Python and Django and you’ll get pass HR (if HR asks you about your experience with such tech stack you can always say that, indeed, I have plenty of experience with MVC web frameworks and blah blah blah). When you pass to the next stage of the interview and get to talk to real engineers, then you can explain that you have many years of experience working with RoR and that learning Django will be a pleasure.
Re: I feel like I made a mistake investing professionally into Flutter
#19Dart is my biggest issue with Flutter. It's still missing ergonomic features like data classes and lower level things like unsigned 64-bit integers. There is no runtime reflection, which I think is a good thing for end user apps, but it's also missing static metaprogramming. And code generation is not integrated into a complier. Since, there is no runtime reflection, metaprogramming & integrated code-gen are sorely n…
It may lack things - true. But it's a pleasure to work in. I code quite a bit of Dart these days and the language never really holds you back. It flows quite easily. I use some code generation by having a build runner in the background.
Re: I feel like I made a mistake investing professionally into Flutter
#20I don’t buy it. As software developers we learn technologies for breakfast. We learn them, and then we forget them. We recollect the wisdom gained and apply it in our next gig using a different technology. It works for mobile development, for frontend, for backend, for infra, for almost anything. I have worked for years with PHP, Apache, Ansible and MySQL. Nowadays not anymore. And in 7 years I’ll be using something…
I agree, but unfortunately hiring managers, recruiter etc. don't think like this. If you happen to find a person that is tech-savy, they can asses your true skillsets and capabilitiy of solving problems. Hiring managers and recruiter match buzzwords in your CV.
I recently got rejected for a project from an agency (am a contractor) because I did not have provable skills or knowledge in "CI/CD". Stupid me, made the mistake of putting extensive details about creating build and deployment pipelines with Travis, GitLab, GitHub Actions, Azure Pipelines for each past project going back to 2012, but did not specify the right buzzword "CI/CD" for the recruiter...