The best Client-Server Systems eBooks: Reddit reviews

From 3.5 billion Reddit comments

Marketing/MIS major @ GVSU and TERP10 certified. In terms of learning material regarding FI/CO, Professor Magal's text Business Process Integration with SAP ERP (https://www.amazon.com/Business-Process-Integration-SAP-ERP-ebook/dp/B00BL828LY/ref=la_B001JSHIYS_1_3?s=books&ie=UTF8&qid=1477241900&sr=1-3) is dense but effective. First two chapters introduce you to both FI/CO, and the remaining go into detail regarding process integration (procurement, production, fulfillment, etc.). Again it's a bit of an investment, but worth it if you'd want a detailed overview of practical SAP instances. There's other texts by the same author to if it proves too intensive!

Estimation is an art. There are several techniques. You'd pick a technique depending on the project's size and other factors. Most devs have received no education in estimation, and just produce guesstimates. Using "expert judgement" should be the last resort. These estimates have little value and are often biased. If you go with this, at least provide best case, worst case and expected case.

Data based techniques are way better. For this you need historical data of your past projects: average time to complete a screen of size X, average time to create a web service with N methods, etc. That way you just estimate the number of screens/lines of code/whatever you need in your new project, and multiply by the average historical time. Of course there will be an error. But if you do this with every project, over time you will be able to calibrate your next estimates and reduce your estimation error.

There are several estimation techniques that are based on data:

• Decomposition and recomposition (by feature,by task, WBS, ...).
• Estimation by analogy (You know total LoC or time of similar past projects)
• Fuzzy logic (when you know LoC for features of sizes small, medium, large, etc)
• Components (when you know LoC or time per form, or per database table, or per retrofit service, etc)
• Story points (when you know LoC or time for a feature of N points)
• T-shirt sizing (when you know LoC or time for Small/Medium/Large code units, whatever the units might be).

If you have data, make sure it is data of Android projects, and using technologies similiar to what you are going to use (e.: don't estimate Compose UIs based on average time data for XML based UIs).

Estimations wil be better at the end of the project (cone of uncertainity).

For anyone interested, I recommend McConnell's often unknown little jewel on estimation: Software Estimation: Demystifying the Black Art

If you want to improve your personal programming craft, it's something that occurs over a lifetime. I've been doing this 25 years, and I still strive to continually improve, and learn new techniques all the time, or re-evaluate old practices.

It's taken me many years to get reasonably decent at writing APIs. You need to have a clear grasp of the problem domains, such that you can anticipate use cases. This is the biggest issue if you're experienced, especially if inexperienced in the domain you're working on.

There are many other factors, such as efficiency, and if your API allows clients to easily make mistakes, or whether it naturally encourages correct code.

I'd recommend an old classic: Code Complete, considered by many to be the best software-writing guide ever. It teaches you bedrock principles, which is most valuable for newer programmers who don't necessarily understand why doing something one way is preferable to another way, etc.

https://www.amazon.com/VDI-Delusion-Desktop-Virtualization-Enterprise-ebook/dp/B007MWG378

VDI fits some very narrow workflows really well. It's never a cost-savings success though.

No course, self study, most likely dozens of hours. I used this book: https://www.amazon.com.au/RHCSA-Linux-Certification-Study-Seventh-ebook/dp/B01DB3H8AM

when i did it years ago, the first chapter was all about setting up a laptop/workstation to be able to host virtual machines. It opens the book and call on experience and concepts not explained until later in the book, so it's a tough start for sure. however if you can get your head around it you will have a virtual machine host, two VMs and a virtual network to play around with. You can then follow along with the books. The RHCSA in particular is recommended for the basic foundation of Linux it does a pretty good job of laying out, if you studying everything in the RHCSA section you will 'learn Linux' in the process.

I like Jang's book because it expects you to have a VM or two and play around with things as you learn, so it's more involved than simply 'reading text'.

Good luck and enjoy, I had a lot of fun learning the RHCSA curriculum and it has aided my career is so many ways.

I apologies for the confusion I honestly read your post a couple times and thought you were a r/lostredditors.

I would recommend reading the book Code Complete (Developer Best Practices) 2nd Edition. I have read a good portion of the book and it gives a good foundation to become better at software architecture. The book is a bit dry, but many people I have talked to in industry have read this book and found it helpful.

The subreddit sidebar has links to some good training video playlists, so check those out. For books I like SCCM Unleashed and the Deployment Fundamentals series.

I recently had to spin up a new coworker on SCCM. We frequently referenced this book for resource material and reading assignments. We have come to call it “The Bible”.

I recently had the opportunity to meet one of the authors. Good dude. This is an amazing book.

System Center Unleashed (CB)

Thanks! I used CompTIA Cloud+ Certification Study Guide, by Wilson and Vanderberg as my main book.

System Center 2012 Configuration Manager (SCCM) Unleashed https://www.amazon.de/dp/B008LW61JI/ref=cm_sw_r_oth_api_njjxAbDX7YBYA

https://www.google.de/amp/s/prajwaldesai.com/sccm-2012-r2-step-by-step-guide/amp/

I did an in person class from Microsoft (they actually sent people to train us) and then another online 8 months later. Both were nice for familiarization... but they really taught from a "perfect world" perspective, which didn't really help me out that much while I was in the process of taking over / learning in a production environment. The single greatest learning resource I can recommend is the Unleashed series of books on SCCM 2012. It will help you figure out what each log file does and where to find it, and give you information you literally will not find anywhere else. It is a TREMENDOUSLY valuable reference that you seriously need to have available to you while you are on the job. There's a vanilla 2012 book and a R2 companion book. I would recommend getting both if you can afford them.

I would say the definitive book on this is Steve McConnell's book. He discusses everything, from the "cone of uncertainty" making early estimates be off by an order of magnitude, to explaining different methods of keeping yourself straight when coming up with estimates to managing expectations (commitment vs. estimate, buy spending more effort estimating you can't get the estimate lower, only more precise, etc.).

That said, I have found that trying to get estimates to be precise is rarely worth the effort. Mostly a ballpark estimate, multiplied by a correction factor derived from empirical data and setting limits where to enter cut-our-losses mode is quite enough.

I liked this book a lot, is kind of outdated on the language side, but it has some examples and simple ways of resolving them. http://www.amazon.com/Applying-Domain-Driven-Design-Patterns-ebook/dp/B0054KOKQQ/ref=sr_1_2?ie=UTF8&qid=1322572512&sr=8-2