361–365 of 365 posts
Earlier quoted context omitted.
Just master rails -g and you can be done in an afternoon.
I agree that if you tune it for shop conventions and know its warts well, one can indeed be productive in it. But getting to that point is not necessarily short or easy.
Earlier quoted context omitted.
I imagine this was partly an attempt at data normalization. If you'd been allowed to type it in they would have had to worry about differences in spelling, capitalization, etc. I'm not saying the solution they used was a good one mind, but I bet that was part of the motivation to implement it that way
I expect you're right, but there are better ways (e.g. autocomplete) to achieve that.
Earlier quoted context omitted.
Salesforce, the core database/CRUD bit of it if you ignore all the stuff they've purchased and tacked-on in the last few years, is essentially 'Access in the cloud', in terms of the sorts of things you can do and the ease with which you can do it, and how far you can stretch it before it starts to get cumbersome. And yes, they are making a killing. edit: And if that sounds easy, imagine how you would go about upgradi…
I'm not sure if a cloud version could ever replace access. Access is already paid for, works with on premise data, is easily deployed (no browser version madness), is ubiquitous, is easy to recover from bus factors (search the victims computer for .mdbs) and is easy to control access too. Salesforce seems like a particularly bad solution, you end up with a small army of high priced, low skilled salesforce contractors…
Earlier quoted context omitted.
Based on my limited experience, Power Pivot has a maddening lack of smooth integration with Excel. Power BI is a separate install, I believe, so not currently an option. I'm stuck with Office 2013 for the time being and can't upgrade or install anything. If I could use anything, I'd probably prefer to go back to SSRS. Maybe Informatica, or OBIEE or something. I'm biased by spending so many years writing SQL, but I fo…
DAX and SQL are qualitatively different languages. They serve different use cases entirely. DAX is designed solely for analytical queries using dynamic context (so you don't have to code for every user selected filter or relationship dependency in your model.) Its meant to be written once and then used interactively by your users. It has tons of helper functions like time intelligence, iterators and generators .. SQL…