A very good principle regimen is one that contains many ideas formed over years
and sometimes centuries.  These could be from others, your mentors, or your
very own.  Giving a good gift of talking about it is one way to share your
ideals for others to consider.  As a developer, consider this when writing
instructions for others who may be developers themselves, or your objective,
as customer centered for instance.


You cannot make an instant principle per-se.  Well established principles are
expected, not just because they are good or right, but because others trust your
judgment.  It could be broader or focused on one thing.  However, your
gift of reading this is one way the builders of SCREENS wanted to convey some
ideals formed many years ago.  And it is this sort of basis of principles
which did not shift or change.  Some of those could be issues around privacy,
concepts of doing the right thing and talking about it; sharing; making purpose
of someone's desire (possible), and such; Principles of fairness, open capability,
and generally ideals on great goals.

Rounding this up to one sentence or a book may not be so simple.  If you are
considering what to take from this, consider these two ideals or principle-possibilities:

1. Do you want others to use your extension or software connection for something
useful which is consistently accepted and respected as such?

2. Do you need people to consider how attitude and ways of interacting are substantially
important?  If so, then maybe you should consider what your principles per-se are.


Going to the doctor and getting good treatment is expected.  It is just this thing
we call "Expected" because you think of what could go wrong would be really, really,
possibly not so good.  You have expectations of going to the doctor and getting
good information (hopefully) and getting the best out of the journey.

A principle in one way or the other can be the "Principle" of expectation.  Your
developer goals will create those expectations.  Without exception, this is where
this type of principle will be formed and will expand or change.  It is surely your
hope to make it a good experience, without problems, and to the best hope and express
desire to "Make it work".  Depending on the nature of your project, you can consider
this example as talking about what others are invariably going to do.  To evaluate,
to consider, and to expect.  If setting the bar very high is useful by working
your developer processes (such as instructions, communications, and all of the above
concepts developers think of
) - - you'll be on the right footing.

At the end of the day, one principle that is hard to escape is Expectations.  If you
fail to set them or try to let it grow without structure then you might be creating
a service or product which has many views on reliability.  Whether true or not,
it may be one reason to consider why you need some basis to build on which can be
expressed somehow.  As a developer, consider the Doctor's Office as how generally
importance of establishing good basic principles are important.


Finding that fresh sandwich is expected.  Unlike the doctor's office, it is a
consumable.  When developer(s) execute a plan to build a working project which
extends or adds benefits to SCREENS, it should be considered to escalate importance
when consumables are introduced.  Consider this as one thing which must be
substantially strengthened thru good communications, documentation, and understanding
of public policy.  While it may be one or two things to consider, or maybe
nothing at all, ... A developer should consider all avenues when discussing how
their project should connect customers to end-products, such as food.

Another way to look at it is to consider as a developer when establishing connections
to SCREENS as these: 1. Is it ambiguous on the fact food or beverages will be served,
where food or beverages certainly are served?; 2. Do people know if special styles of
goods are being provided or fall under a unique pricing category?; 3. Do end-users know
if any special conditions exist for freebies or even when take-homes are prohibited?;
4. Is there a method of process available which makes any unique conditions very
clear to actual end-users? - - This certainly is where any developer will tailor their
project or science to fit the exact needs (wherever that may be).

Before beginning any major work it should be considered with special attention when
food and beverages are part of something your bringing to the marketplace.


If you have a wish to build an experimental service then the concept of principle
basis necessity is even more critical.  Wondering if it will work, or wondering
if there could be problems should never be without careful thought.  And while
nobody can know for sure on long term success, the careful study of necessary
developer considerations are essential.  This should always include ensuring
use cases of your project or "thing" are always well researched.  End-users ultimately
should know what they are getting into and always know for sure if it is safe (or at
least has warnings).  Where law provides opportunity to leverage opportunities
in the marketplace the nice developer will ensure all bases are covered.

Considering end-user needs and making sure documentation is available can be one
step to making your experimental idea work well.  Going beyond and working
on advanced studies and providing extra information will be all the better.  If the
end-user has an open framework to build on your idea, any extra information is useful
when the concept is very new.


Find a good pet project which has well established roots.  Or alternatively explore
the library for some great works from history.  You might find some neat principles
and ways to think about things not covered here.

If you are ready to dive in, why not begin your day (sitting down) reading through some
technical specifications for Boundary Protection and what you need to know!

If you are ready and can make notes, please start here https://www.capient.com/developers_only/


A good developer will consider that the eventual outcome of what they release will
ultimately be used in different conditions.  This may be explicitly true or false.
To consider this is something of an important thinking exercise when writing good
documentation.  You will want to ensure your process and business-rules, or
other methodology lines up with end-uses expected.  This can be very useful when
others will want to know how something works or want further details.

Plan ahead by noting your end-use goals and ensuring you are continually writing and
updating any planbook.  At the end of the development cycle your devtasks will
be greatly reduced by starting off strong.

Methods and ways to build any for or not for profit thing should consider the principle
of well documented ideas important.  Expectations, documentation, and many other
ideas previously discussed here will help along the way by 1. Being clear on what it
should be; 2. Knowing entirety of documentation before you start!; 3. And being upfront
and fair when dealing with subjects that impact end-users who are your potential customers.