3 ms·

>On the other hand, the replacement is needed because we are now hitting the limits of the original approach, be it the model, the technology, the market evolut

>On the other hand, the replacement is needed because we are now hitting the limits of the original approach, be it the model, the technology, the market evolution or the understanding of them all. Releasing a new solution, way better than the original one, will prove that the DM did a bad job. Not it won't. It will just prove that the rewrite was justified. >Good developers turn into Dungeon Masters because this is what the system demands. They really don't. Good developers realize that there is an endless of cycle of the old being replaced by the new and if you can't deal with that you are not suited to a career producing software. The whole thing reads like the author encountered one or more people whose self esteem is so fragile that they are unsuited to the commercial software industry. It sounds like those individuals had a lot of trouble keeping their own (fragile) ego out of technical and business decisions. >The moment a different implementation shows that a lot money could have been saved, then the cost of keeping the old software for too long is exposed too. And this can be scary: imagine you discover a wrong design decision you made 10 years ago costed millions to your company… would you happily expose it? Yes. Exposing it presumably then saves the company millions going forward and any halfway competent boss will respect you for putting the organization first. Shelve your ego, it's called being a professional. Never mind being professional, its also a matter of acting like an adult. The article isn't so much about dungeon masters as it is about people who shouldn't be programmers.

knieveltech 10y ago
Folks who shouldn't be N: folks who make declarations about who should or shouldn't be N. There's no gate and you, sir or ma'am, are certainly not the gatekeeper.
- Chris2048 10y ago
  Your statement generates a declaration about who shouldn't be N for all N that have declarations about them, hence barring you from doing pretty much anything... including making statements about who shouldn't be N? knieveltechs' Paradox...
  - knieveltech 10y ago
    I like the way you think. ;)
zemanel 10y ago
So, part of the work i'm doing at the moment (mainly devops for a pre-revenue startup) involves doing an ETL sub-project (scrape data from websites, ingest into a database) which i'm implementing with Django, Django Rest Framework, Scrapy, Celery, Haystack (with ElasticSearch) and Postgres, with the Django Admin configured for data curation/high level job monitoring. It basically took me half a sprint (1 week plus a couple of days) to get a large part of the work done (Scrapy spider work was mosly done by a previous developer), including unit tests for the API/DRF code base, CI integration (Codeship) and a local dev Vagrant setup. The rest of our stack (the main backend API), which was poorly implemented by a non-proficient developer (which i wouldn't consider a bad developer, merely non-experienced; he eventually moved jobs), is currently done in NodeJS/Express/Sequelize and IMHO should be scrapped and rewritten. Recently, during a conversation with a new hire frontend developer, he mentioned the ETL sub-project should be done in NodeJS as well, for same language consistency across the stack and i basically replied that if he was willing to rewrite it (with the same features i get from solid, highly featured mature community libraries) in NodeJS himself, he'd be free to do it :-) Unfortunately, the CTO <rant>which IMHO is pretty null at managing people/software projects and sole aspiration seems to be becoming the CTO of the next Trello</rant>keeps throwing out buzzwords as "Kafka based event data driven application", "snappy websockets driven UI" and "microservices", while in the last year was hardly able to get a buggy over engineered MVP up and doesn't seem to have taken a Q, which means i'm looking for a new job. In the middle of all this NodeJS madness, i'm hopeing i have not become a dungeon Master myself :-)
- alxndr 10y ago
  > "i'm hopeing i have not become a dungeon Master myself :-)" I have bad news for you...

knieveltech 10y ago

Folks who shouldn't be N: folks who make declarations about who should or shouldn't be N. There's no gate and you, sir or ma'am, are certainly not the gatekeeper.

Chris2048 10y ago
Your statement generates a declaration about who shouldn't be N for all N that have declarations about them, hence barring you from doing pretty much anything... including making statements about who shouldn't be N? knieveltechs' Paradox...
- knieveltech 10y ago
  I like the way you think. ;)

zemanel 10y ago

So, part of the work i'm doing at the moment (mainly devops for a pre-revenue startup) involves doing an ETL sub-project (scrape data from websites, ingest into a database) which i'm implementing with Django, Django Rest Framework, Scrapy, Celery, Haystack (with ElasticSearch) and Postgres, with the Django Admin configured for data curation/high level job monitoring. It basically took me half a sprint (1 week plus a couple of days) to get a large part of the work done (Scrapy spider work was mosly done by a previous developer), including unit tests for the API/DRF code base, CI integration (Codeship) and a local dev Vagrant setup. The rest of our stack (the main backend API), which was poorly implemented by a non-proficient developer (which i wouldn't consider a bad developer, merely non-experienced; he eventually moved jobs), is currently done in NodeJS/Express/Sequelize and IMHO should be scrapped and rewritten. Recently, during a conversation with a new hire frontend developer, he mentioned the ETL sub-project should be done in NodeJS as well, for same language consistency across the stack and i basically replied that if he was willing to rewrite it (with the same features i get from solid, highly featured mature community libraries) in NodeJS himself, he'd be free to do it :-) Unfortunately, the CTO <rant>which IMHO is pretty null at managing people/software projects and sole aspiration seems to be becoming the CTO of the next Trello</rant>keeps throwing out buzzwords as "Kafka based event data driven application", "snappy websockets driven UI" and "microservices", while in the last year was hardly able to get a buggy over engineered MVP up and doesn't seem to have taken a Q, which means i'm looking for a new job. In the middle of all this NodeJS madness, i'm hopeing i have not become a dungeon Master myself :-)

alxndr 10y ago
> "i'm hopeing i have not become a dungeon Master myself :-)" I have bad news for you...