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
Is it even worth it to learn all of this Bootstrapping and stuff that just feels like I'm not really doing any work?
I feel like it's a bit cheat-y, y'know?
I showed someone a site I had built and they said it was good, but it didn't work well at all across multiple platforms.
So, I Googled for some tips on how I can make the site adjust to different screen sizes, and every link I went to just listed different Bootstrapping things and plug-ins that'll do it for me.
I want to learn this stuff for myself so I have better control over it, I suppose.
Is that really a good idea, or would it be more worth it to look into Bootstrapping and junk?
I would advocate to learn how things work first, and then use libraries/frameworks to accelerate your workflow.
The idea behind this is that if those tools have bugs, or issues, you'll have a much better capacity to dig in and debug.
Trying to build all of these tools yourself, however, is NOT recommended (unless its for exploratory reasons). These libraries and frameworks exist for a reason, they have many contributors (something you can't compete against as a solo dev) and they solve real-world problems.
That being said, learning how to properly select a given lib/framework for a given use-case is a skill really worth building. And that comes from understanding what problems the libs/frameworks solve, which is the result of having explored "the inner workings" by digging in.
In the end, these tools will greatly accelerate your development speed, which is great, especially when it's business related (your job).
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
I picked up coding during quarantine and haven't gone a day without learning since. I've managed to learn the basics of Ruby in little under two weeks and run a few programs/started creating a basic app. Now I have to get a hang of Ruby on Rails. Furthermore, I have started learning Data Structures & Algorithms as a separate topic to complement the programming followed by Logic & Discrete Mathematics. I'm a very fast and curious learner and simply cannot just let a question be without knowing the solution to it (which led me to making my StackOverflow account).
Learning is always easier and more engaging when you have an enthusiastic and passionate person to guide you through a subject.
I was wondering if anyone knows where I can find a good one-to-one mentor that caters to an enthusiastic beginner programmer?
Alternatively, is there a recommended online forum, group or organisation that does the same thing?
Answers would be very much appreciated.
Ultimately there isn't really a great place for this yet, perhaps because there's a point at which developers no longer wish to be mentored rather than rely upon a mutual network. StackOverflow being an obvious example.
Coding Coach tries to tie mentors and mentees together, for free. In my experience it can be quite difficult to find active mentors on the platform though.
CodeMentor isn't free but also has a large number of active mentors.
RailsLink has a channel called beginners-and-mentors for small bits of advice.
It can be quite difficult to find someone willing to engage one-to-one when you're learning because, unfortunately, it's often quite boring for the mentor. For that reason, networking with peers is a great way to learn when starting out. It also means that one 'mentor' can help a collective with greater ease.
Try reaching out to people on Twitter or other social media and try to be helpful where you can too. Even if you're only one week in you're a week ahead of someone who's not tried at all.
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 5 years ago.
Improve this question
I am going to start a new application in iOS and there are multiple architectures available in iOS i.e Viper,MVVM,MVP and MVC.
I have search google but didn't find any specific use of these architectures.
Can anyone please guide me that when and which architecture should be used and which is more beneficial?
I will try to put my answer in short:
MVC: This is the basic architecture you will find most of the people use. Without knowing this, don't go forward as it's wasting time doing so. But this architecture no one is interested in the current market as it has few drawbacks. When comes to unit testing people find it difficult. So they started moving on. One good thing about this architecture is your development is super fast.
VIPER: which became very popular these days for its separation of data, design, controller logic. For unit testing, it will be very nice. But understanding and putting efforts in this are more. If you fully understand this one, I advise you to go.
MVP: People who understand MVC, can easily go with this MVP. As there are not many changes involved in this from MVC. Presentation logic will be separated out. If you want to build good architecture, not the basic one go for this.
MVVM: It also requires good efforts from you. Don't go until you understood. Again very good separation of model, View, ViewModel.
Now it's your choice to get onboard. As all of us know, how important an architecture is for an app, don't take fast decisions here. Take your own time and conclude based on the time you have in your hands, the need for proper architecture.
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
Is there any standard way to build developer, just making the developers understand the code easily after delivering, if you have sample it's better
If you want to know how to make your code better, you need to read about SOLID and other object-oriented design patterns.
There are no official Apple developer programming style guides.
I.e.: no official "Programming Standards" exist.
Standard only exist in terms of UI, external appearance of your application.
Normal software development criteria apply:
commenting
using software patterns appropriately, as pointed out in another answer, SOLID makes a lot of sense. Just in order to understand Apple Frameworks you need to know software patterns: delegation, visitor, proxy, etc.
document requisites and change requests, api and architecture if the app is complex
don't rely too much on bug tracking, these tend to be abused (change requests marked as bugs) and might add too much complexity of their own (JIIRA).
your organization may adopt an existing programming "quality standard" and adapt it to iOS development. ITIL is and ISO are usually overkill.
Sometimes it makes no sense to over-optimize and over-engineer everything, including your code and programming standards.
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
You can find thousands of questions out there about how you develop software and which methodology is the best one. But mainly these are targeting medium to large teams, with people having different roles and responsibilities.
What I'm interested in is what methodology are you using for your one-man-shows? What steps are you doing, what documents are you creating to get the things you want to develop clear and document it well, to share it with the community?
Especially, I’m interested in the following questions:
_Are you using a structured approach even you’re developing on your own or no at all?
_What phases are you using?
_Which documents are you writing before and after coding?
And if you have “your” standardized approach, can you share templates which you are using?
Thanks in advance,
cheers
Gerry
Personally I think it is a matter of making decisions when it comes to the development process (solo). In my case I wouldn't recommend setting up a massive development process but I would pick elements which prevent problems that I have earlier had. My approach for small applications (in the right order):
Always write down what you are going to make and what you are not going to make (define a scope) - Think of functional requirements (Functional Design)
(OO only) Make a class diagram that displays relations between classes. (Technical Design - Sequence diagrams, while usefull, take up massive amounts of time to make)
Write your program according to what you have just written down (or part of it).
Refactor and redesign your application (once in every X hours, write this one down)
Repeat step 3 to 4 until the result is what you wrote in the Functional Design.
Walk through every corner of your application to find every single path and write this down in a testdocument. Identify possible problems in the paths and test them.
When it comes to big applications however (or assignments for someone else) I prefer using the "medium to large teams" approach. Which almost brings a guarantee that you will not be meeting most problems.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
It's been 20 years since I learned any coding and things are very different now. After playing with cakephp and yii, I decided on ROR. I'm having a blast!
My question is not so much about ROR, but the best way to learn anything.
I started learning ROR and found out about version control and git. That was interesting and lead me to a few days of really learning it. I got back to rails and found out about RVM. That too was really interesting and I spent a couple days learning that. It goes on and on like this. I almost obsess about every new thing I learn.
The real question: Is it better to learn just enough to get by in the beginning and go back later and learn the intricacies of your tools or is it better to really learn each tool as you go?
Hope this makes sense as it is more of a philosophical question than a technical one.
Thanks
I don't think you should learn whatever you are most interested in at the moment because this can easily get out of hand...
I suggest a more focused approach to learning. Pick a real project with a goal (it should be challenging, but still realistic). Then learn along the way to reach your goal. Try not to learn stuff that's not directly related, and make sure you learn everything that you need to come up with a really good, simple solution. When done, pick next goal and repeat.
I think you should learn whatever you are most interested in at the moment.