We are a tiny bit miffed at some missing features, though (especially in System.Reflection.Emit).
656 karma · joined February 18, 2011
We are a tiny bit miffed at some missing features, though (especially in System.Reflection.Emit).
public readonly ref struct Span<T>
{
private readonly ref T _pointer;
private readonly int _length;
...
}
But the important parts are not _pointer or _length. Most of the implementation effort went into the `ref struct` part, which was released at the same time as Span<T> and is precisely what makes Span<T> powerful. It is a big thing.For public and almost-public organizations, there is a regulation: you can communicate in exactly one language (French) or at least three languages (usually these will be English and German).
On the other hand, trying to sell to the average French person will require a French translation, and the same is probably true for most other EU countries if you wish to improve your chances ("have a translation in that language" is likely in the top 5 of improvement suggestions for a new market). 300 million people sharing the same language is a boon, especially for B2C or B2SMB.
The traditional publisher takes almost all the financial risks : they pay for editing, type-setting, marketing and for the initial printing run of the book, without any guarantee that sales will cover the investment. Bookshops do buy the books, but they are allowed to return unsold inventory after a while, and the publisher takes the loss.
With a self-published author, who shoulders the risk of printing a copy and delivering it to bookshop shelves ? For CreateSpace in France, that's 15€-ish. The author can't, the bookshops won't, and the traditional investor (the publisher) is out of the equation.
- You must kill me, Ioannes (vocative: John must kill you)
- You must kill me, Ioannem (accusative: John must be killed)
But if strong consistency was abandoned because someone wrote general statements in favor of eventual consistency...
It does change the scaling math, but don't automatically assume that every ES+CQRS system is intended for thousand-writes-per-second, terabytes-per-day kind of scales. If the system stays at ten-writes-per-second, megabytes-per-day, a read store (beyond in-memory projections), a queue or an indexer are not necessary.
As for asynchronous error handling, and delays between reads/writes : why would that be a consequence of ES+CQRS ? It would be a consequence of implementing ES+CQRS with asynchronous or eventually consistent behaviour...
Even without asynchronous read/write, there are still benefits worth the (arguably, small) additional complexity. For instance, the ability to add new functionality without having to migrate existing data is amazing.
- Car 1 and 10 are engines, and include some second class seats. - Cars 2 and 3 are first class. - Car 4 is the bar-restaurant. - Car 5 is first class. - Cars 6, 7, 8 and 9 are second class.
All the infrastructure is designed to treat the train as a single unit, during all operations at the shunting yard, in repair workshops, and son on.
And the position of toilets (including special toilets for nappy changes) is fixed.
It is also not illegal to require visitors to clarify to which data processing they consent to (GDPR only says that if you require consent for processing that is not necessary to provide the service, then that does not count as consent for GDPR purposes).
"To have legal control over your PII" and "To have legal control over your possessions" are similar in nature. The fact that such purposes are implemented in different ways, for mostly technical reasons, does not diminish the argument.
The main technical reason is that, right now, loss of control over PII is widespread, and individually processing each claim would likely overload the judicial system of EU countries which usually don't have class action lawsuits. GDPR simulates a class action lawsuit using regulatory bodies, to be triggered by refusal to comply with a significant number GDPR requests.
My employer does supply chain optimization, because many "average" businesses have supply chains that need to be optimized. We have specialized AI tools based on deep learning and differential programming, and we have human supply chain experts that can fit those tools to the specifics of a customer's situation.
I would say that despite our best marketing efforts, many of our customers don't know that we're doing this "AI" thing they've been hearing about.
The anti-pattern with "Do we hire some AI guys?" is that, if you have to teach those guys how a supply chain works, you've already lost. Pick someone who is already specialized in the problem you're trying to solve.
S[ x ↦ V ]
indicates that the new state is equal to old state S, but with variable x now bound to value V.
Lokad is a software company that provides inventory and price optimization for customers in retail, aerospace or manufacturing. We are profitable and growing fast. We are closing deals in North America, Europe and Asia. The vast majority of our clients are based outside of France.
As a C# developer, you will join a team of talented software engineers in order to further develop our Big Data analytics environment : an in-house programming language and its modules for data import, export and storage, probabilistic forecasting, linear programming, and data presentation. We have infrastructure, data processing, scalability and reliability challenges, and need your help in addressing them.
At Lokad, you will benefit from the coaching of an awesome dev team. You will gain skills in large-scale data processing, domain-specific language design and cloud computing apps. Our codebase is clean, documented and heavily unit-tested. Located in Paris, 50m from Place d'Italie, our offices are quiet (no open space!), bright, and you can get three monitors.
We are a C#/.NET shop, and you will be developing under Visual Studio, the source code being versioned in Git. Our apps are hosted on Microsoft Azure. In addition, with the arrival of .NET Core, we also anticipate a few strategic migrations towards Linux.
We expect you to have strong software development skills. As a bonus, we appreciate people with a taste for low-level high performance computing, for compiler design and implementation, or for distributed systems. Contributions to open source projects are also highly regarded.
You can reach us at contact@lokad.com
Moving to a different environment where those techniques are no longer as effective will result in lower productivity for a while. Moving to an environment where those techniques can no longer be used (no type-checking, no ability to unit test) results in frustration, bargaining and hopefully acceptance, but the end result is that everyone stays on their side of the fence depending on whether they identify as "relies on type-checking to ensure correctness".
By the way, funny how sometimes, we get something out of bargaining (TypeScript because there is no type-checking in JavaScript, Selenium because there is no unit-testing in graphical user interfaces).
The same principles would be at play if you were letting a friend store their bike in your garage on weekdays. One tuesday in April you call them to say "I need to paint the garage in June, come and get your bike". But they're out of the country for the week, so the next day you throw away the bike.
You would have the legal right to clear out your garage, you had no signed contract to rent out a space for your friend's bike, but the way in which you did it caused your friend to lose their bike after you had given them a reasonable expectation that they wouldn't, and you had no good reason not to wait until the end of the week.
This doesn't mean that you own that home or office.
The general principle is that you can do what you want with your property, but you must pay for any damages you cause in doing so.
The important question is whether you did cause those damages (maybe it was someone else's fault, or maybe the damages were inevitable and would have happened regardless of your action or inaction, or maybe you acted in good faith like any other person would have) which gives judges plenty to think about.
Lokad is a software company that provides inventory and price optimization for customers in retail, aerospace or manufacturing. We are profitable and growing fast. We are closing deals in North America, Europe and Asia. The vast majority of our clients are based outside of France.
As a C# developer, you will join a team of talented software engineers in order to further develop our Big Data analytics environment : an in-house programming language and its modules for data import, export and storage, probabilistic forecasting, linear programming, and data presentation. We have infrastructure, data processing, scalability and reliability challenges, and need your help in addressing them.
At Lokad, you will benefit from the coaching of an awesome dev team. You will gain skills in large-scale data processing, domain-specific language design and cloud computing apps. Our codebase is clean, documented and heavily unit-tested. Located in Paris, five minutes from Place d'Italie, our offices are quiet (no open space!), bright, and you can get three monitors.
We are a C#/.NET shop, and you will be developing under Visual Studio, the source code being versioned in Git. Our apps are hosted on Microsoft Azure.
We expect you to have strong software development skills. As a bonus, we appreciate people with a taste for low-level high performance computing, for compiler design and implementation, or for distributed systems. Contributions to open source projects are also highly regarded.
More information here: http://www.lokad.com/software-engineering
You can reach me at victor.nicollet@lokad.com (I'm the CTO)
Our hiring process starts with a phone interview and there's a quick technical discussion (mostly there to avoid wasting time if the candidate's skills obviously do not match what we need). A live coding exercise is hard to set up and takes a while to perform, if only because the candidate needs some time to understand the question and gather some elementary insights. So, instead, I ask the candidate to explain some code that they have written, and I expect them to be articulate and knowledgeable about it.
So I want to be able to find a commit or file that can serve as a basis for an in-depth discussion relevant to the kind of work that the position involves. If I'm hiring for web front-end, then client-side JavaScript will have to be involved. If I'm hiring for Big Data, then high-performance code, low-level code, or distributed/parallel code will be good. If I'm hiring for Compiler Design, then a toy (or non-toy) compiler is nice.
I will tell the candidate ahead of time about the commit/file that I find interesting (or even ask them for pointers to help me pick one). That way, if they join me on the phone interview and have no idea what their code is doing, that's the end of the line.
I don't really care about code quality. Obviously, if the code is so bad that it's impossible to understand, that's bad news, but most of the time the code is readable, it's just missing comments, or has variables like `item2`, or functions that are too long, or other stuff that you would expect in an open source project. That's fine, because it leads into two very powerful questions in this type of interview: "Are you happy with the quality of this code?" (the correct answer is "no") and "If you had a few weeks just to improve this project, what would you do ?" (I expect insights about refactoring, or improving test coverage or even improving testing/validation strategy, or adding comments).
The idea behind this library grew from our pains with Irony (a grammar description DSL embedded in C#) when converting from its weakly typed AST representation to our own strongly typed AST.
Like tool-generated parsers, the parsers written with this library cannot encounter type errors at runtime. Unlike tool-generated parsers, there is no preliminary build step required to turn the grammar description into C# code. Instead, the library extracts the grammar description through reflection.
If you have any questions, ask away :-)
The point of the article (and I'm surprised that it takes them so long to explain it) is that regardless of the blockchain building process you choose, the entities responsible for adding blocks to the blockchain form a highly competitive market, and in these kinds of markets the costs grow very close to their expected income.
For Bitcoin, those entities are the miners, and costs grow because if you don't buy the latest high-powered hash-nozzle, your neighbor will, and your expected revenue will drop. It's an arms race that only stops once the costs exceed the revenue, meaning that most of the revenue from each block dissipates into electricity and hardware, and the electricity and hardware that doesn't contribute to a block is waster.
But even for a different blockchain model, designed to not waste anything, the same thing would happen: block-adders are incentivized to spend as much money as possible to increase their slice of the pie. In the end, the same amount of money (the revenue for a block) would still be spent in electricity, hardware, bespoke lava lamps or golf sessions with senators, anything that lets miners get one step ahead in the arms race.
Of course, if you were to drive down transaction costs, the available revenue for each block would go down, and the amount of wealth that can be wasted would decrease as well.