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 9 years ago.
Improve this question
I was wondering how people think about using productivity tools like Coderush or Resharper in live demos. Is it a don't and should someone only use the most default settings of the IDE? Or is it ok to speed things up a little during the demo? Also, should you explain you are using this tool during the demo?
I've seen a lot of presentations where people use these tools and personally I don't mind.
Make sure you tell people that are going to be using the tool and then announce the action that you are about to take. e.g. "I'll use Resharper to extract this method into the Foo class"
It really depends on what you want to demonstrate. This kind of productivity tool are usefull even for demos in order to avoid loosing time on basic technical problems. You may also take advantages of such demos to introduce the features of these tools...
I tend to use DevExpress Refactor! Pro, and GhostDoc, when I do code-related presentations. I try to make sure the audience knows what I'm doing by saying out loud what I'm going to do, but I have also built my own custom tool for this, which you can find a beta of here: LVK.ScreenKeys.
Basically the tool will pop up, in the upper right corner of the screen, yellow tooltip/toast-like windows showing the key stroke/sequence I invoked, and also a textual description of what it means, depending on the software it was invoked in.
Before I started using such a tool, I invariably had questions like "what did you do now", and if you don't want to use such a tool (there are others besides mine), I would consider not using more than a few functions of such tools.
Related
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 just graduated and started my career as a junior software engineer. The one thing I am struggling with right now is not knowing when to stop doing something from scratch.
Last week I was told to simulate a warehouse environment and tell my boss what sorts of layout should be optimal. I spent days trying to build that in Simpy, Netlogo, Google OR tools. Even though I was aware there's a software tool called AnyLogic for doing all this for you, I just didn't use it.
After spending almost two weeks with partial development my boss wasn't satisfied with my work. And now I'm watching AnyLogic tutorials. I am not sure whether I should keep working on improving my partial work or switch to AnyLogic and save time.
I would highly appreciate if you give me some suggestions to know when to go for the built in stuff and when not to. I know it sounds very simple but it's actually not. Requirement analysis of a project is very tough.
Thank you. :D
If future flexibility (upgrading, knowing how it works, etc.) of doing it from scratch benefits you more than using a prebuilt system saves you time, do it from scratch. Otherwise it's not worth it. Time is money, and you can't get time back.
As long as you understand what exactly it is that you are doing with a prebuilt system then there is no issue in using it. When I code, am I doing something wrong by using VSCode instead of writing my own text editor? No, I know what a text editor does and how it does it.
When I use VSCode, am I doing something wrong by running it in Microsoft Windows or Linux, and not custom developing my own operating system? No, because I know what an operating system does.
The flexibility of writing my own software to do these tasks does not outweigh the time saved by using a prebuilt solution and therefore I will end up being more productive, and probably make more money in the end, by using them.
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 7 years ago.
Improve this question
Yes, while i'm working on node.js, i still love perl, :)
The old web product is based on old perl CGI, i'm looking to the simplest way to fix XSS/Sql injection/etc. web security holes, within a week including testing, :(
So for
Catalyst
Dancer
Mason
Maypole
Mojolicious
which one should i use in the ARM platform ?
Thank you !
You have fallen foul of the primarily opinion-based off-topic categorisation, and your question will probably be closed very soon. However I think it's worth offering a few guidelines here
First of all you should absorb what is written in CGI::Alternatives as it is a reasonable summary of the subject
Next you should separate the HTML generation functionality of your existing CGI code from the interface itself, and consider replacements for each of them separately. If you were to use HTML::Tiny together with CGI::Simple then your code would have to change very little and you would have achieved better partitioning of functionality
Ideally you will move on to one of the many templating systems such as Template Toolkit, together with one of the frameworks, which is the topic of your question. In the end you will need to do a lot of research and many trials to discover how well each framework fits your requirement, in terms of both the feature list and the convenience and clarity of the API
All I can do here is say that I am very fond of the Mojolicious suite and suggest that it may be a good starting point. The API focuses on command chaining in a way similar to Ruby, and there is a Mojolicious::Plugin::CGI accessory which will allow you to execute CGI scripts unchanged during your migration
Note however that all of the frameworks that you mention, as well as several others, will have their proponents. That is why you must make the selection yourself, as such recommendations will be influenced primarily by familiarity, and without your own knowledge of the requirements of your project
Unfortunately I cannot speak to the security issues of the various options, but I hope that has helped a little
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 9 years ago.
Improve this question
I have been evaluating DNN over a few months. It has it´s pros and cons. I find it hard to evaluate systems by reading articles and don´t have time to check them all on my own.
What are your general feeling about this?
As my background is with .net, which system would you choose?
Also, does anybody know if these pages at stack overflow is based on a CMS and if so which?
Since everyone would rather spend more time criticizing your post than answering it, I'll give it a shot.
You have a few options with building a portal. Either go with an established, open source portal (like DNN), look into some paid solutions or build your own.
Open Source - I've worked with DNN and MojoPortal. DNN is a little slower and has a few more requirements to develop skins and modules, but it has A LOT more features and some of the free/paid modules are really cool. Overall, DNN wins here, but if you don't need a large portal and you want to keep development really simple, MojoPortal might be better. MojoPortal has a few nice features that makes it easier to configure.
Open Source (Other) - There are tons of them out there. Orchard is one I'm thinking of because I'm interested in MVC. But, it's still young in terms of features and support.
Umbraco - I can't really speak to this because I have not used it, but it does have some popularity.
Build it - This is an option and allows the most flexibility, but it takes a lot of time and so many features that are built into these portals could be left out. Role based access, page management, page/module permissions, downloadable modules, profile/profile properties, file management, skinning, acct management, menu management, event logs, etc
I left out non .NET solutions like ones based on PHP, Grails, etc because you are a .NET developer. There is plenty out there, but sticking to .NET will help speed your development up.... unless you are just wanting to learn something new.
Hope this helps.
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 9 years ago.
Improve this question
I wish to make an iOS application that includes a document library, log/journal, forums, possible randomized quotes ?and coaching tools?, and have built applications of that size in other contexts but this is my first iOS application.
Right now I'm working through http://www.raywenderlich.com/1797/how-to-create-a-simple-iphone-app-tutorial-part-1 , and I'd welcome comments on other tutorials, but I wanted to ask: does it work to work out the logical gears of an application before developing the graphic design? I would like to have somewhere between a Dirtylicious and Nature look, but my natural bent (no pun intended) is to get most the gears working and then defer most of the design work until after the gears. I expect they should not be completely separated, and there are cases where you apply the design and then realized that what the gears are doing only looked good on paper, but I wanted to do a sanity check on whether it makes to look up tutorials appropriate to a document library, a log/journal, forums, etc. and get them to work together first, and then skin it.
TIA,
It is recommended that you follow the MVC pattern, which strives for separation between layers.
http://developer.apple.com/library/ios/#documentation/general/conceptual/devpedia-cocoacore/MVC.html
Xcode helps you implementing that pattern.
I think you should try to put in "paper" everything you want to do, before doing any actual coding, check how many views you are gonna have, what you need, the flow between views, try to diagram everything, that will save you a lot of pain later. You don't have to be so specific about the GUI at this stage, you only need to know what kind of visuals you need in the views, (buttons, labels, etc...)
And yes, I think you're safe doing the Model first.
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 8 years ago.
Improve this question
I'm new to emacs and I find it hard to make decisions on which extension to choose. Too many choices I say. The same pattern is true when I first started to use linux (choosing a distro, choosing packages to install, etc.)
I'm now faced with the dilemma of choosing between autocomplete and company. Both are emacs extensions that provide completion mechanisms for emacs. I may decide to use autocomplete because I think it's much more mature, and because of AutoJavaComplete which requires autocomplete. However, company mode also seems to be good, and some users report that it's much better than autocomplete. It lacks documentation though, which I rather find daunting.
Basically, I just want "intellisensy" completion when writing code. Which among the two is a better choice for this?
The latest company-mode release is 12 hours old as I'm writing this. Recent work focused on bugfixing, as well as some nice new features.
I encourage you to try it, I think it provides better user experience than auto-complete.
You can feed company backends to auto-complete, and the compatibility is probably possible in the reverse direction too - so your choice may not be too critical.
What comes out of discussions at the emacs wiki is that CompanyMode is older, and there is at least one mention of bugs in favor of auto-complete. Indeed, it seems auto-conplete is what the cool kids are using these days, and repository on github shows active development. The latest version of company, on the other hand, is nearly 11 months old.