Yep, what @seancorfield said. I should have been clear that I'm contracting. But I meant that the project is a nice isolated chunk of work that could be done agency style by a team, the issue would be that a lot of these orgs want to own the code and the IP/maintain it themselves which is why they bring it in house.
We are sometimes doing contract work here in Germany (mostly non-Clojure, unfortunately). IP and code ownership is normally not a problem. It is quite common to agree on a model that fits both sides (perhaps at the expense of higher prices, e.g. for exclusivity). The typical model in such contracts is to grant unlimited, non-exclusive rights to the customer. The contractor then retains authorship and unlimited rights. However, practice shows that custom development results are hard to reuse at scale.
that's interesting. I guess it depends on the size of the org. current org I'm working into is 72k employees so they want all the cake 😂
Well, then they probably pay for it in hard currency, don't they?
Actually, from my experience size is not the dominating factor. It's rather corporate culture and general IT maturity.
Over-generalizing a bit: E.g. companies from the financial industry tend to exercise more secrecy, public sector orgs tend to be more open-minded.
yeah true, I've worked for agencies facing into govt/civil service before and that was more typical project based work
To be honest I’m interested in general =)… Even part time stuff could be doable, I just have to make sure I’m not signing IP on everything I do…
I think the contracting "culture" is different in every country as well, affected by local employment, tax, and IP laws. The US has been very different for me doing contract work here vs the UK, for example.
I was full-time contracting in the UK for about five years in the '90s and I've done about the same in the US at the end of the '00s. Of course, some of those differences may also be due to the passage of time (a decade is a long time in IT!).1💯
Completely agree with that =)…