During an employment speed-dating event this recruiting agency saw my resume for three minutes then said that they had a six-month mission that could be well suited for me to do. They said I needed to know Qt and when I said that I didn't know it, they said that it was "just a library" and that I could adapt.
Of course I can always learn on the fly (I'm familiar with WxWidgets for example) but I'm kinda worried that the agency is trying to sell my profile (which they don't know well) for a project that they don't know either.
What does one do in such a situation? I'd like a meeting with the client so as to ask all the good questions, what would one ask in order to be sure that this project won't fail miserably?
Of course its possible to learn a new library or framework on the fly, but Qt is a really advanced one.
It's a huge framework with a lot of quirks.
I think asking for a meeting with the customer is a good idea. You may also express our concerns more explicitly to your agency.
Really tho? Because if I wind up in a team with other Qt devs, they're gonna know immediately
I don't intend to fake it tho, I intend to say "Never used, it, but I've use WxWidgets"
>It's a huge framework with a lot of quirks.
What would be a good point for saying "I'm kinda familiar with it"?
At what point can I claim to "Know Qt"?
I've got a week ahead of me
>asking for a meeting with the customer is a good idea
Any idea of important questions I might want to ask specifically?
>You may also express our concerns more explicitly to your agency
Hopefully that might help also
I'm concerned about this situation because I've had it before where some guy I was working for sold himself and me as experts on a certain topic. The lie was so big that I had to quit the job before the mission started, which is good for me because my ex boss himself turned out to be quite sub-par to say the least and really lost face in front of the client
You definitely should take a look at Qt's resource managemant. It's in some cases quite different than what you would expect from C++.
A basic understanding of the widget/layout principle would also be good.
If you ganna develop a QML application you don't have to worry about this.
Most of the components however are quite intuitive. And the documentation is really good.
I think >>50793949 would be a good approach.
thanks for the pointers, I'll look in those directions
>You definitely should take a look at Qt's resource managemant
Any specific examples off the top of your head?
Is Qt designer worth a shit at all or is it better practice to do VisualStudio + Qt?
E.g. Qt nearly always works with pointers so when i first started out i thought i would have to delete every one of them.
But if you pass e.g. a widget ptr to an layout, the layout takes ownership ower the widget and is responsible for its destruction.
There are more situations like that.
I'm not an expert in Qt however. I'm too still learning to use it for a university project.
I've never used VS+Qt so i can't judge the setup but QtCreator and QtDesigner are pretty good!
Sweet, thank you for your answers
Concerning independent contractor / consultant work, what would be some general do's and don'ts or general advice? I've only worked as an employee in large teams before
>Concerning independent contractor / consultant work, what would be some general do's and don'ts or general advice? I've only worked as an employee in large teams before
For example, is it acceptable to socialize with the client's team members, or is it better to keep distances?
In my old company it was good form to ask people about what they were working on, so as to exchange ideas and potentially bring in new insight. But maybe as a contractor this could be seen as a potential confidentiality breach?