Reputation
30,015
Next tag badge:
97/100 score
21/20 answers
Badges
3 63 110
Newest
 Enlightened
Impact
~1.1m people reached

Jun
25
comment How to reduce reworking?
you already know how to do it - plan your design upfront. That you're not too good at this is another matter, but you will get better at it through practice and experience. Then, when you have these skills, you too can tut, shake your head and say "you kids refactoring everything, you need to learn to design up front". That's the best part of it :-)
Jun
25
awarded  Nice Answer
Jun
25
revised Should you write your back-end as an API?
added 2302 characters in body
Jun
25
comment Should you write your back-end as an API?
Imagine you're writing it as a website - all those tiny functions cannot be as interactive as you imagine, so you'll have to get the data and cache it locally while you construct your page (or pass them as potentially stale data to the client, as appropriate to the system). For a lot of this, you have to change your design from "react on demand" to "anticipate up front" but most of your system will be making API calls. Design your API to be less granular and more data-centric, so IsUserLoggedOn doesn't have to be an API call, you only need a "GetUserDetails" once that you then inspect locally.
Jun
25
comment Is it a common practice to first develop a RESTful backend (no MVC), then build thin client on top of it
See programmers.stackexchange.com/questions/287819/… as a duplicate.
Jun
25
comment Is it a common practice to first develop a RESTful backend (no MVC), then build thin client on top of it
It isn't what tends to happen in the enterprise as there are so many factors involved in building products (eg generally reuse existing code, or create new stuff from scratch quickly) but your approach will work, and will work very well. (personally I'd create the REST service using a different technology so in turn, don't tie the backend service to ASP.NET, you may find WCF services are much better)
Jun
25
answered Should you write your back-end as an API?
Jun
25
answered Create new object or reset every property?
Jun
25
comment Source control branch design for deployed environments
@dimgl using that model (which is good) you CI on the develop or master branches, whichever you merge most to. You should also then create CI builds using the build server (or continually update a single release) for each production build.
Jun
24
answered Design question concerning extensibility
Jun
24
comment Is the git “Golden Rule of Rebasing” so essential?
"hey nobody push for a while I have to fix ..." .. sounds like the old days of using Visual Source Safe. I thought git was better than that.
Jun
24
comment Learning machine code?
try one of the open source compilers first, eg llbm. Then you'll have yo go to the specs for CPU architectures from eg ARM and Intel.
Jun
24
revised How safe is it to compile a piece of source code from a random stranger?
deleted 1526 characters in body
Jun
23
comment How safe is it to compile a piece of source code from a random stranger?
of course, make is not a compiler...
Jun
23
comment DB Schema design : single table with more columns vs multiple tables with fewer colomns
better to ask on the DBAs SE site
Jun
23
comment How safe is it to compile a piece of source code from a random stranger?
OK< I will mention template metaprogramming, but that can only produce output that the compiler allows - no 'pwning' possible.
Jun
23
revised How safe is it to compile a piece of source code from a random stranger?
added 1526 characters in body
Jun
23
comment How safe is it to compile a piece of source code from a random stranger?
I think you'd notice cleverly crafter code designed to exploit a vulnerability in a server, or a compiler. But taking this to the extreme, why take the risk of viewing the code at all?! There are several exploits in editors that can be exploited just by viewing a file.
Jun
23
answered How safe is it to compile a piece of source code from a random stranger?
Jun
23
comment Managing International Programmers
I worked with a company that hired some Russian devs, they wrote all the code in English, as required, but all the comments were in Russian. It made maintenance of it quite tricky, we had to hire them back in the end.