We are looking for a Delphi Software Engineer, near Strasbourg, France (no remote job possible, sorry).
We are looking for a Delphi Software Engineer, near Strasbourg, France (no remote job possible, sorry).
It would be to work mostly on a brand new cloud of servers, implementing SOA/REST best practices using the mORMot framework.
This is a very innovative solution, featuring horizontal scaling and high availability, following DDD and SOLID patterns, with no RAD design, but pure OOP + interfaces, using Delphi and FPC (Windows+Linux), over SQL and NoSQL databases.
Fell free to send me an email: jobsxb at synopse dot info !
It would be to work mostly on a brand new cloud of servers, implementing SOA/REST best practices using the mORMot framework.
This is a very innovative solution, featuring horizontal scaling and high availability, following DDD and SOLID patterns, with no RAD design, but pure OOP + interfaces, using Delphi and FPC (Windows+Linux), over SQL and NoSQL databases.
Fell free to send me an email: jobsxb at synopse dot info !
Is there a special reason why remote work is not pissible?
ReplyDeleteIt is not the common case this in the company - which is not Synopse, but the company I currently work for. It may be possible, but someone working locally would be preferred AFAIK.
ReplyDeleteRemote jobs are not yet well established in France...
A. Bouchez
ReplyDeleteI guess it will be difficult to find someone onside but maybe you have luck...
Some people are able to move for a good opportunity. I did it several times...
ReplyDeleteYes, but Strasbourg is not Paris...
ReplyDeleteLife quality is IMHO higher in Strasbourg.... But it is just my feedback - and I lived for years in both places... :-)
ReplyDeleteMaybe, but it must be easier to find someone in Paris.
ReplyDeleteRoman Kassebaum IMHO Delphi jobs are a small market, so offers and appliances are also in small number, even in Paris. The hardest is to find something exciting, e.g. a new project like ours. Most of the offers are about maintaining a legacy system, or converting it to other technologies. Both may be very frustrating, and the 2nd option, which is very common, due to managers lack of vision, is IMHO a wrong idea. Paying inexperienced developers in mainstream technology just because it is mainstream and C#/Java developers are easy to find, makes sense from the "project" point of view, but it sounds to me like ignorance of what developing actually is.
ReplyDeleteIn fact, we have some candidates in Strasbourg, but I just wanted not to let the opportunity be missed by anyone in this G+ community.
A. Bouchez
ReplyDeleteWhat I mean is the following: Strasbourg might be a nice city with a high living standard but it is not the middle of the Delphi world. With insisting on onside work you cut the number of potential candidates form the first.
I believe, in eastern europe you will find enough good Delphi developers, who are willing to move to France.
ReplyDeleteThe technical approach sounds like a dream. If only RF had not such high taxation.
ReplyDeleteOliver Funcke
ReplyDeleteHow is the taxation at the place where you live?
~25% but in many cases possibly much lower.
ReplyDeleteOliver Funcke
ReplyDeleteThis is about the half of the German taxation. How is the taxation in France?
You can live in Germany, and work in Strasbourg. Just the river to cross. ;)
ReplyDeleteIn France, private taxation is increasing (0-10K€=0%, 10-27K€=14%,27-70K€=30%, then up to 45%). Plus CSG/RDS (8%). Plus other little things...
And the taxation of the employer (and the employee) on the pay receipt is also very high.
But we have a very good social system, especially in Alsace (Strasbourg area), even much better than "inside France".
I think le GD de Luxembourg is unbeatable when it comes to taxation as well as the social system.
ReplyDeleteA. Bouchez
ReplyDeleteI read an article a few days ago about chip fabrication in the 1970s. It turned out that all of the major fabrication plants were (unknown to them) buying their diamond-tipped saws from one company. That company turned out to literally be one man working from his garage! When he got sick, world-wide chip production was actually affected!
Enterprises are not short-sighted for preferring mainstream solutions. It's to avoid the "single vendor" nightmare. You don't want to use technology that very few people understand (unless it's providing amazing benefits) nor do you want to use a single vendor for your technology (as chip fabricators learned the hard way). Delphi is older, expensive, single-source technology with enterprise-unfriendly licensing and support. For all these reasons it makes sense for enterprises to prefer mainstream solutions.
One of the biggest benefits you omit is "ecosystem". While you are a gem in the Delphi world (and in a sense a "single source" for enterprise-oriented Delphi libraries yourself) the ecosystem is still a fraction of what it once was. The books, magazines and courses are gone. Pascal was last used for AP computer science in 1998 or 1999 - a whole generation now has never seen a line of Pascal and there is precious little to teach them with. Libraries are also a tiny fraction of what they are for more mainstream languages and Delphi's package management is in its infancy. With C# or Java there are "off the shelf" solutions, often open source, for almost any need. I did some math this weekend courtesy of a website that tracks package totals for many languages' package websites. Over the last two weeks, I counted a total of 8 new, free or open source libraries added to Torry.net. During the same period Python's package repository added a total of approximately 685 (about 48 per day)! Java added 83 per day, and node.js an amazing 263 per day!
Ecosystem arguably is the biggest benefit of mainstream languages.
As regards "ignorance of what developing actually is", I've heard one tech CEO say that he tells his developers "I hate code and I want as little of it as possible in our product" (it's a software product).. :-) The job of (most) developers isn't to write code - it's to solve problems. Mainstream languages like C# and Java let developers turn out code reasonably quickly with less chance of bugs than some lower-level languages (such as C++). Clean, clear, maintainable, (possibly) portable, performant, and future-proof code... that's what developing is for most enterprises.
Joseph Mitzen You are perfectly right about the single source syndrome, and also the lack of Ecosystem - even if the Delphi community is still alive, and quality (e.g. in G+) is very high, higher that what I found in C# for instance.
ReplyDelete"Clean, clear, maintainable, portable, performant, and future-proof code" is highly controversial, and I honestly laughed when I read this, and think back about the Java or C# code I've seen in some enterprises I worked for... And how many money was lost because of a .Net runtime unattended upgrade which broke a server, or what we were forced to install our own JVM to ensure that there won't be any conflict...
If the job of developers is to solve problems, it will eventually add more problems to the software, since it will always add complexity and logical connections between components. :)
The lazy path of solving problems may be good, e.g. as proposed by the Agile Manifesto, but it needs skilled developers.
I can tell you that the CEO you talked about would be intereste in our current project: the code base of the project itself is very short (just the business logic with a little plumbing, in a DDD approach), thanks to all the features available in mORMot - this is one of the benefit of the "convention over configuration" design, which made RoR popularity. Definitively shorter of what you may need with a classical WCF/J2EE stack.