Just another coder of this planet. Love to play games in PC and love to play with his kid. Was a die hard Java fan and still is! But front-end JS frameworks tilted my opinion a little bit! Would code for money with PHP(a.k.a Freelancing!).
Consulting for new Projects. Help mentor team. Freelance. Full time/Part Time Remote work opportunities.
No blogs yet.
Mentoring is not teaching. This is improving. If a person knows Javascript and works with me, I would ask him to go through existing codebase and analyse how code is written against his current code. This will improve his code but will improve the overall codebase as eventually he has to start merging his code into working codebase. Will ask him to do a lot of online coding puzzles not to learn the coding logic only but to learn to manage time. The problem with most new guys are they don't value time. They need to work within time. I see a lot of them stay late at night and finish things but can do the same without staying late. I believe in writing clean code and if my code-review tool says otherwise, I will not merge the code. Even if that means weeks of his work. In the end we need to enforce such things for better code instead of giving in for such short time pressures. Lot more can be done, but I just mentioned few that I deemed as important.
I also have teaching experience. I don't know how to monetize that, though. Join as tutor in sites like udemy. iOS is most touted teaching skill and I am sure you make decent money if you put up some good courses. Start with couple of free courses on introduction. If they like it, they will surely buy your courses. Join a startup which is well funded and have clear goal. Work there and use the free time for brain-storming. Having people around and listening to their problems are the best way for creating best products. Because you are solving real world problems. And if you feel have any semi-decent idea for app, post it somewhere, improve it and release it in iOS. It will generate some decent revenue and will lead to something else.
This is ONE of the parameter and I do consider this among other qualities which I expect. Although the main reason why we go outside for help is, if we stuck at some problem. What we expect is, people to give us pseudo code to fix the particular solution. While what you said is nice to have, but it is not something which can be taught sooner but knowing your basics is something which can't be, especially if you are experienced.
Either you follow this and have less messier code or you don't and have a lot more messier one. It is that simple. Whoever does code without a plan always end up creating more junk comparatively.
Am I approaching this with too wide or narrow of a scope? Yes, partly. Building a site is not as simple as that. Especially a B2C product. Do you have any suggestions of how you would approach this project? I layout the flow in use-case diagrams of various modules. And see if there is any link between modules. Before I code, I make sure I get all right(atleast80%) as this would save lot of time by not creating mess. Please have a prototype ready, which is nothing but barebone app with no design, nothing. Just HTML/forms which emulate the exact functionality you expect out of it. This might sound boring and time consuming, but trust me, it will get you out of so much trouble. Can you tell me based on the functions of this app, what skills/languages I need to learn as I go? I'd suggest you to use PHP/PostgreSQL (or) MySQL for this. With bluehost already supporting PHP, you don't have anything to worry about in terms of hosting. Which parts of this project are worth reinventing the wheel vs. finding a plugin to integrate? Whole thing. You can find nice open source real estate CMS (http://estatezilla.com/) and tweak the shit out of that. But since it is mainly for learning, there is no harm in developing a new one. Is it even possible to create a separate section of our website that is not using wordpress and it all be under the same domain? We are using Bluehost for hosting, just FYI Yes, but forgot how its done.
Get requirements from user and convert it into usable spec for developers to work with. Manage team with assigning tasks and mentoring, of course. Monitor code quality. Do performance tuning and fix critical tasks. Co-ordinate with on-site team to get shit done. Take care of deployments(more of monitoring it now-a-days) Answer client queries and give estimation in case of new enhancement. Integrate with other vendors and integrate with 3rd party APIs. I can go on and on, but this is what I do, literally, everyday.
Hi, I'm Rajkumar, working as a Project Lead in a SME at a Tier-2 city in India. Currently working in Spring/AngularJS/Oracle at my regular job and in PHP/Node/Go for my freelancing and hobby projects. I have 2 kids and I love playing video games(anyone up for CS:GO, KF?). I love to learn new technologies and I have OCD to update myself every now and then. This is how I feel alive. While I like application development as well, I love Web Development and fascinated in fixing the day to day challenges of big web applications which is used by thousands of users. I've been part of Hashnode for a short time, but I feel I am more updated than before as I get to know about all the technologies in one place rather than keeping different bookmarks for update in various technologies. Not to mention the awesome devs who made this place very welcoming. If not these, I wouldn't keep hashnode tab open everyday in my browser, at work and at home.
Been working with Spring for over 8 years and I guess I can post my opinion here. When Spring was a buzzword, it was mainly because how JavaEE ecosystem was back then. Coupling a framework with a container is the stupidest thing to do and that's what JavaEE was. We had no option other than to look for alternative and that is when Spring was gaining traction, thanks to it's easy to configure(not too easy, but still better than JavaEE) and vast documentation. We really enjoyed working with Spring back then, as we didn't had any exposure outside of that. Then things started developing in rapid manner. The once most touted Spring is now nothing but a bloatware(Well, Spring Boot and all you can argue, but I am playing with 30+MB WAR files, so not an lean framework anymore). More and more I learn about the individual libraries, more and more I keep my distance away from Spring. I am not hating Spring, but it is not fit enough to attract me today. But the fact is, Spring was indeed an attractive option back then and I actually enjoyed working with it. (Hibernate, not much! I hate it). Not anymore. I started using Go for webapps, Kotlin in Android and with that in my hands, I don't see any benefit in using Spring now. This is just me!