Michielvv

Inscene Company | Utrecht, The Netherlands | Junior Developer | Partial Onsite/Remote | Interns can also apply

For Networkapp (http://www.networkapp.eu) and related apps we are looking for a junior developer. Depending on your experience you will work on either the app (C#) or backend (Python)

Inscene Company has a small team and you will be able to make a significant impact on the product.

There is some flexibility in hours e.g. part-time work.

It's possible to work remotely, but regular (at least weekly) office visits are expected.

We also have a position for one or two interns on related projects.

I currently work partly remote: I go to the office for one day a week (8hr) and work the other 12 hours from home.

I like this arrangement as the day in the office also gives me insight into what else is going on, besides my immediate tasks. For example I may pick up on something that my coworker is spending a lot of time on that could easily be automated or a client request that may influence my schedule.

On the other hand the time remote gives me a chance to focus on harder issues.

What I like about the part-time aspect is that I can choose to just work when I'm focussed. If things are not moving as I like, I just stop working. This is also the disadvantage, because that way work spreads out over more days than it would if I would sit in the office.

In general I think the jobs are there, but you will probably have to know someone at the company that is already aware of your skills. Maybe first starting out as a contractor on a smaller project. (Assuming you would prefer a long-term job over contracting)

Guess it is answered... yes... this breaks your auth flow... It is now mentioned on: https://developer.linkedin.com/support/developer-program-tra... as well, don't remember reading that before.

What I'm wondering about is, what will happen if you request certain permissions (e.g. w_messages / rw_groups ) as part of the oauth process, but do not actually call API endpoints that require them.

The documentation just mentions the limitation in API endpoints, but I'm a bit worried whether it could make the oauth login fail due to permissions requested that you can no longer use.

I've been on projects with both: For business like apps, Xamarin (Forms in my case) is miles ahead. Although Xamarin.Forms isn't really stable (We experienced quite a lot of regressions with each new version) neither is Corona.

Corona is nice if you have a lot of custom graphics, but if you are going for pretty standard user interaction, you will spend a lot of time recreating what exists on other platforms.

For both Xamarin.Forms and Corona you will run into the limitations, but with Forms it is much easier to adjust those with native code.

I think the main issue with Corona is that they are more focussed on the game case (for which it works)

Finally, I really started to appreciate C# after doing Lua, PHP and JavaScript for years. Especially on a complex app, the static typing really helps making changes to code you did not write yourself.

Yep, that was one of the first things I did to make it somewhat usable, but besides that: - it sometimes spontaneously re-aranges windows in a completely useless way - windows go blank, sometimes requiring to disable/enable the extension multiple times - it sometimes closes your chat windows with your unsubmitted messages if the internet is down - it sometimes keeps looking like you've got unread messages somewhere when you don't

But still the fact that I can use it on the desktop and the android client is pretty ok, makes me use it.

I've evaluated the beta last month and it is a really interesting technology. Especially now it has incremental state transfer, which allows nodes to catch up again (e.g. after a reboot). It has some rough edges, but the developers are really helpful and on top of things.

I have to disagree on taking a break every 20 to 30 minutes being in conflict with getting into flow. If I apply the Pomodoro method and set a fixed time for the break to start, I found that for me it's actually quite easy to get back onto the problem after the short break.

What I think makes the difference is that forcing the break, although annoying at first, makes you take the break when things are going well, resulting in eagerness to continue solving the problem after the break. While, if you take a break when you feel you need one, things are probably already stuck and it's harder to start up again.

I do agree with getting away from the computer for a proper break every few hours, but isn't that quite natural already? I can't go without eating/drinking for much longer than that anyway.