charlsy chuks

Ranch Hand
+ Follow
since May 18, 2012
Merit badge: grant badges
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by charlsy chuks

Thanks for the details . Does your book teach on how to get data from one app to another in any of those 4 scenarios?
Secondly,can an android app talk to other databases apart from mysql?
6 years ago
Hi Joel,
I would love to know what to expect in your book in terms of what approach you take to communicate the concepts of android programming to the reader. Also will Eclipse be the default IDE? Thanks.
6 years ago
Welcome Joel Murach! I hope this book revives my interest in android programming.
6 years ago
Hi Bryson,
This is another area I need some input on. Pair programming is good. Both participants have different levels of skills.
One person's strength might be another's weakness and vice versa, so they could complement each other.

In a case where you have kids learning on one PC, both novices to the computing game, how do you achieve the same benefit
without slowing either child's rate of assimilation?

7 years ago
Yeah Bryson,

When I showed them HTML, the response was classic! I just went straight to HTML since they were almost done with high school.
The experience was priceless. However, I think the block styles would have laid a kind of foundation for them to eventually grasp the
basic concepts of programming.

The next challenge which may not be much of a challenge is disabusing their minds that this stuff is for nerds only or folks who are really good at
math or sciences. I have not really gotten that personally but it is a stereotype that needs to be changed.

I am sure you have had a share of your own experiences which you can share.
7 years ago

Bryson Payne wrote:Wayne,
I've got lots of friends who have used Scratch with their children, and they loved it as a start. When their kids wanted to be able to do more than the block-style languages allowed, that's when they made the switch to Python or JavaScript.
I chose to use Python from the start with my children (starting at 2 and 4, now 5 and 7) - they would sit in my lap and come up with fun changes to the short programs I'd write, I'd help them find the keys to type in a change or two, then we'd watch the result.
I believe Python's turtle graphics offer as visually rich an experience as Scratch or Blockly, and kids love seeing the results immediately.
Plus, I love a good-old-fashioned text-based adventure, like the MadLibs app we build at the end of chapter 1 .
I think the important thing is finding something your kids enjoy, whichever path you take, and spending time with them at the computer, together.
Best wishes, and happy coding!

I think I like this approach of starting with Block and moving on to text based languages when they have explored visual styles enough. A hybrid technique more like. Gee, Thank you so much for this idea.
7 years ago
Hi Bryson,

I have done a little of introducing high school students to html and a bit of code. Now I was wondering if I could also do same for kids in primary school or could I just stick with visual aids like the 'Scratch'
Model used by folks at for example?

Now if I stick to the visual aid for those kids, would they really feel like they were programming a computer? What are your views on this?

7 years ago
Hi Bryson!!!

Teaching Kids to Code is a field I just ventured into. I do it along side active coding.
I have always believed the earlier kids are introduced to coding, the stronger the chances are that they would choose a career in software development.
This is sure gonna be an interesting journey with you.
Welcome sir!
7 years ago
Well said Junilu,
When I said 'huge' I meant having a thorough understanding of the system by quizzing the client, potential users and other stakeholders plus analyzing the whole system to be automated. But I totally understand your point of view.

The challenge I think most teams have is they implement some aspects of agile and leave others which are important. Like I know I have not really tried automated testing before and probably came across SLAP for the first time here. However, I have attempted using DRY by putting code thats called in multiple places into methods so if I need to change I simply update the method once. I can just imagine having a database where a foreign key relationship exists and lots of code has been written around that relationship only to be changed at the last minute because of a new update to functional requirements.

If the system were database access agnostic, it would only require changing the data access queries which in itself could be pretty difficult.

Truly that synergy is what we all need.
Great replies Andrew and Junilu,

However, if I got you guys right it's not a question that has a fixed answer and could vary from project to project or even from team to team. I came to the conclusion that some tools and technologies lend themselves more to Agile style of development than others. I don't know if it is okay to recommend some here.

Concepts that you might want to look into include emergent design, clean code, re-factoring, design principles like SOLID, DRY and SLAP, continuous integration, automated testing, and Test-Driven Development. When done properly, all these contribute to agility and the team's ability to effectively evolve the software as you learn more about the system that you are developing.

I was just wondering that given the nature of agile development, which of these principles fits BEST into the agile framework?

The best for analysis and design is the last responsible moment. This is one of the ideas that really differentiates agile teams from more traditional ones, and it's central to having an agile mindset.
.....Agile teams take a similar latest responsible moment approach to planning, too, which lets then have much more simple and flexible plans.

I just wanted to be sure; was that a typo or are there really differences between last and latest?

Take for example the oft-cited example of Fitnesse: They chose to defer the decision on using a database. This turned out to be a good choice on that project because they were able to defer the decision *away* altogether.

I wonder if any 'serious' development can be done 'without' a database either relational or object kind like you cited in Fitnesse. A risk I sense here is that in doing bits of the system at different times, after a while especially without adequate comments and documentation, one forgets how the entire system fits in and works hand-in-hand. By that I mean how the different modules should
interact. Hence those who say a huge part of the design should be done upfront with about 90% clarity of the BIG picture of the system may have a point. Do you agree?
I am currently working on a team and I am pretty sure we are adopting agile strategies even though we are not following it strictly.
We basically design one module at a time and implement partly then move to another. At the points where one interact with another we revisit the previous ones.
When the client says a new feature should be added or asks for modification of an existing feature, it could involve heavy change in database schema, not to mention code.

I often wonder if this is what agile is really about because it could be stressful making changes and undoing stuff that took time to put in place.

Hence my question 'When is the best time for some analysis and design on an agile project?' Thanks.
Agile is a HOT TOPIC any time, any day especially when you consider it against the back drop of architecture like Simon Brown did in his GREAT book-Software architecture for developers.
I am very sure that Andrew Stellman & Jennifer Greene did justice to agile in this book.

Welcome Andrew & Jennifer!
Wow, if we consider weekends and most days after work, I would say that would be a period of at least 6 months, give or take.
I think I can work with that and set reasonable milestones as Dittmer said.
8 years ago
Hi Ulf Dittmer, I appreciate the angle you are coming from on setting milestones and all that, but when your superiors are breathing heavily on your neck and timelines are buzzing amber lights
They need you to learn it quickly. I am sure you understand. Thanks for the input all the same.

Thanks Jeff,

I appreciate this. I have downloaded the material. However, the chapters and the "What You would learn area" under Full Description is so rich and hard to resist.

The Java skills necessary for Android development
The core Java language fundamentals
Classes, objects, inheritance, polymorphism, and interfaces
Advanced Java language features (such as generics)
The basic Java APIs necessary for Android (such as the String class and threading)
The Collections Framework for organizing objects
The Concurrency Utilities for simplifying multi-threading
Classic and New I/O
Networking and database access
Parsing, creating, and transforming XML documents
Additional APIs for creating and accessing ZIP and JAR files, and more

No wonder you have used up 1,200 pages . I must commend your effort in putting this together. I am sure it will make for an interesting read.
8 years ago
Hi Jeff,

I picked up a book that was very introductory on Android development but I gave it up after a while. It kind of "SLOW" in introducing topics and very detailed to a fault. Now, the thing is I need a book that will get me up to speed with Android development in a short time.

I am a bit familiar with the Eclipse environment already but I need to know will your book enable me to quickly master Android development? If Yes, how is it structured to do so? One more thing, do you know if there are any plans for Netbeans to become Android friendly soon?
Thank you.
8 years ago