Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I work in an organization where we for many years have been planning to start using SAS DI Server/DIStudio.
Now we are just a few months away from starting to use the product. It's a huge investment. The license cost is just a minor part. Training and the project for converting current base programs to DI Studio Jobs is where the big money will be spent.
But now I'm beginning to have doubts.
DI Studio depends on SAS Metadata Server. And as I understand SAS Viya has no metadata server.
We are on a 100% 9.4 environment today, but we want to introduce SAS Viya. Using DI Studio means we have to keep two environments up and running and in sync (four when counting test environments). And what happens the day SAS9.4 is not supported? Will there be a migration path? Is there even a DI substitute for SAS Viya?
What do you say? Would you begin using SAS DI Studio today?
Or would you continue base-coding your DI-jobs and focus on migrating to SAS Viya and get rid of the 9.4 environment?
Agree with Reeza on forum but I would recommend moving forward to Viya vs DI Studio. If you plan on switching to Viya, no need to continue adding to the current stack. Just makes migration harder.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I'm working on a development road map for a django project. My choosen IDE is pycharm pro and mock up tool is bootstrap studio. One of my criteria is a calendar and I have discovered that none of the existing public projects will meet my needs so I will have to create one from scratch (no problem). My typical approach would have been that the UI and the django project would be done in near parallel periodically merging and diverging the two. However, given the ability of the two software tools, I'm starting to think that that a better approach may be to do the UI first in BSS, next import the templates into the django project and finally perform the django dev to meet the needs of the UI.
The specific calendar functionality is not the issue here, this is a methodology question. While I know that there is a subjective answer to this question (which is not the "answer" I'm looking for here), there also has to be an objective answer as to why this would not work, or be the incorrect approach.
Doing the UI first is fine if you already know exactly what you want it to do and can specify that. Doing the Django first lets you play around with a working rough version and get a better feel for what works best before fine tuning the look and feel. Like you suggest, working on them both together will let each inform the other.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I am building a mobile dating app and plan to leverage google's cloud infrastructure.
I'm trying to figure out whether the entire application should live in a single GCP project or not.
On reading the best practices documentation I can see they advise the following naming convention:
[company tag]-[group tag]-[system name]-[environment (dev, test, uat, stage, prod)]
So should I split all the core components of the application between different projects? For example one for the data science matching algorithm (fizz-ds-matching-dev) and one for the android application? Or should I jam it all in one project?
Looking to follow best practices...
You're asking for some heat here. What to call things is probably as confrontational as asking vim or emacs!
As an employee of a large company where I oversee like 50 GCP projects my advice would be pick a naming scheme that lets your i-dont-have-time-for-this-kubernetes-gke-yaml-shit developer/pm/boss man find the project they want in 8 key presses or less.
A scheme which has worked well for me is: org-app-environment which is fairly close to what google recommends. I imagine your ops, so dont try to be clever with your naming scheme. Even though your users are dev, they're still users. If it takes them more than 5 seconds to find their project, they will do whatever the equivalent of an Arab spring is in the software world.
You need to find the nirvana of if the new guy is using this, is it easy to filter and find and is it quick to identify wtf is running there.
I recommend org-app-environment. Drop the org if you only have one, otherwise keep it.
Gods speed ops man.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Where can one find code base for power BI visuals, I need code for radial gauge chart to customize it.
I have tried searching google and posting it in power BI community but have not found an answer yet.
I believe Microsoft uses GitHub for its Power BI visuals' repositories. I understand the radial gauge is one of the earlier ones and was developed using Microsoft's earlier approach, so its coding structure doesn't align with the current documentation and approach for how to develop visuals. (You'll likely experience some issues just trying to tweak it.)
Anyhow, I believe this is the TypeScript for it. It is located within https://github.com/Microsoft/PowerBI-visuals-core, which has been deprecated. Check out https://github.com/Microsoft/PowerBI-visuals for information about how to code custom visuals for Power BI the current way.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I just became familiar with ember js and came to know that I have to build ember app and deploy the dist folder to my server. As I join new job and they were already using ember so I have to use it but I figured out some thing very bad. I wanted to share and ask for clarification.
It creates one large js file which was near 2MB and will increase as modules usage and features will increase.
As it is compiled to one file I cannot figure out which feature was broken and I have to look at it in the latest release or some thing like that.
While developing when I run the ember server it kills me when it is taking time.
Please let me know if you know some good points about ember also the bad points.
Before this question gets closed, let me slip in some thoughts:
It creates one large js file which was near 2MB and will increase as modules usage and features will increase.
Yes, it does. Basically, Ember is large. People have been exploring approaches to this for years, but AFAIK there is no silver bullet at the moment.
As it is compiled to one file I cannot figure out which feature was broken and I have to look at it in the latest release or some thing like that.
I don't understand this part of your question. Perhaps you could provide details on a specific case.
While developing when I run the ember server it kills me when it is taking time.
It's most likely the build process, not the server, which is slow. There are some approaches to solving this, including running the Windows console in administrator mode, which you can find by googling for "ember build slow". Here's a possibly out-of-date SO question on the topic. The simplest approach is to get a faster machine with SSD, and/or work on Mac/Linux.
Please let me know if you know some good points about ember also the bad points.
Many people love Ember. Many people hate it. Many people have a love-hate relationship with it. It appears that the current Ember adoption rate is in the low-to-mid single digits. Draw your own conclusions.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I'm using now the build-in plugin for Code Coverage in IntelliJ. But I need more detailed information about my unit tests. How can I get some branch test statistic in this IDE ?
As far as I know, there's nothing comparable to how sonar branch testing works in IntelliJ out of the box.
For example if a line of code has multiple execution paths, IntelliJ will mark it green if just one of the paths is executed.
In contrast, sonar will tell you that (for example) 1 of 3 possible paths were executed.
Your best bet is to run sonar locally or on a server and use sonar a plugin, for which I see 2 options that seem to be fairly up to date:
http://plugins.jetbrains.com/plugin/7168?pr=idea
http://plugins.jetbrains.com/plugin/7238?pr=idea
Good luck.