Why are people so obsessed with hyper specializing in software development? Labeling yourself a react dev or rails dev or flutter dev or whatever is only going to limit your growth and options. Your career will outlive many tech stacks. Tech changes quickly. Never stop learning.
Because recruiters. The person with one year of experience selling cellphones who now does the phone screen needs to see the exact tech listed on a resume or they pass.
I feel like I made a mistake investing professionally into Flutter
231–240 of 308 posts
Re: I feel like I made a mistake investing professionally into Flutter
#232I 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…
>don’t buy it. As software developers we learn technologies for breakfast. This is such a funny mantra. Okay learn how nuclear fission works. Or EUV lithography. Or power transmission across superconductors. All of these are extant, commercial, technologies (yes even the last one). Too much? How about something more pedestrian like overhead cams and electric fuel injection? Too far afield? Okay learn how DMA works on…
Re: I feel like I made a mistake investing professionally into Flutter
#233Earlier quoted context omitted.
Google can hire separate developers for each platform and pay them, investing millions of dollars into their mobile app. Can you afford to spend money developing same thing twice forever?
I worked for a midsized health care company a few years ago (around 300 people including customer service). They had three mobile developers who supported the iOS app and the Android app.
Similarly there were 3 iOS devs.
The feature set was enormous but we did fine.
Re: I feel like I made a mistake investing professionally into Flutter
#234Earlier quoted context omitted.
And the other part of “leading the team” is being able to mentor juniors and help them technically. What good is a lead if they can’t answer technical questions and can’t help other developers with technical guidance? What will it do for team morale on your iOS team when they know you bought in a “lead” who couldn’t actually help them with the tough technical problems?
The team has a culture that knows full well someone is brought in for who they are ... what they know might need some catch up. I'm not saying this is right in all circumstances. I wouldn't do this with, for example, realtime embedded. For what I operate in, fairly bland web applications and stacks. It works fine, exceptions excepted.
Re: I feel like I made a mistake investing professionally into Flutter
#235parsing JSON in Flutter seems like A LOT https://codewithandrea.com/articles/parse-json-dart/
Re: I feel like I made a mistake investing professionally into Flutter
#236Earlier quoted context omitted.
This is what has prevented me from diving into Flutter for a personal project. Although it supports desktop and web, it is first and foremost a tool for building mobile applications. For desktop, too much of the API is built around the assumption that you are on a mobile device with a single window and a finger as the pointing device. Feature requests for desktop, such as proper support for mouse-based drag and drop…
What do you mean by mouse based drag and drop? As far as I can tell Draggable and DragTarget work fine on windows and macos at least.
Re: I feel like I made a mistake investing professionally into Flutter
#237Earlier quoted context omitted.
You're saying that in isolation. If you have 50 other resumes on your desk for a React job, there's no way you're going to choose the guy who hasn't touched front-end since 2012.
I’ve done this exact thing. Stop telling people how they’d act.
I kid.
Re: I feel like I made a mistake investing professionally into Flutter
#238Earlier quoted context omitted.
>don’t buy it. As software developers we learn technologies for breakfast. This is such a funny mantra. Okay learn how nuclear fission works. Or EUV lithography. Or power transmission across superconductors. All of these are extant, commercial, technologies (yes even the last one). Too much? How about something more pedestrian like overhead cams and electric fuel injection? Too far afield? Okay learn how DMA works on…
You're just arguing semantics. And the example given can go the other way: if your Ford motor plant closes and the only places hiring are software shops, you'd also be "fucked".
I never have any clue what this retort means: when exactly are semantics (the meanings of things) not important?
> Ford motor plant closes and the only places hiring are software shops, you'd also be "fucked".
That's one hundred percent true but the difference is I don't see assembly plant workers going around claiming they learn technologies for breakfast (or lunch or dinner).
Re: I feel like I made a mistake investing professionally into Flutter
#239Earlier quoted context omitted.
The team has a culture that knows full well someone is brought in for who they are ... what they know might need some catch up. I'm not saying this is right in all circumstances. I wouldn't do this with, for example, realtime embedded. For what I operate in, fairly bland web applications and stacks. It works fine, exceptions excepted.
The team has a culture where the leads know less than they do and they are okay that?
I think that for architecting systems that's probably true, but as technology becomes more specialized and ecosystems become more complex it's harder for individuals to pick up and run with.
Consider if someone has written lots of PHP and jQuery
Now tell them to write a NodeJS server, React Frontend using NextJS.
It's not just "Oh I need to pick up ExpressJS" anymore. It's a whole beast.
Yeah the fundamentals stay the same. REST is still REST, SQL is still SQL, but actually writing lines of code is still a key activity of the job which people familiar with the technology will be better at.
Personally I run into this any time I try and write C#. There's a massive undercurrent of stuff that I feel I don't understand about C# and I bounce off that ecosystem every time I try