UK-AL

35 ms·

391.
by UK-AL 9y ago
A domain can become more about behaviour, intergration and business proccess. Rather than pure data. I find most SQL languages are not particularly great for general purpose programming. Especially tooling for testing.
392.
by UK-AL 9y ago
Well we have gone past the point where running on a simple master/replica database is an option. We are distributed.
393.
by UK-AL 9y ago
It's depends on your domain. However most domains are just as much about behaviour and data then just data. Bugs are just as likely to occur in the database programming language as they are in application logic. In fact i think tooling
394.
by UK-AL 9y ago
Well those layers are really protecting the domain.
395.
by UK-AL 9y ago
Well if you model your domain, then if you find only a certain database can persist that domain well, then write a specific adapter for that database and stick with it. If your using DDD + OO most of the adapter will be converting to and fr
396.
by UK-AL 9y ago
Anything where there is calculations, multi-step business process, regulations, complicated business language which takes time to understand is in use. You first step in implementing in a feature is understanding the business domain with th
397.
by UK-AL 9y ago
My raw sql can call out to stored procedure if that's the best tool for the job. A database is a perfectly good application core, if you application primary about creating/updating/deleting records. If your application is bus
398.
by UK-AL 9y ago
You can leverage whatever database feature you want, just a long as you do it in the database adapter/gateway. I write mine in raw sql normally.
399.
by UK-AL 9y ago
I don't think the main advantage of this is switching databases. It's switching mindset. Lots of developers think database first, then build on top of that. That's good for simple crud apps. Creating/updating/deleti
400.
by UK-AL 9y ago
I don't think the main advantage of this is switching databases. It's switching mindset. Lots of developers think database first, then build on top of that. That's good for simple crud apps. For complicated apps you should th
401.
by UK-AL 9y ago
Lots of ways. You can look into agile and xp methods like user stories, story points, backlogs, user story mapping.
402.
by UK-AL 9y ago
I don't why it would be insecure...
403.
by UK-AL 9y ago
A lot of these architectures assumes DDD. (I'm not sure if clean architecture does) Domain driven design. You model you business problem using plain objects and methods. The domain should do nothing else other than modeling the domain,
404.
by UK-AL 9y ago
Clean architecture in this case is just the name of the architecture. There are many others.
405.
by UK-AL 9y ago
Another benefit is getting database stuff out of your domain code, makes solving the business problem a lot cleaner. In fact i just write a domain model, solve the problem, then write database adapter to persist the domain model. I always t
406.
by UK-AL 9y ago
Unfortunately I don't think interviews are a good tool for working out someones suitability. Interviewers have so many biases and pet interests. If you happen start talking about something technical(Some side project using x technology
407.
by UK-AL 9y ago
People who actually know how to build distributed systems would understand transactions and indexes.
408.
by UK-AL 9y ago
Compared to the technologies people learn today, .net is a glacier.
409.
by UK-AL 9y ago
"Tangible examples? I remember well the insistence of one boss that we use TFS because some developers would find it hard to use git. I remember the steadfast committal to ASP.NET web forms because the "new concepts" in ASP.N
410.
by UK-AL 10y ago
Running a small software business (5 - 10 people) in some niche area.
411.
by UK-AL 10y ago
I was under the impression, that linked lists are quite common in the Linux kernel.
412.
by UK-AL 10y ago
This is literally a textbook example survivorship bias. I have known people start companies who do everything right. Have studied all literature, hired great people. Still failed. I have known who do have the first clue about running busine
413.
by UK-AL 10y ago
She would have never of called if she thought she wasn't going to win. This is basically to get a higher majority in the commons, so things can go through unimpeded.
414.
by UK-AL 10y ago
Well agile techniques recommend you don't fix scope, and budget at the same time. Allowing you to go back fix your code that has turned out to be wrong. You're allowed to learn and to adjust your plan as you go a long. Waterfall p
415.
by UK-AL 10y ago
The reason for technical debt is the process. If you have a very waterfall like process like at a lot of large companies, everything has to go through change control. Every change has to have business case, and becomes very bureaucratic. As
416.
by UK-AL 10y ago
Well they've gotten kubernetes running on azure.
417.
by UK-AL 10y ago
DDD is basically more of a code first MDD. It's still very much in vogue. I do like DDD, the idea that you have a project that is completely focused on solving the business issues. Then the infrastructure/technology concerns simpl
418.
by UK-AL 10y ago
There are probably millions of people who had just as strong belief as musk, or jobs and failed. You just don't hear about them.
419.
by UK-AL 10y ago
Kubernates for windows containers is coming.
420.
by UK-AL 10y ago
Well the particulars of what taught is exactly the difference. In computer science you will learning about generic concepts like parsers, compilers or whatever. For vocational you would learn about something specific like asp.net mvc.

More ›