112 karma · joined September 12, 2013
The bytes expressed here are my own opinion, so dig it and dig it well.
[ my public key: https://keybase.io/eddie_31003; my proof: https://keybase.io/eddie_31003/sigs/EW6HiTVvdtVxD0z0HTNpqC7brCvegJl1BQlD1K13hZs ]
Martin Fowler - https://www.martinfowler.com/
Rober C. Martin (Uncle Bob) - https://sites.google.com/site/unclebobconsultingllc/
I prefer SublimeText as a TextEditor. I've been trying to use Atom, but haven't made the complete switch.
I've been playing with WebStorm because I think JetBrains products are #KickAss.
I would recommend to using the best tool for the job/task you're working on. If you're doing .NET Development, then Visual Studio would be your tool of choice.
If you're doing web development for MEAN or LAMP or anything else, you're probably use a combination of SublimeText/Atom and something like WebStorm.
I suggest trying to use as many tools as you can and see which ones work best for you and your workflow. It's always a good thing to know how to use more than one tool.
I would also hit up Meetups, Users Groups, and maybe Alumni mixers. Chances are you might run into an old co-worker/class mate that shares similar interests.
I had several professors at my community college who had contacts in our local industry and knew several peers who landed internships through those connections. However, they were all local tech firms or local agencies looking for technical interns.
A community college is still an accredited educational institution, so you'll meet the requirements. I also suggest attending Meetups, User Groups, and Hackathons.
There's an old saying, "It's not what you know, it's who you know." The more you are able to network and get your name out there the better off you'll be.
https://18f.gsa.gov/2015/01/13/an-open-source-tool-for-easie...
If you're already committed to a specific technology, it may be best to continue down that path. As an example, if you're building .Net Applications it may be advantageous to move to Azure.
However, it you're looking to move fast and pivot when necessary you may want to look at AWS or Rackspace. I think those providers are pretty reliable and offer a lot of options.
I think with open plans you're sharing a lot more germs too. How many times have your co-workers came into work sneezing? Even in a cube farm, those germs just spread. At least with an office you can keep you and your germs better confined.
For smaller features, we'll have a Dev just implement it full stack. This takes for granted that a lot of the plumbing is there, i.e. Service Layers
It helps to have these conversation during Planning Meetings. This will help the Dev's involved to get a better understanding of the Stories and Tasks needed to implement.
2. I try to make plans, but they rarely work. I need to be more diligent about my planning.
3. It usually involves chicken and vegetables.
4. Not really.
5. For me, it's all about timing.
I really comes down to personal preference. Who says you can't do both? I have a corporate IT Background. Microsoft Technologies have kept me happily employed for over 10 years. I'm currently a Full Stack Developer on the MS Stack working for a local gov't agency. However, I have never been exclusive to MS Tech. I love the Mac Book I use. I spin up VMs whenever I want to try something new.
Never stop learning. That's what you should focus on. You'll never be an expert an everything. Try to learn as much as possible about as much as possible. Breadth and depth. I believe we're passed the point of praising the Tech Specialists. Organizations are in more need of the Tech Generalists. We need to know a lot about the Full Stack and everything in between.
Lastly, it's all about finding the right tool for the job. It's best to have a nice set of tools that you can pull from. You'll be better prepared to make architectural decisions when you understand the differences in the tools needed to build great products.
There's some overlap in contents, but I feel they complement each other very well.