61–70 of 72 posts
I am surprised that the Enterprise edition is missing the option to export as an Excel file, eagerly waiting for future releases.
But there are so many flavors of CSV file to choose from. So I’d have to make that pluggable too.
AI-is-the-new-Java edition: http://joelgrus.com/2016/05/23/fizz-buzz-in-tensorflow/
And this is why I will never work in Enterprise again.
While Enterprise is always the go to for things like this, I think any time non technical people get involved in technical decisions the fun time begins. Just today I was told that I wasn't allowed to implement something in python just because it's "a scripting language"
Earlier quoted context omitted.
While Enterprise is always the go to for things like this, I think any time non technical people get involved in technical decisions the fun time begins. Just today I was told that I wasn't allowed to implement something in python just because it's "a scripting language"
If theoretically a developer chose to develop something in Python in my company that would be an automatic no. There are multiple reasons: You would add an another language to support from the development to the operational support like monthly security updates. And that's a major risk and most companies won't take it. If you leave the company then the company may have potentially unsupported app with noone capable o…
Generally having a small number of implementation languages in use shouldn't be an issue. In fact, languages are tools and some are better suited than others to certain uses. If an organization supports products of even modest complexity odds are multiple languages and other technologies are required in order to make it work properly.
Earlier quoted context omitted.
Our issue is that we hired an intern to code FizzBuzz, and he mistakenly coded it as divisible by 3 for Fizz, divisible by 4 for Buzz, and divisible by 13 for FizzBuzz. Now, our sales force runs on this modified FizzBuzz. We cannot simply accept an additional unvetted FizzBuzz, even if it strictly adheres to the standard. This version on GitHub looks solid, but it needs an Enterprise Compatibility Mode that loads an…
Anxiously awaiting your pull request.
I'm appalled that this piece of junk that has the audacity to call itself "enterprise grade" does not employ an industry standard dependency injection framework. 22 appearances of 'new' in the codebase - you gotta be kidding me! I cannot recommend to license this application for deployment at my company unless its code is thoroughly refactored to use Dagger or at the very least Google Guice.
Earlier quoted context omitted.
While Enterprise is always the go to for things like this, I think any time non technical people get involved in technical decisions the fun time begins. Just today I was told that I wasn't allowed to implement something in python just because it's "a scripting language"
If theoretically a developer chose to develop something in Python in my company that would be an automatic no. There are multiple reasons: You would add an another language to support from the development to the operational support like monthly security updates. And that's a major risk and most companies won't take it. If you leave the company then the company may have potentially unsupported app with noone capable o…
FWIW, Python is the 4th most popular language on the TIOBE index (after C, C++, Java). It's not likely that $COMPANY is already using Python than Ruby or Perl.