first commit hugo
This commit is contained in:
commit
37c74ca990
3
.gitmodules
vendored
Normal file
3
.gitmodules
vendored
Normal file
@ -0,0 +1,3 @@
|
||||
[submodule "themes/ananke"]
|
||||
path = themes/ananke
|
||||
url = https://github.com/theNewDynamic/gohugo-theme-ananke.git
|
||||
0
.hugo_build.lock
Normal file
0
.hugo_build.lock
Normal file
15
BuildAndPublish.sh
Normal file
15
BuildAndPublish.sh
Normal file
@ -0,0 +1,15 @@
|
||||
# Build the book
|
||||
hugo
|
||||
|
||||
#Copy assets into place
|
||||
rsync -a public/* ../publish-reachableceo.com
|
||||
|
||||
# Commit the generated assets
|
||||
cd ../publish-reachableceo.com
|
||||
git add -A
|
||||
git commit -m 'deploy new website version'
|
||||
|
||||
# Push the assets to the github page target.
|
||||
git push page master
|
||||
|
||||
cd ..
|
||||
613
LICENSE
Normal file
613
LICENSE
Normal file
@ -0,0 +1,613 @@
|
||||
GNU AFFERO GENERAL PUBLIC LICENSE
|
||||
|
||||
Version 3, 19 November 2007
|
||||
|
||||
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
|
||||
|
||||
Everyone is permitted to copy and distribute verbatim copies of this license
|
||||
document, but changing it is not allowed.
|
||||
|
||||
Preamble
|
||||
|
||||
The GNU Affero General Public License is a free, copyleft license for software
|
||||
and other kinds of works, specifically designed to ensure cooperation with
|
||||
the community in the case of network server software.
|
||||
|
||||
The licenses for most software and other practical works are designed to take
|
||||
away your freedom to share and change the works. By contrast, our General
|
||||
Public Licenses are intended to guarantee your freedom to share and change
|
||||
all versions of a program--to make sure it remains free software for all its
|
||||
users.
|
||||
|
||||
When we speak of free software, we are referring to freedom, not price. Our
|
||||
General Public Licenses are designed to make sure that you have the freedom
|
||||
to distribute copies of free software (and charge for them if you wish), that
|
||||
you receive source code or can get it if you want it, that you can change
|
||||
the software or use pieces of it in new free programs, and that you know you
|
||||
can do these things.
|
||||
|
||||
Developers that use our General Public Licenses protect your rights with two
|
||||
steps: (1) assert copyright on the software, and (2) offer you this License
|
||||
which gives you legal permission to copy, distribute and/or modify the software.
|
||||
|
||||
A secondary benefit of defending all users' freedom is that improvements made
|
||||
in alternate versions of the program, if they receive widespread use, become
|
||||
available for other developers to incorporate. Many developers of free software
|
||||
are heartened and encouraged by the resulting cooperation. However, in the
|
||||
case of software used on network servers, this result may fail to come about.
|
||||
The GNU General Public License permits making a modified version and letting
|
||||
the public access it on a server without ever releasing its source code to
|
||||
the public.
|
||||
|
||||
The GNU Affero General Public License is designed specifically to ensure that,
|
||||
in such cases, the modified source code becomes available to the community.
|
||||
It requires the operator of a network server to provide the source code of
|
||||
the modified version running there to the users of that server. Therefore,
|
||||
public use of a modified version, on a publicly accessible server, gives the
|
||||
public access to the source code of the modified version.
|
||||
|
||||
An older license, called the Affero General Public License and published by
|
||||
Affero, was designed to accomplish similar goals. This is a different license,
|
||||
not a version of the Affero GPL, but Affero has released a new version of
|
||||
the Affero GPL which permits relicensing under this license.
|
||||
|
||||
The precise terms and conditions for copying, distribution and modification
|
||||
follow.
|
||||
|
||||
TERMS AND CONDITIONS
|
||||
|
||||
0. Definitions.
|
||||
|
||||
"This License" refers to version 3 of the GNU Affero General Public License.
|
||||
|
||||
"Copyright" also means copyright-like laws that apply to other kinds of works,
|
||||
such as semiconductor masks.
|
||||
|
||||
"The Program" refers to any copyrightable work licensed under this License.
|
||||
Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals
|
||||
or organizations.
|
||||
|
||||
To "modify" a work means to copy from or adapt all or part of the work in
|
||||
a fashion requiring copyright permission, other than the making of an exact
|
||||
copy. The resulting work is called a "modified version" of the earlier work
|
||||
or a work "based on" the earlier work.
|
||||
|
||||
A "covered work" means either the unmodified Program or a work based on the
|
||||
Program.
|
||||
|
||||
To "propagate" a work means to do anything with it that, without permission,
|
||||
would make you directly or secondarily liable for infringement under applicable
|
||||
copyright law, except executing it on a computer or modifying a private copy.
|
||||
Propagation includes copying, distribution (with or without modification),
|
||||
making available to the public, and in some countries other activities as
|
||||
well.
|
||||
|
||||
To "convey" a work means any kind of propagation that enables other parties
|
||||
to make or receive copies. Mere interaction with a user through a computer
|
||||
network, with no transfer of a copy, is not conveying.
|
||||
|
||||
An interactive user interface displays "Appropriate Legal Notices" to the
|
||||
extent that it includes a convenient and prominently visible feature that
|
||||
(1) displays an appropriate copyright notice, and (2) tells the user that
|
||||
there is no warranty for the work (except to the extent that warranties are
|
||||
provided), that licensees may convey the work under this License, and how
|
||||
to view a copy of this License. If the interface presents a list of user commands
|
||||
or options, such as a menu, a prominent item in the list meets this criterion.
|
||||
|
||||
1. Source Code.
|
||||
|
||||
The "source code" for a work means the preferred form of the work for making
|
||||
modifications to it. "Object code" means any non-source form of a work.
|
||||
|
||||
A "Standard Interface" means an interface that either is an official standard
|
||||
defined by a recognized standards body, or, in the case of interfaces specified
|
||||
for a particular programming language, one that is widely used among developers
|
||||
working in that language.
|
||||
|
||||
The "System Libraries" of an executable work include anything, other than
|
||||
the work as a whole, that (a) is included in the normal form of packaging
|
||||
a Major Component, but which is not part of that Major Component, and (b)
|
||||
serves only to enable use of the work with that Major Component, or to implement
|
||||
a Standard Interface for which an implementation is available to the public
|
||||
in source code form. A "Major Component", in this context, means a major essential
|
||||
component (kernel, window system, and so on) of the specific operating system
|
||||
(if any) on which the executable work runs, or a compiler used to produce
|
||||
the work, or an object code interpreter used to run it.
|
||||
|
||||
The "Corresponding Source" for a work in object code form means all the source
|
||||
code needed to generate, install, and (for an executable work) run the object
|
||||
code and to modify the work, including scripts to control those activities.
|
||||
However, it does not include the work's System Libraries, or general-purpose
|
||||
tools or generally available free programs which are used unmodified in performing
|
||||
those activities but which are not part of the work. For example, Corresponding
|
||||
Source includes interface definition files associated with source files for
|
||||
the work, and the source code for shared libraries and dynamically linked
|
||||
subprograms that the work is specifically designed to require, such as by
|
||||
intimate data communication or control flow between those
|
||||
|
||||
subprograms and other parts of the work.
|
||||
|
||||
The Corresponding Source need not include anything that users can regenerate
|
||||
automatically from other parts of the Corresponding Source.
|
||||
|
||||
The Corresponding Source for a work in source code form is that same work.
|
||||
|
||||
2. Basic Permissions.
|
||||
|
||||
All rights granted under this License are granted for the term of copyright
|
||||
on the Program, and are irrevocable provided the stated conditions are met.
|
||||
This License explicitly affirms your unlimited permission to run the unmodified
|
||||
Program. The output from running a covered work is covered by this License
|
||||
only if the output, given its content, constitutes a covered work. This License
|
||||
acknowledges your rights of fair use or other equivalent, as provided by copyright
|
||||
law.
|
||||
|
||||
You may make, run and propagate covered works that you do not convey, without
|
||||
conditions so long as your license otherwise remains in force. You may convey
|
||||
covered works to others for the sole purpose of having them make modifications
|
||||
exclusively for you, or provide you with facilities for running those works,
|
||||
provided that you comply with the terms of this License in conveying all material
|
||||
for which you do not control copyright. Those thus making or running the covered
|
||||
works for you must do so exclusively on your behalf, under your direction
|
||||
and control, on terms that prohibit them from making any copies of your copyrighted
|
||||
material outside their relationship with you.
|
||||
|
||||
Conveying under any other circumstances is permitted solely under the conditions
|
||||
stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
|
||||
|
||||
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
|
||||
|
||||
No covered work shall be deemed part of an effective technological measure
|
||||
under any applicable law fulfilling obligations under article 11 of the WIPO
|
||||
copyright treaty adopted on 20 December 1996, or similar laws prohibiting
|
||||
or restricting circumvention of such measures.
|
||||
|
||||
When you convey a covered work, you waive any legal power to forbid circumvention
|
||||
of technological measures to the extent such circumvention is effected by
|
||||
exercising rights under this License with respect to the covered work, and
|
||||
you disclaim any intention to limit operation or modification of the work
|
||||
as a means of enforcing, against the work's users, your or third parties'
|
||||
legal rights to forbid circumvention of technological measures.
|
||||
|
||||
4. Conveying Verbatim Copies.
|
||||
|
||||
You may convey verbatim copies of the Program's source code as you receive
|
||||
it, in any medium, provided that you conspicuously and appropriately publish
|
||||
on each copy an appropriate copyright notice; keep intact all notices stating
|
||||
that this License and any non-permissive terms added in accord with section
|
||||
7 apply to the code; keep intact all notices of the absence of any warranty;
|
||||
and give all recipients a copy of this License along with the Program.
|
||||
|
||||
You may charge any price or no price for each copy that you convey, and you
|
||||
may offer support or warranty protection for a fee.
|
||||
|
||||
5. Conveying Modified Source Versions.
|
||||
|
||||
You may convey a work based on the Program, or the modifications to produce
|
||||
it from the Program, in the form of source code under the terms of section
|
||||
4, provided that you also meet all of these conditions:
|
||||
|
||||
a) The work must carry prominent notices stating that you modified it, and
|
||||
giving a relevant date.
|
||||
|
||||
b) The work must carry prominent notices stating that it is released under
|
||||
this License and any conditions added under section 7. This requirement modifies
|
||||
the requirement in section 4 to "keep intact all notices".
|
||||
|
||||
c) You must license the entire work, as a whole, under this License to anyone
|
||||
who comes into possession of a copy. This License will therefore apply, along
|
||||
with any applicable section 7 additional terms, to the whole of the work,
|
||||
and all its parts, regardless of how they are packaged. This License gives
|
||||
no permission to license the work in any other way, but it does not invalidate
|
||||
such permission if you have separately received it.
|
||||
|
||||
d) If the work has interactive user interfaces, each must display Appropriate
|
||||
Legal Notices; however, if the Program has interactive interfaces that do
|
||||
not display Appropriate Legal Notices, your work need not make them do so.
|
||||
|
||||
A compilation of a covered work with other separate and independent works,
|
||||
which are not by their nature extensions of the covered work, and which are
|
||||
not combined with it such as to form a larger program, in or on a volume of
|
||||
a storage or distribution medium, is called an "aggregate" if the compilation
|
||||
and its resulting copyright are not used to limit the access or legal rights
|
||||
of the compilation's users beyond what the individual works permit. Inclusion
|
||||
of a covered work in an aggregate does not cause this License to apply to
|
||||
the other parts of the aggregate.
|
||||
|
||||
6. Conveying Non-Source Forms.
|
||||
|
||||
You may convey a covered work in object code form under the terms of sections
|
||||
4 and 5, provided that you also convey the machine-readable Corresponding
|
||||
Source under the terms of this License, in one of these ways:
|
||||
|
||||
a) Convey the object code in, or embodied in, a physical product (including
|
||||
a physical distribution medium), accompanied by the Corresponding Source fixed
|
||||
on a durable physical medium customarily used for software interchange.
|
||||
|
||||
b) Convey the object code in, or embodied in, a physical product (including
|
||||
a physical distribution medium), accompanied by a written offer, valid for
|
||||
at least three years and valid for as long as you offer spare parts or customer
|
||||
support for that product model, to give anyone who possesses the object code
|
||||
either (1) a copy of the Corresponding Source for all the software in the
|
||||
product that is covered by this License, on a durable physical medium customarily
|
||||
used for software interchange, for a price no more than your reasonable cost
|
||||
of physically performing this conveying of source, or (2) access to copy the
|
||||
Corresponding Source from a network server at no charge.
|
||||
|
||||
c) Convey individual copies of the object code with a copy of the written
|
||||
offer to provide the Corresponding Source. This alternative is allowed only
|
||||
occasionally and noncommercially, and only if you received the object code
|
||||
with such an offer, in accord with subsection 6b.
|
||||
|
||||
d) Convey the object code by offering access from a designated place (gratis
|
||||
or for a charge), and offer equivalent access to the Corresponding Source
|
||||
in the same way through the same place at no further charge. You need not
|
||||
require recipients to copy the Corresponding Source along with the object
|
||||
code. If the place to copy the object code is a network server, the Corresponding
|
||||
Source may be on a different server (operated by you or a third party) that
|
||||
supports equivalent copying facilities, provided you maintain clear directions
|
||||
next to the object code saying where to find the Corresponding Source. Regardless
|
||||
of what server hosts the Corresponding Source, you remain obligated to ensure
|
||||
that it is available for as long as needed to satisfy these requirements.
|
||||
|
||||
e) Convey the object code using peer-to-peer transmission, provided you inform
|
||||
other peers where the object code and Corresponding Source of the work are
|
||||
being offered to the general public at no charge under subsection 6d.
|
||||
|
||||
A separable portion of the object code, whose source code is excluded from
|
||||
the Corresponding Source as a System Library, need not be included in conveying
|
||||
the object code work.
|
||||
|
||||
A "User Product" is either (1) a "consumer product", which means any tangible
|
||||
personal property which is normally used for personal, family, or household
|
||||
purposes, or (2) anything designed or sold for incorporation into a dwelling.
|
||||
In determining whether a product is a consumer product, doubtful cases shall
|
||||
be resolved in favor of coverage. For a particular product received by a particular
|
||||
user, "normally used" refers to a typical or common use of that class of product,
|
||||
regardless of the status of the particular user or of the way in which the
|
||||
particular user actually uses, or expects or is expected to use, the product.
|
||||
A product is a consumer product regardless of whether the product has substantial
|
||||
commercial, industrial or non-consumer uses, unless such uses represent the
|
||||
only significant mode of use of the product.
|
||||
|
||||
"Installation Information" for a User Product means any methods, procedures,
|
||||
authorization keys, or other information required to install and execute modified
|
||||
versions of a covered work in that User Product from a modified version of
|
||||
its Corresponding Source. The information must suffice to ensure that the
|
||||
continued functioning of the modified object code is in no case prevented
|
||||
or interfered with solely because modification has been made.
|
||||
|
||||
If you convey an object code work under this section in, or with, or specifically
|
||||
for use in, a User Product, and the conveying occurs as part of a transaction
|
||||
in which the right of possession and use of the User Product is transferred
|
||||
to the recipient in perpetuity or for a fixed term (regardless of how the
|
||||
transaction is characterized), the Corresponding Source conveyed under this
|
||||
section must be accompanied by the Installation Information. But this requirement
|
||||
does not apply if neither you nor any third party retains the ability to install
|
||||
modified object code on the User Product (for example, the work has been installed
|
||||
in ROM).
|
||||
|
||||
The requirement to provide Installation Information does not include a requirement
|
||||
to continue to provide support service, warranty, or updates for a work that
|
||||
has been modified or installed by the recipient, or for the User Product in
|
||||
which it has been modified or installed. Access to a network may be denied
|
||||
when the modification itself materially and adversely affects the operation
|
||||
of the network or violates the rules and protocols for communication across
|
||||
the network.
|
||||
|
||||
Corresponding Source conveyed, and Installation Information provided, in accord
|
||||
with this section must be in a format that is publicly documented (and with
|
||||
an implementation available to the public in source code form), and must require
|
||||
no special password or key for unpacking, reading or copying.
|
||||
|
||||
7. Additional Terms.
|
||||
|
||||
"Additional permissions" are terms that supplement the terms of this License
|
||||
by making exceptions from one or more of its conditions. Additional permissions
|
||||
that are applicable to the entire Program shall be treated as though they
|
||||
were included in this License, to the extent that they are valid under applicable
|
||||
law. If additional permissions apply only to part of the Program, that part
|
||||
may be used separately under those permissions, but the entire Program remains
|
||||
governed by this License without regard to the additional permissions.
|
||||
|
||||
When you convey a copy of a covered work, you may at your option remove any
|
||||
additional permissions from that copy, or from any part of it. (Additional
|
||||
permissions may be written to require their own removal in certain cases when
|
||||
you modify the work.) You may place additional permissions on material, added
|
||||
by you to a covered work, for which you have or can give appropriate copyright
|
||||
permission.
|
||||
|
||||
Notwithstanding any other provision of this License, for material you add
|
||||
to a covered work, you may (if authorized by the copyright holders of that
|
||||
material) supplement the terms of this License with terms:
|
||||
|
||||
a) Disclaiming warranty or limiting liability differently from the terms of
|
||||
sections 15 and 16 of this License; or
|
||||
|
||||
b) Requiring preservation of specified reasonable legal notices or author
|
||||
attributions in that material or in the Appropriate Legal Notices displayed
|
||||
by works containing it; or
|
||||
|
||||
c) Prohibiting misrepresentation of the origin of that material, or requiring
|
||||
that modified versions of such material be marked in reasonable ways as different
|
||||
from the original version; or
|
||||
|
||||
d) Limiting the use for publicity purposes of names of licensors or authors
|
||||
of the material; or
|
||||
|
||||
e) Declining to grant rights under trademark law for use of some trade names,
|
||||
trademarks, or service marks; or
|
||||
|
||||
f) Requiring indemnification of licensors and authors of that material by
|
||||
anyone who conveys the material (or modified versions of it) with contractual
|
||||
assumptions of liability to the recipient, for any liability that these contractual
|
||||
assumptions directly impose on those licensors and authors.
|
||||
|
||||
All other non-permissive additional terms are considered "further restrictions"
|
||||
within the meaning of section 10. If the Program as you received it, or any
|
||||
part of it, contains a notice stating that it is governed by this License
|
||||
along with a term that is a further restriction, you may remove that term.
|
||||
If a license document contains a further restriction but permits relicensing
|
||||
or conveying under this License, you may add to a covered work material governed
|
||||
by the terms of that license document, provided that the further restriction
|
||||
does not survive such relicensing or conveying.
|
||||
|
||||
If you add terms to a covered work in accord with this section, you must place,
|
||||
in the relevant source files, a statement of the additional terms that apply
|
||||
to those files, or a notice indicating where to find the applicable terms.
|
||||
|
||||
Additional terms, permissive or non-permissive, may be stated in the form
|
||||
of a separately written license, or stated as exceptions; the above requirements
|
||||
apply either way.
|
||||
|
||||
8. Termination.
|
||||
|
||||
You may not propagate or modify a covered work except as expressly provided
|
||||
under this License. Any attempt otherwise to propagate or modify it is void,
|
||||
and will automatically terminate your rights under this License (including
|
||||
any patent licenses granted under the third paragraph of section 11).
|
||||
|
||||
However, if you cease all violation of this License, then your license from
|
||||
a particular copyright holder is reinstated (a) provisionally, unless and
|
||||
until the copyright holder explicitly and finally terminates your license,
|
||||
and (b) permanently, if the copyright holder fails to notify you of the violation
|
||||
by some reasonable means prior to 60 days after the cessation.
|
||||
|
||||
Moreover, your license from a particular copyright holder is reinstated permanently
|
||||
if the copyright holder notifies you of the violation by some reasonable means,
|
||||
this is the first time you have received notice of violation of this License
|
||||
(for any work) from that copyright holder, and you cure the violation prior
|
||||
to 30 days after your receipt of the notice.
|
||||
|
||||
Termination of your rights under this section does not terminate the licenses
|
||||
of parties who have received copies or rights from you under this License.
|
||||
If your rights have been terminated and not permanently reinstated, you do
|
||||
not qualify to receive new licenses for the same material under section 10.
|
||||
|
||||
9. Acceptance Not Required for Having Copies.
|
||||
|
||||
You are not required to accept this License in order to receive or run a copy
|
||||
of the Program. Ancillary propagation of a covered work occurring solely as
|
||||
a consequence of using peer-to-peer transmission to receive a copy likewise
|
||||
does not require acceptance. However, nothing other than this License grants
|
||||
you permission to propagate or modify any covered work. These actions infringe
|
||||
copyright if you do not accept this License. Therefore, by modifying or propagating
|
||||
a covered work, you indicate your acceptance of this License to do so.
|
||||
|
||||
10. Automatic Licensing of Downstream Recipients.
|
||||
|
||||
Each time you convey a covered work, the recipient automatically receives
|
||||
a license from the original licensors, to run, modify and propagate that work,
|
||||
subject to this License. You are not responsible for enforcing compliance
|
||||
by third parties with this License.
|
||||
|
||||
An "entity transaction" is a transaction transferring control of an organization,
|
||||
or substantially all assets of one, or subdividing an organization, or merging
|
||||
organizations. If propagation of a covered work results from an entity transaction,
|
||||
each party to that transaction who receives a copy of the work also receives
|
||||
whatever licenses to the work the party's predecessor in interest had or could
|
||||
give under the previous paragraph, plus a right to possession of the Corresponding
|
||||
Source of the work from the predecessor in interest, if the predecessor has
|
||||
it or can get it with reasonable efforts.
|
||||
|
||||
You may not impose any further restrictions on the exercise of the rights
|
||||
granted or affirmed under this License. For example, you may not impose a
|
||||
license fee, royalty, or other charge for exercise of rights granted under
|
||||
this License, and you may not initiate litigation (including a cross-claim
|
||||
or counterclaim in a lawsuit) alleging that any patent claim is infringed
|
||||
by making, using, selling, offering for sale, or importing the Program or
|
||||
any portion of it.
|
||||
|
||||
11. Patents.
|
||||
|
||||
A "contributor" is a copyright holder who authorizes use under this License
|
||||
of the Program or a work on which the Program is based. The work thus licensed
|
||||
is called the contributor's "contributor version".
|
||||
|
||||
A contributor's "essential patent claims" are all patent claims owned or controlled
|
||||
by the contributor, whether already acquired or hereafter acquired, that would
|
||||
be infringed by some manner, permitted by this License, of making, using,
|
||||
or selling its contributor version, but do not include claims that would be
|
||||
infringed only as a consequence of further modification of the contributor
|
||||
version. For purposes of this definition, "control" includes the right to
|
||||
grant patent sublicenses in a manner consistent with the requirements of this
|
||||
License.
|
||||
|
||||
Each contributor grants you a non-exclusive, worldwide, royalty-free patent
|
||||
license under the contributor's essential patent claims, to make, use, sell,
|
||||
offer for sale, import and otherwise run, modify and propagate the contents
|
||||
of its contributor version.
|
||||
|
||||
In the following three paragraphs, a "patent license" is any express agreement
|
||||
or commitment, however denominated, not to enforce a patent (such as an express
|
||||
permission to practice a patent or covenant not to s ue for patent infringement).
|
||||
To "grant" such a patent license to a party means to make such an agreement
|
||||
or commitment not to enforce a patent against the party.
|
||||
|
||||
If you convey a covered work, knowingly relying on a patent license, and the
|
||||
Corresponding Source of the work is not available for anyone to copy, free
|
||||
of charge and under the terms of this License, through a publicly available
|
||||
network server or other readily accessible means, then you must either (1)
|
||||
cause the Corresponding Source to be so available, or (2) arrange to deprive
|
||||
yourself of the benefit of the patent license for this particular work, or
|
||||
(3) arrange, in a manner consistent with the requirements of this License,
|
||||
to extend the patent
|
||||
|
||||
license to downstream recipients. "Knowingly relying" means you have actual
|
||||
knowledge that, but for the patent license, your conveying the covered work
|
||||
in a country, or your recipient's use of the covered work in a country, would
|
||||
infringe one or more identifiable patents in that country that you have reason
|
||||
to believe are valid.
|
||||
|
||||
If, pursuant to or in connection with a single transaction or arrangement,
|
||||
you convey, or propagate by procuring conveyance of, a covered work, and grant
|
||||
a patent license to some of the parties receiving the covered work authorizing
|
||||
them to use, propagate, modify or convey a specific copy of the covered work,
|
||||
then the patent license you grant is automatically extended to all recipients
|
||||
of the covered work and works based on it.
|
||||
|
||||
A patent license is "discriminatory" if it does not include within the scope
|
||||
of its coverage, prohibits the exercise of, or is conditioned on the non-exercise
|
||||
of one or more of the rights that are specifically granted under this License.
|
||||
You may not convey a covered work if you are a party to an arrangement with
|
||||
a third party that is in the business of distributing software, under which
|
||||
you make payment to the third party based on the extent of your activity of
|
||||
conveying the work, and under which the third party grants, to any of the
|
||||
parties who would receive the covered work from you, a discriminatory patent
|
||||
license (a) in connection with copies of the covered work conveyed by you
|
||||
(or copies made from those copies), or (b) primarily for and in connection
|
||||
with specific products or compilations that contain the covered work, unless
|
||||
you entered into that arrangement, or that patent license was granted, prior
|
||||
to 28 March 2007.
|
||||
|
||||
Nothing in this License shall be construed as excluding or limiting any implied
|
||||
license or other defenses to infringement that may otherwise be available
|
||||
to you under applicable patent law.
|
||||
|
||||
12. No Surrender of Others' Freedom.
|
||||
|
||||
If conditions are imposed on you (whether by court order, agreement or otherwise)
|
||||
that contradict the conditions of this License, they do not excuse you from
|
||||
the conditions of this License. If you cannot convey a covered work so as
|
||||
to satisfy simultaneously your obligations under this License and any other
|
||||
pertinent obligations, then as a consequence you may
|
||||
|
||||
not convey it at all. For example, if you agree to terms that obligate you
|
||||
to collect a royalty for further conveying from those to whom you convey the
|
||||
Program, the only way you could satisfy both those terms and this License
|
||||
would be to refrain entirely from conveying the Program.
|
||||
|
||||
13. Remote Network Interaction; Use with the GNU General Public License.
|
||||
|
||||
Notwithstanding any other provision of this License, if you modify the Program,
|
||||
your modified version must prominently offer all users interacting with it
|
||||
remotely through a computer network (if your version supports such interaction)
|
||||
an opportunity to receive the Corresponding Source of your version by providing
|
||||
access to the Corresponding Source from a network server at no charge, through
|
||||
some standard or customary means of facilitating copying of software. This
|
||||
Corresponding Source shall include the Corresponding Source for any work covered
|
||||
by version 3 of the GNU General Public License that is incorporated pursuant
|
||||
to the following paragraph.
|
||||
|
||||
Notwithstanding any other provision of this License, you have permission to
|
||||
link or combine any covered work with a work licensed under version 3 of the
|
||||
GNU General Public License into a single combined work, and to convey the
|
||||
resulting work. The terms of this License will continue to apply to the part
|
||||
which is the covered work, but the work with which it is combined will remain
|
||||
governed by version 3 of the GNU General Public License.
|
||||
|
||||
14. Revised Versions of this License.
|
||||
|
||||
The Free Software Foundation may publish revised and/or new versions of the
|
||||
GNU Affero General Public License from time to time. Such new versions will
|
||||
be similar in spirit to the present version, but may differ in detail to address
|
||||
new problems or concerns.
|
||||
|
||||
Each version is given a distinguishing version number. If the Program specifies
|
||||
that a certain numbered version of the GNU Affero General Public License "or
|
||||
any later version" applies to it, you have the option of following the terms
|
||||
and conditions either of that numbered version or of any later version published
|
||||
by the Free Software Foundation. If the Program does not specify a version
|
||||
number of the GNU Affero General Public License, you may choose any version
|
||||
ever published by the Free Software Foundation.
|
||||
|
||||
If the Program specifies that a proxy can decide which future versions of
|
||||
the GNU Affero General Public License can be used, that proxy's public statement
|
||||
of acceptance of a version permanently authorizes you to choose that version
|
||||
for the Program.
|
||||
|
||||
Later license versions may give you additional or different permissions. However,
|
||||
no additional obligations are imposed on any author or copyright holder as
|
||||
a result of your choosing to follow a later version.
|
||||
|
||||
15. Disclaimer of Warranty.
|
||||
|
||||
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
|
||||
LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
|
||||
OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
|
||||
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
|
||||
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
|
||||
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
|
||||
PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
|
||||
CORRECTION.
|
||||
|
||||
16. Limitation of Liability.
|
||||
|
||||
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
|
||||
ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM
|
||||
AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
|
||||
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO
|
||||
USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
|
||||
INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE
|
||||
PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
|
||||
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
|
||||
|
||||
17. Interpretation of Sections 15 and 16.
|
||||
|
||||
If the disclaimer of warranty and limitation of liability provided above cannot
|
||||
be given local legal effect according to their terms, reviewing courts shall
|
||||
apply local law that most closely approximates an absolute waiver of all civil
|
||||
liability in connection with the Program, unless a warranty or assumption
|
||||
of liability accompanies a copy of the Program in return for a fee. END OF
|
||||
TERMS AND CONDITIONS
|
||||
|
||||
How to Apply These Terms to Your New Programs
|
||||
|
||||
If you develop a new program, and you want it to be of the greatest possible
|
||||
use to the public, the best way to achieve this is to make it free software
|
||||
which everyone can redistribute and change under these terms.
|
||||
|
||||
To do so, attach the following notices to the program. It is safest to attach
|
||||
them to the start of each source file to most effectively state the exclusion
|
||||
of warranty; and each file should have at least the "copyright" line and a
|
||||
pointer to where the full notice is found.
|
||||
|
||||
<one line to give the program's name and a brief idea of what it does.>
|
||||
|
||||
Copyright (C) <year> <name of author>
|
||||
|
||||
This program is free software: you can redistribute it and/or modify it under
|
||||
the terms of the GNU Affero General Public License as published by the Free
|
||||
Software Foundation, either version 3 of the License, or (at your option)
|
||||
any later version.
|
||||
|
||||
This program is distributed in the hope that it will be useful, but WITHOUT
|
||||
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
|
||||
FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more
|
||||
details.
|
||||
|
||||
You should have received a copy of the GNU Affero General Public License along
|
||||
with this program. If not, see <https://www.gnu.org/licenses/>.
|
||||
|
||||
Also add information on how to contact you by electronic and paper mail.
|
||||
|
||||
If your software can interact with users remotely through a computer network,
|
||||
you should also make sure that it provides a way for users to get its source.
|
||||
For example, if your program is a web application, its interface could display
|
||||
a "Source" link that leads users to an archive of the code. There are many
|
||||
ways you could offer source, and different solutions will be better for different
|
||||
programs; see section 13 for the specific requirements.
|
||||
|
||||
You should also get your employer (if you work as a programmer) or school,
|
||||
if any, to sign a "copyright disclaimer" for the program, if necessary. For
|
||||
more information on this, and how to apply and follow the GNU AGPL, see <https://www.gnu.org/licenses/>.
|
||||
5
archetypes/default.md
Normal file
5
archetypes/default.md
Normal file
@ -0,0 +1,5 @@
|
||||
+++
|
||||
title = '{{ replace .File.ContentBaseName "-" " " | title }}'
|
||||
date = {{ .Date }}
|
||||
draft = true
|
||||
+++
|
||||
12
content/posts/2024 Monthly Objectives Key Results.md
Normal file
12
content/posts/2024 Monthly Objectives Key Results.md
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
created: 2024-01-05T08:16:29-05:00
|
||||
modified: 2024-01-05T08:18:51-05:00
|
||||
---
|
||||
|
||||
# 2024 Monthly Objectives Key Results
|
||||
|
||||
January: Finish my involvement in critical path of operations and fully delegate operations to COO/CFO
|
||||
|
||||
February: Prepare outreach material
|
||||
|
||||
March: Reconnect with my entire network and share the outreach material
|
||||
100
content/posts/AnnotatedApplicationList.md
Normal file
100
content/posts/AnnotatedApplicationList.md
Normal file
@ -0,0 +1,100 @@
|
||||
# ReachableCEO Workstation Software List
|
||||
|
||||
## Introduction
|
||||
|
||||
I have created this list of software that I have installed on my workstation as CTO/co-founder of TSYS Group. It is a sub/super set of the comprehensive software/hardware engineering software list in the TSYS Group Handbook.
|
||||
|
||||
|
||||
Elmer
|
||||
7-zip
|
||||
ActivityWatch
|
||||
Adobe Acrobat
|
||||
Android Studio
|
||||
Apache Directory Studio
|
||||
Arduino IDE
|
||||
Audacity
|
||||
AuoHotkey
|
||||
Bitscope
|
||||
Bitwarden
|
||||
Bonita Community
|
||||
Calibre
|
||||
Camotics
|
||||
Camstudio
|
||||
Code Composer Studio
|
||||
Codelite
|
||||
Composer PHP Dependency Manager
|
||||
CubicSDR
|
||||
Darktable
|
||||
Dbeaver
|
||||
Digikam
|
||||
Docear
|
||||
Docker Deskop (see my containers blogpost for my Docker setup)
|
||||
Draw.io
|
||||
Esim
|
||||
Faraday
|
||||
Filezilla
|
||||
Flatcam
|
||||
Freecad
|
||||
Gephi
|
||||
Gimp
|
||||
Git
|
||||
Git-cola
|
||||
Gns3
|
||||
Go Programming Language
|
||||
Grass Gis
|
||||
Ida freeware
|
||||
Imagemagick
|
||||
Jstock
|
||||
Jxplorer
|
||||
Kdenlive
|
||||
Kicad
|
||||
Kmymoney
|
||||
Krita
|
||||
Lazarus
|
||||
Libreoffice
|
||||
Lmstudio
|
||||
Lmms
|
||||
Ltspice
|
||||
Mattercontrol
|
||||
Meshlab
|
||||
Microchip Studio
|
||||
Microsoft Visual Studio Code
|
||||
Microsoft Visual Studio
|
||||
Miktex
|
||||
Mremoteng
|
||||
Mysql
|
||||
Nmap
|
||||
Node.js
|
||||
Notepad++
|
||||
Nvidia Cuda
|
||||
Obs studio
|
||||
Octave
|
||||
Openbuildscontrol
|
||||
Openshot
|
||||
Pencil
|
||||
Postgis
|
||||
Postgresql
|
||||
Python
|
||||
Qgis
|
||||
R
|
||||
Recoll
|
||||
Rocketchat
|
||||
Rstudio
|
||||
Ruby
|
||||
Rust
|
||||
Scilab
|
||||
Scribus
|
||||
Silhouette Studio
|
||||
Sqlite Studio
|
||||
Strawberry Perl
|
||||
Streamlabs Desktop
|
||||
Utilmaker Cura
|
||||
Vym
|
||||
Windows Subsystem For Linux
|
||||
Winmerge
|
||||
Winscp
|
||||
Wireguard
|
||||
Wireshark
|
||||
Wxcrafter
|
||||
Wxformbuilder
|
||||
Zotero
|
||||
1
content/posts/AnnotatedApplicationsLists.md
Normal file
1
content/posts/AnnotatedApplicationsLists.md
Normal file
@ -0,0 +1 @@
|
||||
# AnnotatedApplicationsList
|
||||
28
content/posts/DailySchedule.md
Normal file
28
content/posts/DailySchedule.md
Normal file
@ -0,0 +1,28 @@
|
||||
+++
|
||||
title = 'Daily Schedule'
|
||||
date = 2024-05-15T09:26:11-05:00
|
||||
draft = false
|
||||
+++
|
||||
|
||||
## Context
|
||||
|
||||
Over the past year or so, I've been maintaining an 18/6 schedule (awake 18 hours, asleep 6 hours).
|
||||
|
||||
Here is how I am currently allocating time:
|
||||
|
||||
### Daily (weekdays)
|
||||
|
||||
- 00:00 - 06:30 Sleep.
|
||||
- 06:30 - 07:00 Morning routine
|
||||
- 07:00 - 11:00 commute, breakfast, household maintenance, light personal/TSYS admin tasks
|
||||
- 11:00 - 19:00 $DAYJOB from my home office
|
||||
- 19:00 - 22:00 dinner with partner, relaxing, exercise
|
||||
- 22:00 - 00:00 deep work
|
||||
|
||||
### Saturday
|
||||
|
||||
- 8am to 8pm TSYS work
|
||||
|
||||
### Sunday
|
||||
|
||||
- Completely off (relaxing, exercising, household projects etc)
|
||||
19
content/posts/Docker-Setup.md
Normal file
19
content/posts/Docker-Setup.md
Normal file
@ -0,0 +1,19 @@
|
||||
# Docker Containers and setup on ReachableCEO workstation
|
||||
|
||||
## Introduction
|
||||
|
||||
I am a very heavy user of Docker containers. This post documents how I use them personally and as CTO of a hardware/software startup.
|
||||
|
||||
## Read First
|
||||
|
||||
Read my general workstation setup post.
|
||||
|
||||
## Servers
|
||||
|
||||
### Production (cloudron)
|
||||
|
||||
### Production (on-premise)
|
||||
|
||||
### R&D
|
||||
|
||||
## Containers
|
||||
7
content/posts/GeneralWorkstationSetupNotes.md
Normal file
7
content/posts/GeneralWorkstationSetupNotes.md
Normal file
@ -0,0 +1,7 @@
|
||||
# General workstations setup notes of the @ReachableCEO workstation
|
||||
|
||||
## Introduction
|
||||
|
||||
## OS
|
||||
|
||||
## Accounts
|
||||
10
content/posts/HoldingMyselfToAccount.md
Normal file
10
content/posts/HoldingMyselfToAccount.md
Normal file
@ -0,0 +1,10 @@
|
||||
|
||||
|
||||
Over the last quarter or so, I have been holding (regular) 1 on 1 meetings with members of the TSYS board of directors and advisory board. I have been
|
||||
getting high quality feedback, perspective, analysis.
|
||||
|
||||
The overall message is to be outcome focused. Delegate as much as possible. Focus on being CEO (get out of the COO/CIO/CTO aspects).
|
||||
|
||||
The immediate action that I'm taking, is to update this blog on a regular basis, with Daily Standup posts. This will ensure that I remain transparent and accountable to all stakeholders in the TSYS Group mission.
|
||||
|
||||
The posts will be updated as I progress, and then a "finished/shipped" label will be applied (and post will be added to that category).
|
||||
62
content/posts/HowIOrganizeMyResearch.md
Normal file
62
content/posts/HowIOrganizeMyResearch.md
Normal file
@ -0,0 +1,62 @@
|
||||
# How I Organize My Research Archive
|
||||
|
||||
## Introduction
|
||||
|
||||
As (acting as of 04/14/2021) CTO of an incredibly complex product/services portfolio, I have a large amount of research material. I am writing this note on how I organize it and make it fully available to the world without any overhead on my part.
|
||||
|
||||
Short version:
|
||||
|
||||
### Documents
|
||||
|
||||
This means PDF, print to PDF of web page, other file types (doc/xls/whatever)
|
||||
|
||||
1) Bookmark the link where'er is appropriate in my taxonomy.
|
||||
2) Download the URI to ~/ResearchMaterial
|
||||
3) calibre (on Raberry pi) is using ~/ResearchMaterial and that folder is synced via nextcloud to the corporate file server so I can also use Docear/Polar/Zotero on my x86 vm
|
||||
|
||||
### NOtes
|
||||
|
||||
I use this git repository (notes-public) with a folder of markdown files.
|
||||
|
||||
I primarily use VsCode on the ras pi todo note taking (and of course longer document creation)
|
||||
Occasionally on mobile (iOS), I use Buffer and the WorkingCopy git client to make quick edits or capture something when I"m out
|
||||
and get inspired.
|
||||
|
||||
I heavily use Working Copy on my iPad Mini 5th Generation to do code review, issue cleanup etc and I use Calibre to load up a long research paepr and read it over. I also may access the folder directly via samba if I want to annotate.
|
||||
|
||||
## Source material
|
||||
|
||||
* <https://blogs.princeton.edu/librarian/2013/05/organizing-my-research-life-updated/>
|
||||
|
||||
## More detailed version
|
||||
|
||||
### Taxonomy
|
||||
|
||||
I use a single taxonomy across:
|
||||
|
||||
* e-mail folders
|
||||
* bookmarks
|
||||
* home directory
|
||||
* notes folder (this repository)
|
||||
|
||||
|
||||
It is:
|
||||
|
||||
```console
|
||||
❯ ls
|
||||
Board CEO CFO CIO CMO COO CTO dotfiles dotfiles-git landed notes-public personal PFVEMer
|
||||
~/charles 15:03:47
|
||||
❯
|
||||
```
|
||||
|
||||
* Board
|
||||
* CEO
|
||||
* CFO
|
||||
* CIO
|
||||
* COO
|
||||
* CMO
|
||||
* CTO
|
||||
|
||||
I then have division names or project/product names under those folders.
|
||||
|
||||
More coming soon , still dialing things in.
|
||||
14
content/posts/OrientationToTSYSGroup.md
Normal file
14
content/posts/OrientationToTSYSGroup.md
Normal file
@ -0,0 +1,14 @@
|
||||
# Orientation to TSYS Group
|
||||
|
||||
For Executives and BoD
|
||||
|
||||
## Facilities
|
||||
|
||||
### PFV
|
||||
|
||||
### Cloud
|
||||
|
||||
## Systems
|
||||
|
||||
### Cloudron
|
||||
|
||||
4
hugo.toml
Normal file
4
hugo.toml
Normal file
@ -0,0 +1,4 @@
|
||||
baseURL = 'https://reachableceo.com/'
|
||||
languageCode = 'en-us'
|
||||
title = 'ReachableCEO Homepage'
|
||||
theme = 'ananke'
|
||||
103
public/404.html
Normal file
103
public/404.html
Normal file
@ -0,0 +1,103 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/404.html">
|
||||
|
||||
|
||||
<meta property="og:title" content="404 Page not found" />
|
||||
<meta property="og:description" content="" />
|
||||
<meta property="og:type" content="website" />
|
||||
<meta property="og:url" content="https://reachableceo.com/404.html" />
|
||||
|
||||
<meta itemprop="name" content="404 Page not found">
|
||||
<meta itemprop="description" content=""><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="404 Page not found"/>
|
||||
<meta name="twitter:description" content=""/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
<article class="center cf pv5 measure-wide-l">
|
||||
<h1>
|
||||
This is not the page you were looking for
|
||||
</h1>
|
||||
</article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
Binary file not shown.
Binary file not shown.
BIN
public/EmailFolder.png
Normal file
BIN
public/EmailFolder.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 27 KiB |
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
1
public/ananke/css/main.min.css
vendored
Normal file
1
public/ananke/css/main.min.css
vendored
Normal file
File diff suppressed because one or more lines are too long
120
public/categories/index.html
Normal file
120
public/categories/index.html
Normal file
@ -0,0 +1,120 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link href="/categories/index.xml" rel="alternate" type="application/rss+xml" title="ReachableCEO Homepage" />
|
||||
<link href="/categories/index.xml" rel="feed" type="application/rss+xml" title="ReachableCEO Homepage" />
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/categories/">
|
||||
|
||||
|
||||
<meta property="og:title" content="Categories" />
|
||||
<meta property="og:description" content="" />
|
||||
<meta property="og:type" content="website" />
|
||||
<meta property="og:url" content="https://reachableceo.com/categories/" />
|
||||
|
||||
<meta itemprop="name" content="Categories">
|
||||
<meta itemprop="description" content=""><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="Categories"/>
|
||||
<meta name="twitter:description" content=""/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="pb3-m pb6-l bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
<div class="tc-l pv3 ph3 ph4-ns">
|
||||
<h1 class="f2 f-subheadline-l fw2 light-silver mb0 lh-title">
|
||||
Categories
|
||||
</h1>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="cf pa3 pa4-m pa4-l">
|
||||
<div class="measure-wide-l center f4 lh-copy nested-copy-line-height nested-links mid-gray">
|
||||
|
||||
</div>
|
||||
</article>
|
||||
<div class="mw8 center">
|
||||
<section class="ph4">
|
||||
|
||||
</section>
|
||||
</div>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
11
public/categories/index.xml
Normal file
11
public/categories/index.xml
Normal file
@ -0,0 +1,11 @@
|
||||
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Categories on ReachableCEO Homepage</title>
|
||||
<link>https://reachableceo.com/categories/</link>
|
||||
<description>Recent content in Categories on ReachableCEO Homepage</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
<atom:link href="https://reachableceo.com/categories/index.xml" rel="self" type="application/rss+xml" />
|
||||
</channel>
|
||||
</rss>
|
||||
BIN
public/images/gohugo-default-sample-hero-image.jpg
Normal file
BIN
public/images/gohugo-default-sample-hero-image.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 276 KiB |
255
public/index.html
Normal file
255
public/index.html
Normal file
@ -0,0 +1,255 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link href="/index.xml" rel="alternate" type="application/rss+xml" title="ReachableCEO Homepage" />
|
||||
<link href="/index.xml" rel="feed" type="application/rss+xml" title="ReachableCEO Homepage" />
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/">
|
||||
|
||||
|
||||
<meta property="og:title" content="ReachableCEO Homepage" />
|
||||
<meta property="og:description" content="" />
|
||||
<meta property="og:type" content="website" />
|
||||
<meta property="og:url" content="https://reachableceo.com/" />
|
||||
|
||||
<meta itemprop="name" content="ReachableCEO Homepage">
|
||||
<meta itemprop="description" content=""><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="ReachableCEO Homepage"/>
|
||||
<meta name="twitter:description" content=""/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="pb3-m pb6-l bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
<div class="tc-l pv3 ph3 ph4-ns">
|
||||
<h1 class="f2 f-subheadline-l fw2 light-silver mb0 lh-title">
|
||||
ReachableCEO Homepage
|
||||
</h1>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
<article class="cf ph3 ph5-l pv3 pv4-l f4 tc-l center measure-wide lh-copy mid-gray">
|
||||
|
||||
</article>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="pa3 pa4-ns w-100 w-70-ns center">
|
||||
|
||||
|
||||
<h1 class="flex-none">
|
||||
Recent Posts
|
||||
</h1>
|
||||
|
||||
|
||||
|
||||
|
||||
<section class="w-100 mw8">
|
||||
|
||||
|
||||
<div class="relative w-100 mb4">
|
||||
|
||||
<article class="bb b--black-10">
|
||||
<div class="db pv4 ph3 ph0-l no-underline dark-gray">
|
||||
<div class="flex flex-column flex-row-ns">
|
||||
|
||||
<div class="blah w-100">
|
||||
<h1 class="f3 fw1 athelas mt0 lh-title">
|
||||
<a href="/posts/dailyschedule/" class="color-inherit dim link">
|
||||
Daily Schedule
|
||||
</a>
|
||||
</h1>
|
||||
<div class="f6 f5-l lh-copy nested-copy-line-height nested-links">
|
||||
Context Over the past year or so, I’ve been maintaining an 18/6 schedule (awake 18 hours, asleep 6 hours).
|
||||
Here is how I am currently allocating time:
|
||||
Daily (weekdays) 00:00 - 06:30 Sleep. 06:30 - 07:00 Morning routine 07:00 - 11:00 commute, breakfast, household maintenance, light personal/TSYS admin tasks 11:00 - 19:00 $DAYJOB from my home office 19:00 - 22:00 dinner with partner, relaxing, exercise 22:00 - 00:00 deep work Saturday 8am to 8pm TSYS work Sunday Completely off (relaxing, exercising, household projects etc)
|
||||
</div>
|
||||
<a href="/posts/dailyschedule/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</article>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="relative w-100 mb4">
|
||||
|
||||
<article class="bb b--black-10">
|
||||
<div class="db pv4 ph3 ph0-l no-underline dark-gray">
|
||||
<div class="flex flex-column flex-row-ns">
|
||||
|
||||
<div class="blah w-100">
|
||||
<h1 class="f3 fw1 athelas mt0 lh-title">
|
||||
<a href="/posts/2024-monthly-objectives-key-results/" class="color-inherit dim link">
|
||||
|
||||
</a>
|
||||
</h1>
|
||||
<div class="f6 f5-l lh-copy nested-copy-line-height nested-links">
|
||||
2024 Monthly Objectives Key Results January: Finish my involvement in critical path of operations and fully delegate operations to COO/CFO
|
||||
February: Prepare outreach material
|
||||
March: Reconnect with my entire network and share the outreach material
|
||||
</div>
|
||||
<a href="/posts/2024-monthly-objectives-key-results/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</article>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="relative w-100 mb4">
|
||||
|
||||
<article class="bb b--black-10">
|
||||
<div class="db pv4 ph3 ph0-l no-underline dark-gray">
|
||||
<div class="flex flex-column flex-row-ns">
|
||||
|
||||
<div class="blah w-100">
|
||||
<h1 class="f3 fw1 athelas mt0 lh-title">
|
||||
<a href="/posts/annotatedapplicationlist/" class="color-inherit dim link">
|
||||
|
||||
</a>
|
||||
</h1>
|
||||
<div class="f6 f5-l lh-copy nested-copy-line-height nested-links">
|
||||
ReachableCEO Workstation Software List Introduction I have created this list of software that I have installed on my workstation as CTO/co-founder of TSYS Group. It is a sub/super set of the comprehensive software/hardware engineering software list in the TSYS Group Handbook.
|
||||
Elmer 7-zip ActivityWatch Adobe Acrobat Android Studio Apache Directory Studio Arduino IDE Audacity AuoHotkey Bitscope Bitwarden Bonita Community Calibre Camotics Camstudio Code Composer Studio Codelite Composer PHP Dependency Manager CubicSDR Darktable Dbeaver Digikam Docear Docker Deskop (see my containers blogpost for my Docker setup) Draw.
|
||||
</div>
|
||||
<a href="/posts/annotatedapplicationlist/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</article>
|
||||
|
||||
</div>
|
||||
|
||||
</section>
|
||||
|
||||
|
||||
<section class="w-100">
|
||||
<h1 class="f3">More</h1>
|
||||
|
||||
|
||||
<h2 class="f5 fw4 mb4 dib mr3">
|
||||
<a href="/posts/annotatedapplicationslists/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h2>
|
||||
|
||||
<h2 class="f5 fw4 mb4 dib mr3">
|
||||
<a href="/posts/docker-setup/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h2>
|
||||
|
||||
<h2 class="f5 fw4 mb4 dib mr3">
|
||||
<a href="/posts/generalworkstationsetupnotes/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h2>
|
||||
|
||||
<h2 class="f5 fw4 mb4 dib mr3">
|
||||
<a href="/posts/holdingmyselftoaccount/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<a href="/posts/" class="link db f6 pa2 br3 bg-mid-gray white dim w4 tc">All Posts</a>
|
||||
|
||||
</section>
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
88
public/index.xml
Normal file
88
public/index.xml
Normal file
@ -0,0 +1,88 @@
|
||||
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<link>https://reachableceo.com/</link>
|
||||
<description>Recent content on ReachableCEO Homepage</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
<lastBuildDate>Wed, 15 May 2024 09:26:11 -0500</lastBuildDate>
|
||||
<atom:link href="https://reachableceo.com/index.xml" rel="self" type="application/rss+xml" />
|
||||
<item>
|
||||
<title>Daily Schedule</title>
|
||||
<link>https://reachableceo.com/posts/dailyschedule/</link>
|
||||
<pubDate>Wed, 15 May 2024 09:26:11 -0500</pubDate>
|
||||
<guid>https://reachableceo.com/posts/dailyschedule/</guid>
|
||||
<description>Context Over the past year or so, I&rsquo;ve been maintaining an 18/6 schedule (awake 18 hours, asleep 6 hours).
|
||||
Here is how I am currently allocating time:
|
||||
Daily (weekdays) 00:00 - 06:30 Sleep. 06:30 - 07:00 Morning routine 07:00 - 11:00 commute, breakfast, household maintenance, light personal/TSYS admin tasks 11:00 - 19:00 $DAYJOB from my home office 19:00 - 22:00 dinner with partner, relaxing, exercise 22:00 - 00:00 deep work Saturday 8am to 8pm TSYS work Sunday Completely off (relaxing, exercising, household projects etc) </description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/2024-monthly-objectives-key-results/</link>
|
||||
<pubDate>Fri, 05 Jan 2024 08:18:51 -0500</pubDate>
|
||||
<guid>https://reachableceo.com/posts/2024-monthly-objectives-key-results/</guid>
|
||||
<description>2024 Monthly Objectives Key Results January: Finish my involvement in critical path of operations and fully delegate operations to COO/CFO
|
||||
February: Prepare outreach material
|
||||
March: Reconnect with my entire network and share the outreach material</description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/annotatedapplicationlist/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/annotatedapplicationlist/</guid>
|
||||
<description>ReachableCEO Workstation Software List Introduction I have created this list of software that I have installed on my workstation as CTO/co-founder of TSYS Group. It is a sub/super set of the comprehensive software/hardware engineering software list in the TSYS Group Handbook.
|
||||
Elmer 7-zip ActivityWatch Adobe Acrobat Android Studio Apache Directory Studio Arduino IDE Audacity AuoHotkey Bitscope Bitwarden Bonita Community Calibre Camotics Camstudio Code Composer Studio Codelite Composer PHP Dependency Manager CubicSDR Darktable Dbeaver Digikam Docear Docker Deskop (see my containers blogpost for my Docker setup) Draw.</description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/annotatedapplicationslists/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/annotatedapplicationslists/</guid>
|
||||
<description>AnnotatedApplicationsList </description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/docker-setup/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/docker-setup/</guid>
|
||||
<description>Docker Containers and setup on ReachableCEO workstation Introduction I am a very heavy user of Docker containers. This post documents how I use them personally and as CTO of a hardware/software startup.
|
||||
Read First Read my general workstation setup post.
|
||||
Servers Production (cloudron) Production (on-premise) R&amp;D Containers </description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/generalworkstationsetupnotes/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/generalworkstationsetupnotes/</guid>
|
||||
<description>General workstations setup notes of the @ReachableCEO workstation Introduction OS Accounts </description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/holdingmyselftoaccount/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/holdingmyselftoaccount/</guid>
|
||||
<description>Over the last quarter or so, I have been holding (regular) 1 on 1 meetings with members of the TSYS board of directors and advisory board. I have been getting high quality feedback, perspective, analysis.
|
||||
The overall message is to be outcome focused. Delegate as much as possible. Focus on being CEO (get out of the COO/CIO/CTO aspects).
|
||||
The immediate action that I&rsquo;m taking, is to update this blog on a regular basis, with Daily Standup posts.</description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/howiorganizemyresearch/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/howiorganizemyresearch/</guid>
|
||||
<description>How I Organize My Research Archive Introduction As (acting as of 04/14/2021) CTO of an incredibly complex product/services portfolio, I have a large amount of research material. I am writing this note on how I organize it and make it fully available to the world without any overhead on my part.
|
||||
Short version:
|
||||
Documents This means PDF, print to PDF of web page, other file types (doc/xls/whatever)
|
||||
Bookmark the link where&rsquo;er is appropriate in my taxonomy.</description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/orientationtotsysgroup/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/orientationtotsysgroup/</guid>
|
||||
<description>Orientation to TSYS Group For Executives and BoD
|
||||
Facilities PFV Cloud Systems Cloudron </description>
|
||||
</item>
|
||||
</channel>
|
||||
</rss>
|
||||
168
public/posts/2024-monthly-objectives-key-results/index.html
Normal file
168
public/posts/2024-monthly-objectives-key-results/index.html
Normal file
@ -0,0 +1,168 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="2024 Monthly Objectives Key Results January: Finish my involvement in critical path of operations and fully delegate operations to COO/CFO
|
||||
February: Prepare outreach material
|
||||
March: Reconnect with my entire network and share the outreach material">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/2024-monthly-objectives-key-results/">
|
||||
|
||||
|
||||
<meta property="og:title" content="" />
|
||||
<meta property="og:description" content="2024 Monthly Objectives Key Results January: Finish my involvement in critical path of operations and fully delegate operations to COO/CFO
|
||||
February: Prepare outreach material
|
||||
March: Reconnect with my entire network and share the outreach material" />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://reachableceo.com/posts/2024-monthly-objectives-key-results/" /><meta property="article:section" content="posts" />
|
||||
|
||||
<meta property="article:modified_time" content="2024-01-05T08:18:51-05:00" />
|
||||
|
||||
<meta itemprop="name" content="">
|
||||
<meta itemprop="description" content="2024 Monthly Objectives Key Results January: Finish my involvement in critical path of operations and fully delegate operations to COO/CFO
|
||||
February: Prepare outreach material
|
||||
March: Reconnect with my entire network and share the outreach material">
|
||||
<meta itemprop="dateModified" content="2024-01-05T08:18:51-05:00" />
|
||||
<meta itemprop="wordCount" content="35">
|
||||
<meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content=""/>
|
||||
<meta name="twitter:description" content="2024 Monthly Objectives Key Results January: Finish my involvement in critical path of operations and fully delegate operations to COO/CFO
|
||||
February: Prepare outreach material
|
||||
March: Reconnect with my entire network and share the outreach material"/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="flex-l flex-wrap justify-between mw8 center ph3">
|
||||
<header class="mt4 w-100">
|
||||
<aside class="instapaper_ignoref b helvetica tracked ttu">
|
||||
|
||||
Posts
|
||||
</aside>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div id="sharing" class="mt3 ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<h1 class="f1 athelas mt3 mb1"></h1>
|
||||
|
||||
|
||||
|
||||
<time class="f6 mv4 dib tracked" datetime="2024-01-05T08:18:51-05:00">January 5, 2024</time>
|
||||
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
<div class="nested-copy-line-height lh-copy serif f4 nested-links mid-gray pr4-l w-two-thirds-l"><h1 id="2024-monthly-objectives-key-results">2024 Monthly Objectives Key Results</h1>
|
||||
<p>January: Finish my involvement in critical path of operations and fully delegate operations to COO/CFO</p>
|
||||
<p>February: Prepare outreach material</p>
|
||||
<p>March: Reconnect with my entire network and share the outreach material</p>
|
||||
<ul class="pa0">
|
||||
|
||||
</ul>
|
||||
<div class="mt6 instapaper_ignoref">
|
||||
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<aside class="w-30-l mt6-l">
|
||||
|
||||
|
||||
|
||||
|
||||
</aside>
|
||||
|
||||
</article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
254
public/posts/annotatedapplicationlist/index.html
Normal file
254
public/posts/annotatedapplicationlist/index.html
Normal file
@ -0,0 +1,254 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="ReachableCEO Workstation Software List Introduction I have created this list of software that I have installed on my workstation as CTO/co-founder of TSYS Group. It is a sub/super set of the comprehensive software/hardware engineering software list in the TSYS Group Handbook.
|
||||
Elmer 7-zip ActivityWatch Adobe Acrobat Android Studio Apache Directory Studio Arduino IDE Audacity AuoHotkey Bitscope Bitwarden Bonita Community Calibre Camotics Camstudio Code Composer Studio Codelite Composer PHP Dependency Manager CubicSDR Darktable Dbeaver Digikam Docear Docker Deskop (see my containers blogpost for my Docker setup) Draw.">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/annotatedapplicationlist/">
|
||||
|
||||
|
||||
<meta property="og:title" content="" />
|
||||
<meta property="og:description" content="ReachableCEO Workstation Software List Introduction I have created this list of software that I have installed on my workstation as CTO/co-founder of TSYS Group. It is a sub/super set of the comprehensive software/hardware engineering software list in the TSYS Group Handbook.
|
||||
Elmer 7-zip ActivityWatch Adobe Acrobat Android Studio Apache Directory Studio Arduino IDE Audacity AuoHotkey Bitscope Bitwarden Bonita Community Calibre Camotics Camstudio Code Composer Studio Codelite Composer PHP Dependency Manager CubicSDR Darktable Dbeaver Digikam Docear Docker Deskop (see my containers blogpost for my Docker setup) Draw." />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://reachableceo.com/posts/annotatedapplicationlist/" /><meta property="article:section" content="posts" />
|
||||
|
||||
|
||||
|
||||
<meta itemprop="name" content="">
|
||||
<meta itemprop="description" content="ReachableCEO Workstation Software List Introduction I have created this list of software that I have installed on my workstation as CTO/co-founder of TSYS Group. It is a sub/super set of the comprehensive software/hardware engineering software list in the TSYS Group Handbook.
|
||||
Elmer 7-zip ActivityWatch Adobe Acrobat Android Studio Apache Directory Studio Arduino IDE Audacity AuoHotkey Bitscope Bitwarden Bonita Community Calibre Camotics Camstudio Code Composer Studio Codelite Composer PHP Dependency Manager CubicSDR Darktable Dbeaver Digikam Docear Docker Deskop (see my containers blogpost for my Docker setup) Draw.">
|
||||
|
||||
<meta itemprop="wordCount" content="174">
|
||||
<meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content=""/>
|
||||
<meta name="twitter:description" content="ReachableCEO Workstation Software List Introduction I have created this list of software that I have installed on my workstation as CTO/co-founder of TSYS Group. It is a sub/super set of the comprehensive software/hardware engineering software list in the TSYS Group Handbook.
|
||||
Elmer 7-zip ActivityWatch Adobe Acrobat Android Studio Apache Directory Studio Arduino IDE Audacity AuoHotkey Bitscope Bitwarden Bonita Community Calibre Camotics Camstudio Code Composer Studio Codelite Composer PHP Dependency Manager CubicSDR Darktable Dbeaver Digikam Docear Docker Deskop (see my containers blogpost for my Docker setup) Draw."/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="flex-l flex-wrap justify-between mw8 center ph3">
|
||||
<header class="mt4 w-100">
|
||||
<aside class="instapaper_ignoref b helvetica tracked ttu">
|
||||
|
||||
Posts
|
||||
</aside>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div id="sharing" class="mt3 ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<h1 class="f1 athelas mt3 mb1"></h1>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
<div class="nested-copy-line-height lh-copy serif f4 nested-links mid-gray pr4-l w-two-thirds-l"><h1 id="reachableceo-workstation-software-list">ReachableCEO Workstation Software List</h1>
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<p>I have created this list of software that I have installed on my workstation as CTO/co-founder of TSYS Group. It is a sub/super set of the comprehensive software/hardware engineering software list in the TSYS Group Handbook.</p>
|
||||
<p>Elmer
|
||||
7-zip
|
||||
ActivityWatch
|
||||
Adobe Acrobat
|
||||
Android Studio
|
||||
Apache Directory Studio
|
||||
Arduino IDE
|
||||
Audacity
|
||||
AuoHotkey
|
||||
Bitscope
|
||||
Bitwarden
|
||||
Bonita Community
|
||||
Calibre
|
||||
Camotics
|
||||
Camstudio
|
||||
Code Composer Studio
|
||||
Codelite
|
||||
Composer PHP Dependency Manager
|
||||
CubicSDR
|
||||
Darktable
|
||||
Dbeaver
|
||||
Digikam
|
||||
Docear
|
||||
Docker Deskop (see my containers blogpost for my Docker setup)
|
||||
Draw.io
|
||||
Esim
|
||||
Faraday
|
||||
Filezilla
|
||||
Flatcam
|
||||
Freecad
|
||||
Gephi
|
||||
Gimp
|
||||
Git
|
||||
Git-cola
|
||||
Gns3
|
||||
Go Programming Language
|
||||
Grass Gis
|
||||
Ida freeware
|
||||
Imagemagick
|
||||
Jstock
|
||||
Jxplorer
|
||||
Kdenlive
|
||||
Kicad
|
||||
Kmymoney
|
||||
Krita
|
||||
Lazarus
|
||||
Libreoffice
|
||||
Lmstudio
|
||||
Lmms
|
||||
Ltspice
|
||||
Mattercontrol
|
||||
Meshlab
|
||||
Microchip Studio
|
||||
Microsoft Visual Studio Code
|
||||
Microsoft Visual Studio
|
||||
Miktex
|
||||
Mremoteng
|
||||
Mysql
|
||||
Nmap
|
||||
Node.js
|
||||
Notepad++
|
||||
Nvidia Cuda
|
||||
Obs studio
|
||||
Octave
|
||||
Openbuildscontrol
|
||||
Openshot
|
||||
Pencil
|
||||
Postgis
|
||||
Postgresql
|
||||
Python
|
||||
Qgis
|
||||
R
|
||||
Recoll
|
||||
Rocketchat
|
||||
Rstudio
|
||||
Ruby
|
||||
Rust
|
||||
Scilab
|
||||
Scribus
|
||||
Silhouette Studio
|
||||
Sqlite Studio
|
||||
Strawberry Perl
|
||||
Streamlabs Desktop
|
||||
Utilmaker Cura
|
||||
Vym
|
||||
Windows Subsystem For Linux
|
||||
Winmerge
|
||||
Winscp
|
||||
Wireguard
|
||||
Wireshark
|
||||
Wxcrafter
|
||||
Wxformbuilder
|
||||
Zotero</p>
|
||||
<ul class="pa0">
|
||||
|
||||
</ul>
|
||||
<div class="mt6 instapaper_ignoref">
|
||||
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<aside class="w-30-l mt6-l">
|
||||
|
||||
|
||||
|
||||
|
||||
</aside>
|
||||
|
||||
</article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
155
public/posts/annotatedapplicationslists/index.html
Normal file
155
public/posts/annotatedapplicationslists/index.html
Normal file
@ -0,0 +1,155 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="AnnotatedApplicationsList ">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/annotatedapplicationslists/">
|
||||
|
||||
|
||||
<meta property="og:title" content="" />
|
||||
<meta property="og:description" content="AnnotatedApplicationsList " />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://reachableceo.com/posts/annotatedapplicationslists/" /><meta property="article:section" content="posts" />
|
||||
|
||||
|
||||
|
||||
<meta itemprop="name" content="">
|
||||
<meta itemprop="description" content="AnnotatedApplicationsList ">
|
||||
|
||||
<meta itemprop="wordCount" content="1">
|
||||
<meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content=""/>
|
||||
<meta name="twitter:description" content="AnnotatedApplicationsList "/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="flex-l flex-wrap justify-between mw8 center ph3">
|
||||
<header class="mt4 w-100">
|
||||
<aside class="instapaper_ignoref b helvetica tracked ttu">
|
||||
|
||||
Posts
|
||||
</aside>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div id="sharing" class="mt3 ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<h1 class="f1 athelas mt3 mb1"></h1>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
<div class="nested-copy-line-height lh-copy serif f4 nested-links mid-gray pr4-l w-two-thirds-l"><h1 id="annotatedapplicationslist">AnnotatedApplicationsList</h1>
|
||||
<ul class="pa0">
|
||||
|
||||
</ul>
|
||||
<div class="mt6 instapaper_ignoref">
|
||||
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<aside class="w-30-l mt6-l">
|
||||
|
||||
|
||||
|
||||
|
||||
</aside>
|
||||
|
||||
</article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
184
public/posts/dailyschedule/index.html
Normal file
184
public/posts/dailyschedule/index.html
Normal file
@ -0,0 +1,184 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>Daily Schedule | ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="Context Over the past year or so, I’ve been maintaining an 18/6 schedule (awake 18 hours, asleep 6 hours).
|
||||
Here is how I am currently allocating time:
|
||||
Daily (weekdays) 00:00 - 06:30 Sleep. 06:30 - 07:00 Morning routine 07:00 - 11:00 commute, breakfast, household maintenance, light personal/TSYS admin tasks 11:00 - 19:00 $DAYJOB from my home office 19:00 - 22:00 dinner with partner, relaxing, exercise 22:00 - 00:00 deep work Saturday 8am to 8pm TSYS work Sunday Completely off (relaxing, exercising, household projects etc) ">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/dailyschedule/">
|
||||
|
||||
|
||||
<meta property="og:title" content="Daily Schedule" />
|
||||
<meta property="og:description" content="Context Over the past year or so, I’ve been maintaining an 18/6 schedule (awake 18 hours, asleep 6 hours).
|
||||
Here is how I am currently allocating time:
|
||||
Daily (weekdays) 00:00 - 06:30 Sleep. 06:30 - 07:00 Morning routine 07:00 - 11:00 commute, breakfast, household maintenance, light personal/TSYS admin tasks 11:00 - 19:00 $DAYJOB from my home office 19:00 - 22:00 dinner with partner, relaxing, exercise 22:00 - 00:00 deep work Saturday 8am to 8pm TSYS work Sunday Completely off (relaxing, exercising, household projects etc) " />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://reachableceo.com/posts/dailyschedule/" /><meta property="article:section" content="posts" />
|
||||
<meta property="article:published_time" content="2024-05-15T09:26:11-05:00" />
|
||||
<meta property="article:modified_time" content="2024-05-15T09:26:11-05:00" />
|
||||
|
||||
<meta itemprop="name" content="Daily Schedule">
|
||||
<meta itemprop="description" content="Context Over the past year or so, I’ve been maintaining an 18/6 schedule (awake 18 hours, asleep 6 hours).
|
||||
Here is how I am currently allocating time:
|
||||
Daily (weekdays) 00:00 - 06:30 Sleep. 06:30 - 07:00 Morning routine 07:00 - 11:00 commute, breakfast, household maintenance, light personal/TSYS admin tasks 11:00 - 19:00 $DAYJOB from my home office 19:00 - 22:00 dinner with partner, relaxing, exercise 22:00 - 00:00 deep work Saturday 8am to 8pm TSYS work Sunday Completely off (relaxing, exercising, household projects etc) "><meta itemprop="datePublished" content="2024-05-15T09:26:11-05:00" />
|
||||
<meta itemprop="dateModified" content="2024-05-15T09:26:11-05:00" />
|
||||
<meta itemprop="wordCount" content="84">
|
||||
<meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="Daily Schedule"/>
|
||||
<meta name="twitter:description" content="Context Over the past year or so, I’ve been maintaining an 18/6 schedule (awake 18 hours, asleep 6 hours).
|
||||
Here is how I am currently allocating time:
|
||||
Daily (weekdays) 00:00 - 06:30 Sleep. 06:30 - 07:00 Morning routine 07:00 - 11:00 commute, breakfast, household maintenance, light personal/TSYS admin tasks 11:00 - 19:00 $DAYJOB from my home office 19:00 - 22:00 dinner with partner, relaxing, exercise 22:00 - 00:00 deep work Saturday 8am to 8pm TSYS work Sunday Completely off (relaxing, exercising, household projects etc) "/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="flex-l flex-wrap justify-between mw8 center ph3">
|
||||
<header class="mt4 w-100">
|
||||
<aside class="instapaper_ignoref b helvetica tracked ttu">
|
||||
|
||||
Posts
|
||||
</aside>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div id="sharing" class="mt3 ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<h1 class="f1 athelas mt3 mb1">Daily Schedule</h1>
|
||||
|
||||
|
||||
|
||||
<time class="f6 mv4 dib tracked" datetime="2024-05-15T09:26:11-05:00">May 15, 2024</time>
|
||||
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
<div class="nested-copy-line-height lh-copy serif f4 nested-links mid-gray pr4-l w-two-thirds-l"><h2 id="context">Context</h2>
|
||||
<p>Over the past year or so, I’ve been maintaining an 18/6 schedule (awake 18 hours, asleep 6 hours).</p>
|
||||
<p>Here is how I am currently allocating time:</p>
|
||||
<h3 id="daily-weekdays">Daily (weekdays)</h3>
|
||||
<ul>
|
||||
<li>00:00 - 06:30 Sleep.</li>
|
||||
<li>06:30 - 07:00 Morning routine</li>
|
||||
<li>07:00 - 11:00 commute, breakfast, household maintenance, light personal/TSYS admin tasks</li>
|
||||
<li>11:00 - 19:00 $DAYJOB from my home office</li>
|
||||
<li>19:00 - 22:00 dinner with partner, relaxing, exercise</li>
|
||||
<li>22:00 - 00:00 deep work</li>
|
||||
</ul>
|
||||
<h3 id="saturday">Saturday</h3>
|
||||
<ul>
|
||||
<li>8am to 8pm TSYS work</li>
|
||||
</ul>
|
||||
<h3 id="sunday">Sunday</h3>
|
||||
<ul>
|
||||
<li>Completely off (relaxing, exercising, household projects etc)</li>
|
||||
</ul>
|
||||
<ul class="pa0">
|
||||
|
||||
</ul>
|
||||
<div class="mt6 instapaper_ignoref">
|
||||
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<aside class="w-30-l mt6-l">
|
||||
|
||||
|
||||
|
||||
|
||||
</aside>
|
||||
|
||||
</article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
172
public/posts/docker-setup/index.html
Normal file
172
public/posts/docker-setup/index.html
Normal file
@ -0,0 +1,172 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="Docker Containers and setup on ReachableCEO workstation Introduction I am a very heavy user of Docker containers. This post documents how I use them personally and as CTO of a hardware/software startup.
|
||||
Read First Read my general workstation setup post.
|
||||
Servers Production (cloudron) Production (on-premise) R&D Containers ">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/docker-setup/">
|
||||
|
||||
|
||||
<meta property="og:title" content="" />
|
||||
<meta property="og:description" content="Docker Containers and setup on ReachableCEO workstation Introduction I am a very heavy user of Docker containers. This post documents how I use them personally and as CTO of a hardware/software startup.
|
||||
Read First Read my general workstation setup post.
|
||||
Servers Production (cloudron) Production (on-premise) R&D Containers " />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://reachableceo.com/posts/docker-setup/" /><meta property="article:section" content="posts" />
|
||||
|
||||
|
||||
|
||||
<meta itemprop="name" content="">
|
||||
<meta itemprop="description" content="Docker Containers and setup on ReachableCEO workstation Introduction I am a very heavy user of Docker containers. This post documents how I use them personally and as CTO of a hardware/software startup.
|
||||
Read First Read my general workstation setup post.
|
||||
Servers Production (cloudron) Production (on-premise) R&D Containers ">
|
||||
|
||||
<meta itemprop="wordCount" content="47">
|
||||
<meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content=""/>
|
||||
<meta name="twitter:description" content="Docker Containers and setup on ReachableCEO workstation Introduction I am a very heavy user of Docker containers. This post documents how I use them personally and as CTO of a hardware/software startup.
|
||||
Read First Read my general workstation setup post.
|
||||
Servers Production (cloudron) Production (on-premise) R&D Containers "/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="flex-l flex-wrap justify-between mw8 center ph3">
|
||||
<header class="mt4 w-100">
|
||||
<aside class="instapaper_ignoref b helvetica tracked ttu">
|
||||
|
||||
Posts
|
||||
</aside>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div id="sharing" class="mt3 ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<h1 class="f1 athelas mt3 mb1"></h1>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
<div class="nested-copy-line-height lh-copy serif f4 nested-links mid-gray pr4-l w-two-thirds-l"><h1 id="docker-containers-and-setup-on-reachableceo-workstation">Docker Containers and setup on ReachableCEO workstation</h1>
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<p>I am a very heavy user of Docker containers. This post documents how I use them personally and as CTO of a hardware/software startup.</p>
|
||||
<h2 id="read-first">Read First</h2>
|
||||
<p>Read my general workstation setup post.</p>
|
||||
<h2 id="servers">Servers</h2>
|
||||
<h3 id="production-cloudron">Production (cloudron)</h3>
|
||||
<h3 id="production-on-premise">Production (on-premise)</h3>
|
||||
<h3 id="rd">R&D</h3>
|
||||
<h2 id="containers">Containers</h2>
|
||||
<ul class="pa0">
|
||||
|
||||
</ul>
|
||||
<div class="mt6 instapaper_ignoref">
|
||||
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<aside class="w-30-l mt6-l">
|
||||
|
||||
|
||||
|
||||
|
||||
</aside>
|
||||
|
||||
</article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
158
public/posts/generalworkstationsetupnotes/index.html
Normal file
158
public/posts/generalworkstationsetupnotes/index.html
Normal file
@ -0,0 +1,158 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="General workstations setup notes of the @ReachableCEO workstation Introduction OS Accounts ">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/generalworkstationsetupnotes/">
|
||||
|
||||
|
||||
<meta property="og:title" content="" />
|
||||
<meta property="og:description" content="General workstations setup notes of the @ReachableCEO workstation Introduction OS Accounts " />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://reachableceo.com/posts/generalworkstationsetupnotes/" /><meta property="article:section" content="posts" />
|
||||
|
||||
|
||||
|
||||
<meta itemprop="name" content="">
|
||||
<meta itemprop="description" content="General workstations setup notes of the @ReachableCEO workstation Introduction OS Accounts ">
|
||||
|
||||
<meta itemprop="wordCount" content="11">
|
||||
<meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content=""/>
|
||||
<meta name="twitter:description" content="General workstations setup notes of the @ReachableCEO workstation Introduction OS Accounts "/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="flex-l flex-wrap justify-between mw8 center ph3">
|
||||
<header class="mt4 w-100">
|
||||
<aside class="instapaper_ignoref b helvetica tracked ttu">
|
||||
|
||||
Posts
|
||||
</aside>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div id="sharing" class="mt3 ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<h1 class="f1 athelas mt3 mb1"></h1>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
<div class="nested-copy-line-height lh-copy serif f4 nested-links mid-gray pr4-l w-two-thirds-l"><h1 id="general-workstations-setup-notes-of-the-reachableceo-workstation">General workstations setup notes of the @ReachableCEO workstation</h1>
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<h2 id="os">OS</h2>
|
||||
<h2 id="accounts">Accounts</h2>
|
||||
<ul class="pa0">
|
||||
|
||||
</ul>
|
||||
<div class="mt6 instapaper_ignoref">
|
||||
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<aside class="w-30-l mt6-l">
|
||||
|
||||
|
||||
|
||||
|
||||
</aside>
|
||||
|
||||
</article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
167
public/posts/holdingmyselftoaccount/index.html
Normal file
167
public/posts/holdingmyselftoaccount/index.html
Normal file
@ -0,0 +1,167 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="Over the last quarter or so, I have been holding (regular) 1 on 1 meetings with members of the TSYS board of directors and advisory board. I have been getting high quality feedback, perspective, analysis.
|
||||
The overall message is to be outcome focused. Delegate as much as possible. Focus on being CEO (get out of the COO/CIO/CTO aspects).
|
||||
The immediate action that I’m taking, is to update this blog on a regular basis, with Daily Standup posts.">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/holdingmyselftoaccount/">
|
||||
|
||||
|
||||
<meta property="og:title" content="" />
|
||||
<meta property="og:description" content="Over the last quarter or so, I have been holding (regular) 1 on 1 meetings with members of the TSYS board of directors and advisory board. I have been getting high quality feedback, perspective, analysis.
|
||||
The overall message is to be outcome focused. Delegate as much as possible. Focus on being CEO (get out of the COO/CIO/CTO aspects).
|
||||
The immediate action that I’m taking, is to update this blog on a regular basis, with Daily Standup posts." />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://reachableceo.com/posts/holdingmyselftoaccount/" /><meta property="article:section" content="posts" />
|
||||
|
||||
|
||||
|
||||
<meta itemprop="name" content="">
|
||||
<meta itemprop="description" content="Over the last quarter or so, I have been holding (regular) 1 on 1 meetings with members of the TSYS board of directors and advisory board. I have been getting high quality feedback, perspective, analysis.
|
||||
The overall message is to be outcome focused. Delegate as much as possible. Focus on being CEO (get out of the COO/CIO/CTO aspects).
|
||||
The immediate action that I’m taking, is to update this blog on a regular basis, with Daily Standup posts.">
|
||||
|
||||
<meta itemprop="wordCount" content="118">
|
||||
<meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content=""/>
|
||||
<meta name="twitter:description" content="Over the last quarter or so, I have been holding (regular) 1 on 1 meetings with members of the TSYS board of directors and advisory board. I have been getting high quality feedback, perspective, analysis.
|
||||
The overall message is to be outcome focused. Delegate as much as possible. Focus on being CEO (get out of the COO/CIO/CTO aspects).
|
||||
The immediate action that I’m taking, is to update this blog on a regular basis, with Daily Standup posts."/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="flex-l flex-wrap justify-between mw8 center ph3">
|
||||
<header class="mt4 w-100">
|
||||
<aside class="instapaper_ignoref b helvetica tracked ttu">
|
||||
|
||||
Posts
|
||||
</aside>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div id="sharing" class="mt3 ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<h1 class="f1 athelas mt3 mb1"></h1>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
<div class="nested-copy-line-height lh-copy serif f4 nested-links mid-gray pr4-l w-two-thirds-l"><p>Over the last quarter or so, I have been holding (regular) 1 on 1 meetings with members of the TSYS board of directors and advisory board. I have been
|
||||
getting high quality feedback, perspective, analysis.</p>
|
||||
<p>The overall message is to be outcome focused. Delegate as much as possible. Focus on being CEO (get out of the COO/CIO/CTO aspects).</p>
|
||||
<p>The immediate action that I’m taking, is to update this blog on a regular basis, with Daily Standup posts. This will ensure that I remain transparent and accountable to all stakeholders in the TSYS Group mission.</p>
|
||||
<p>The posts will be updated as I progress, and then a “finished/shipped” label will be applied (and post will be added to that category).</p>
|
||||
<ul class="pa0">
|
||||
|
||||
</ul>
|
||||
<div class="mt6 instapaper_ignoref">
|
||||
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<aside class="w-30-l mt6-l">
|
||||
|
||||
|
||||
|
||||
|
||||
</aside>
|
||||
|
||||
</article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
212
public/posts/howiorganizemyresearch/index.html
Normal file
212
public/posts/howiorganizemyresearch/index.html
Normal file
@ -0,0 +1,212 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="How I Organize My Research Archive Introduction As (acting as of 04/14/2021) CTO of an incredibly complex product/services portfolio, I have a large amount of research material. I am writing this note on how I organize it and make it fully available to the world without any overhead on my part.
|
||||
Short version:
|
||||
Documents This means PDF, print to PDF of web page, other file types (doc/xls/whatever)
|
||||
Bookmark the link where’er is appropriate in my taxonomy.">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/howiorganizemyresearch/">
|
||||
|
||||
|
||||
<meta property="og:title" content="" />
|
||||
<meta property="og:description" content="How I Organize My Research Archive Introduction As (acting as of 04/14/2021) CTO of an incredibly complex product/services portfolio, I have a large amount of research material. I am writing this note on how I organize it and make it fully available to the world without any overhead on my part.
|
||||
Short version:
|
||||
Documents This means PDF, print to PDF of web page, other file types (doc/xls/whatever)
|
||||
Bookmark the link where’er is appropriate in my taxonomy." />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://reachableceo.com/posts/howiorganizemyresearch/" /><meta property="article:section" content="posts" />
|
||||
|
||||
|
||||
|
||||
<meta itemprop="name" content="">
|
||||
<meta itemprop="description" content="How I Organize My Research Archive Introduction As (acting as of 04/14/2021) CTO of an incredibly complex product/services portfolio, I have a large amount of research material. I am writing this note on how I organize it and make it fully available to the world without any overhead on my part.
|
||||
Short version:
|
||||
Documents This means PDF, print to PDF of web page, other file types (doc/xls/whatever)
|
||||
Bookmark the link where’er is appropriate in my taxonomy.">
|
||||
|
||||
<meta itemprop="wordCount" content="284">
|
||||
<meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content=""/>
|
||||
<meta name="twitter:description" content="How I Organize My Research Archive Introduction As (acting as of 04/14/2021) CTO of an incredibly complex product/services portfolio, I have a large amount of research material. I am writing this note on how I organize it and make it fully available to the world without any overhead on my part.
|
||||
Short version:
|
||||
Documents This means PDF, print to PDF of web page, other file types (doc/xls/whatever)
|
||||
Bookmark the link where’er is appropriate in my taxonomy."/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="flex-l flex-wrap justify-between mw8 center ph3">
|
||||
<header class="mt4 w-100">
|
||||
<aside class="instapaper_ignoref b helvetica tracked ttu">
|
||||
|
||||
Posts
|
||||
</aside>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div id="sharing" class="mt3 ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<h1 class="f1 athelas mt3 mb1"></h1>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
<div class="nested-copy-line-height lh-copy serif f4 nested-links mid-gray pr4-l w-two-thirds-l"><h1 id="how-i-organize-my-research-archive">How I Organize My Research Archive</h1>
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<p>As (acting as of 04/14/2021) CTO of an incredibly complex product/services portfolio, I have a large amount of research material. I am writing this note on how I organize it and make it fully available to the world without any overhead on my part.</p>
|
||||
<p>Short version:</p>
|
||||
<h3 id="documents">Documents</h3>
|
||||
<p>This means PDF, print to PDF of web page, other file types (doc/xls/whatever)</p>
|
||||
<ol>
|
||||
<li>Bookmark the link where’er is appropriate in my taxonomy.</li>
|
||||
<li>Download the URI to ~/ResearchMaterial</li>
|
||||
<li>calibre (on Raberry pi) is using ~/ResearchMaterial and that folder is synced via nextcloud to the corporate file server so I can also use Docear/Polar/Zotero on my x86 vm</li>
|
||||
</ol>
|
||||
<h3 id="notes">NOtes</h3>
|
||||
<p>I use this git repository (notes-public) with a folder of markdown files.</p>
|
||||
<p>I primarily use VsCode on the ras pi todo note taking (and of course longer document creation)
|
||||
Occasionally on mobile (iOS), I use Buffer and the WorkingCopy git client to make quick edits or capture something when I"m out
|
||||
and get inspired.</p>
|
||||
<p>I heavily use Working Copy on my iPad Mini 5th Generation to do code review, issue cleanup etc and I use Calibre to load up a long research paepr and read it over. I also may access the folder directly via samba if I want to annotate.</p>
|
||||
<h2 id="source-material">Source material</h2>
|
||||
<ul>
|
||||
<li><a href="https://blogs.princeton.edu/librarian/2013/05/organizing-my-research-life-updated/">https://blogs.princeton.edu/librarian/2013/05/organizing-my-research-life-updated/</a></li>
|
||||
</ul>
|
||||
<h2 id="more-detailed-version">More detailed version</h2>
|
||||
<h3 id="taxonomy">Taxonomy</h3>
|
||||
<p>I use a single taxonomy across:</p>
|
||||
<ul>
|
||||
<li>e-mail folders</li>
|
||||
<li>bookmarks</li>
|
||||
<li>home directory</li>
|
||||
<li>notes folder (this repository)</li>
|
||||
</ul>
|
||||
<p>It is:</p>
|
||||
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-console" data-lang="console"><span style="display:flex;"><span>❯ ls
|
||||
</span></span><span style="display:flex;"><span>Board CEO CFO CIO CMO COO CTO dotfiles dotfiles-git landed notes-public personal PFVEMer
|
||||
</span></span><span style="display:flex;"><span> ~/charles 15:03:47
|
||||
</span></span><span style="display:flex;"><span>❯
|
||||
</span></span></code></pre></div><ul>
|
||||
<li>Board</li>
|
||||
<li>CEO</li>
|
||||
<li>CFO</li>
|
||||
<li>CIO</li>
|
||||
<li>COO</li>
|
||||
<li>CMO</li>
|
||||
<li>CTO</li>
|
||||
</ul>
|
||||
<p>I then have division names or project/product names under those folders.</p>
|
||||
<p>More coming soon , still dialing things in.</p>
|
||||
<ul class="pa0">
|
||||
|
||||
</ul>
|
||||
<div class="mt6 instapaper_ignoref">
|
||||
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<aside class="w-30-l mt6-l">
|
||||
|
||||
|
||||
|
||||
|
||||
</aside>
|
||||
|
||||
</article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
289
public/posts/index.html
Normal file
289
public/posts/index.html
Normal file
@ -0,0 +1,289 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link href="/posts/index.xml" rel="alternate" type="application/rss+xml" title="ReachableCEO Homepage" />
|
||||
<link href="/posts/index.xml" rel="feed" type="application/rss+xml" title="ReachableCEO Homepage" />
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/">
|
||||
|
||||
|
||||
<meta property="og:title" content="Posts" />
|
||||
<meta property="og:description" content="" />
|
||||
<meta property="og:type" content="website" />
|
||||
<meta property="og:url" content="https://reachableceo.com/posts/" />
|
||||
|
||||
<meta itemprop="name" content="Posts">
|
||||
<meta itemprop="description" content=""><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="Posts"/>
|
||||
<meta name="twitter:description" content=""/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="pb3-m pb6-l bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
<div class="tc-l pv3 ph3 ph4-ns">
|
||||
<h1 class="f2 f-subheadline-l fw2 light-silver mb0 lh-title">
|
||||
Posts
|
||||
</h1>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
<article class="pa3 pa4-ns nested-copy-line-height">
|
||||
<section class="cf ph3 ph5-l pv3 pv4-l f4 tc-l center measure-wide lh-copy mid-gray"></section>
|
||||
<section class="flex-ns flex-wrap justify-around mt5">
|
||||
|
||||
<div class="relative w-100 w-30-l mb4 bg-white">
|
||||
<div class="relative w-100 mb4 bg-white nested-copy-line-height">
|
||||
<div class="bg-white mb3 pa4 gray overflow-hidden">
|
||||
<span class="f6 db">Posts</span>
|
||||
<h1 class="f3 near-black">
|
||||
<a href="/posts/dailyschedule/" class="link black dim">
|
||||
Daily Schedule
|
||||
</a>
|
||||
</h1>
|
||||
<div class="nested-links f5 lh-copy nested-copy-line-height">
|
||||
Context Over the past year or so, I’ve been maintaining an 18/6 schedule (awake 18 hours, asleep 6 hours).
|
||||
Here is how I am currently allocating time:
|
||||
Daily (weekdays) 00:00 - 06:30 Sleep. 06:30 - 07:00 Morning routine 07:00 - 11:00 commute, breakfast, household maintenance, light personal/TSYS admin tasks 11:00 - 19:00 $DAYJOB from my home office 19:00 - 22:00 dinner with partner, relaxing, exercise 22:00 - 00:00 deep work Saturday 8am to 8pm TSYS work Sunday Completely off (relaxing, exercising, household projects etc)
|
||||
</div>
|
||||
<a href="/posts/dailyschedule/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="relative w-100 w-30-l mb4 bg-white">
|
||||
<div class="relative w-100 mb4 bg-white nested-copy-line-height">
|
||||
<div class="bg-white mb3 pa4 gray overflow-hidden">
|
||||
<span class="f6 db">Posts</span>
|
||||
<h1 class="f3 near-black">
|
||||
<a href="/posts/2024-monthly-objectives-key-results/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h1>
|
||||
<div class="nested-links f5 lh-copy nested-copy-line-height">
|
||||
2024 Monthly Objectives Key Results January: Finish my involvement in critical path of operations and fully delegate operations to COO/CFO
|
||||
February: Prepare outreach material
|
||||
March: Reconnect with my entire network and share the outreach material
|
||||
</div>
|
||||
<a href="/posts/2024-monthly-objectives-key-results/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="relative w-100 w-30-l mb4 bg-white">
|
||||
<div class="relative w-100 mb4 bg-white nested-copy-line-height">
|
||||
<div class="bg-white mb3 pa4 gray overflow-hidden">
|
||||
<span class="f6 db">Posts</span>
|
||||
<h1 class="f3 near-black">
|
||||
<a href="/posts/annotatedapplicationlist/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h1>
|
||||
<div class="nested-links f5 lh-copy nested-copy-line-height">
|
||||
ReachableCEO Workstation Software List Introduction I have created this list of software that I have installed on my workstation as CTO/co-founder of TSYS Group. It is a sub/super set of the comprehensive software/hardware engineering software list in the TSYS Group Handbook.
|
||||
Elmer 7-zip ActivityWatch Adobe Acrobat Android Studio Apache Directory Studio Arduino IDE Audacity AuoHotkey Bitscope Bitwarden Bonita Community Calibre Camotics Camstudio Code Composer Studio Codelite Composer PHP Dependency Manager CubicSDR Darktable Dbeaver Digikam Docear Docker Deskop (see my containers blogpost for my Docker setup) Draw.
|
||||
</div>
|
||||
<a href="/posts/annotatedapplicationlist/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="relative w-100 w-30-l mb4 bg-white">
|
||||
<div class="relative w-100 mb4 bg-white nested-copy-line-height">
|
||||
<div class="bg-white mb3 pa4 gray overflow-hidden">
|
||||
<span class="f6 db">Posts</span>
|
||||
<h1 class="f3 near-black">
|
||||
<a href="/posts/annotatedapplicationslists/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h1>
|
||||
<div class="nested-links f5 lh-copy nested-copy-line-height">
|
||||
AnnotatedApplicationsList
|
||||
</div>
|
||||
<a href="/posts/annotatedapplicationslists/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="relative w-100 w-30-l mb4 bg-white">
|
||||
<div class="relative w-100 mb4 bg-white nested-copy-line-height">
|
||||
<div class="bg-white mb3 pa4 gray overflow-hidden">
|
||||
<span class="f6 db">Posts</span>
|
||||
<h1 class="f3 near-black">
|
||||
<a href="/posts/docker-setup/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h1>
|
||||
<div class="nested-links f5 lh-copy nested-copy-line-height">
|
||||
Docker Containers and setup on ReachableCEO workstation Introduction I am a very heavy user of Docker containers. This post documents how I use them personally and as CTO of a hardware/software startup.
|
||||
Read First Read my general workstation setup post.
|
||||
Servers Production (cloudron) Production (on-premise) R&D Containers
|
||||
</div>
|
||||
<a href="/posts/docker-setup/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="relative w-100 w-30-l mb4 bg-white">
|
||||
<div class="relative w-100 mb4 bg-white nested-copy-line-height">
|
||||
<div class="bg-white mb3 pa4 gray overflow-hidden">
|
||||
<span class="f6 db">Posts</span>
|
||||
<h1 class="f3 near-black">
|
||||
<a href="/posts/generalworkstationsetupnotes/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h1>
|
||||
<div class="nested-links f5 lh-copy nested-copy-line-height">
|
||||
General workstations setup notes of the @ReachableCEO workstation Introduction OS Accounts
|
||||
</div>
|
||||
<a href="/posts/generalworkstationsetupnotes/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="relative w-100 w-30-l mb4 bg-white">
|
||||
<div class="relative w-100 mb4 bg-white nested-copy-line-height">
|
||||
<div class="bg-white mb3 pa4 gray overflow-hidden">
|
||||
<span class="f6 db">Posts</span>
|
||||
<h1 class="f3 near-black">
|
||||
<a href="/posts/holdingmyselftoaccount/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h1>
|
||||
<div class="nested-links f5 lh-copy nested-copy-line-height">
|
||||
Over the last quarter or so, I have been holding (regular) 1 on 1 meetings with members of the TSYS board of directors and advisory board. I have been getting high quality feedback, perspective, analysis.
|
||||
The overall message is to be outcome focused. Delegate as much as possible. Focus on being CEO (get out of the COO/CIO/CTO aspects).
|
||||
The immediate action that I’m taking, is to update this blog on a regular basis, with Daily Standup posts.
|
||||
</div>
|
||||
<a href="/posts/holdingmyselftoaccount/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="relative w-100 w-30-l mb4 bg-white">
|
||||
<div class="relative w-100 mb4 bg-white nested-copy-line-height">
|
||||
<div class="bg-white mb3 pa4 gray overflow-hidden">
|
||||
<span class="f6 db">Posts</span>
|
||||
<h1 class="f3 near-black">
|
||||
<a href="/posts/howiorganizemyresearch/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h1>
|
||||
<div class="nested-links f5 lh-copy nested-copy-line-height">
|
||||
How I Organize My Research Archive Introduction As (acting as of 04/14/2021) CTO of an incredibly complex product/services portfolio, I have a large amount of research material. I am writing this note on how I organize it and make it fully available to the world without any overhead on my part.
|
||||
Short version:
|
||||
Documents This means PDF, print to PDF of web page, other file types (doc/xls/whatever)
|
||||
Bookmark the link where’er is appropriate in my taxonomy.
|
||||
</div>
|
||||
<a href="/posts/howiorganizemyresearch/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="relative w-100 w-30-l mb4 bg-white">
|
||||
<div class="relative w-100 mb4 bg-white nested-copy-line-height">
|
||||
<div class="bg-white mb3 pa4 gray overflow-hidden">
|
||||
<span class="f6 db">Posts</span>
|
||||
<h1 class="f3 near-black">
|
||||
<a href="/posts/orientationtotsysgroup/" class="link black dim">
|
||||
|
||||
</a>
|
||||
</h1>
|
||||
<div class="nested-links f5 lh-copy nested-copy-line-height">
|
||||
Orientation to TSYS Group For Executives and BoD
|
||||
Facilities PFV Cloud Systems Cloudron
|
||||
</div>
|
||||
<a href="/posts/orientationtotsysgroup/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</section></article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
88
public/posts/index.xml
Normal file
88
public/posts/index.xml
Normal file
@ -0,0 +1,88 @@
|
||||
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Posts on ReachableCEO Homepage</title>
|
||||
<link>https://reachableceo.com/posts/</link>
|
||||
<description>Recent content in Posts on ReachableCEO Homepage</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
<lastBuildDate>Wed, 15 May 2024 09:26:11 -0500</lastBuildDate>
|
||||
<atom:link href="https://reachableceo.com/posts/index.xml" rel="self" type="application/rss+xml" />
|
||||
<item>
|
||||
<title>Daily Schedule</title>
|
||||
<link>https://reachableceo.com/posts/dailyschedule/</link>
|
||||
<pubDate>Wed, 15 May 2024 09:26:11 -0500</pubDate>
|
||||
<guid>https://reachableceo.com/posts/dailyschedule/</guid>
|
||||
<description>Context Over the past year or so, I&rsquo;ve been maintaining an 18/6 schedule (awake 18 hours, asleep 6 hours).
|
||||
Here is how I am currently allocating time:
|
||||
Daily (weekdays) 00:00 - 06:30 Sleep. 06:30 - 07:00 Morning routine 07:00 - 11:00 commute, breakfast, household maintenance, light personal/TSYS admin tasks 11:00 - 19:00 $DAYJOB from my home office 19:00 - 22:00 dinner with partner, relaxing, exercise 22:00 - 00:00 deep work Saturday 8am to 8pm TSYS work Sunday Completely off (relaxing, exercising, household projects etc) </description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/2024-monthly-objectives-key-results/</link>
|
||||
<pubDate>Fri, 05 Jan 2024 08:18:51 -0500</pubDate>
|
||||
<guid>https://reachableceo.com/posts/2024-monthly-objectives-key-results/</guid>
|
||||
<description>2024 Monthly Objectives Key Results January: Finish my involvement in critical path of operations and fully delegate operations to COO/CFO
|
||||
February: Prepare outreach material
|
||||
March: Reconnect with my entire network and share the outreach material</description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/annotatedapplicationlist/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/annotatedapplicationlist/</guid>
|
||||
<description>ReachableCEO Workstation Software List Introduction I have created this list of software that I have installed on my workstation as CTO/co-founder of TSYS Group. It is a sub/super set of the comprehensive software/hardware engineering software list in the TSYS Group Handbook.
|
||||
Elmer 7-zip ActivityWatch Adobe Acrobat Android Studio Apache Directory Studio Arduino IDE Audacity AuoHotkey Bitscope Bitwarden Bonita Community Calibre Camotics Camstudio Code Composer Studio Codelite Composer PHP Dependency Manager CubicSDR Darktable Dbeaver Digikam Docear Docker Deskop (see my containers blogpost for my Docker setup) Draw.</description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/annotatedapplicationslists/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/annotatedapplicationslists/</guid>
|
||||
<description>AnnotatedApplicationsList </description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/docker-setup/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/docker-setup/</guid>
|
||||
<description>Docker Containers and setup on ReachableCEO workstation Introduction I am a very heavy user of Docker containers. This post documents how I use them personally and as CTO of a hardware/software startup.
|
||||
Read First Read my general workstation setup post.
|
||||
Servers Production (cloudron) Production (on-premise) R&amp;D Containers </description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/generalworkstationsetupnotes/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/generalworkstationsetupnotes/</guid>
|
||||
<description>General workstations setup notes of the @ReachableCEO workstation Introduction OS Accounts </description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/holdingmyselftoaccount/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/holdingmyselftoaccount/</guid>
|
||||
<description>Over the last quarter or so, I have been holding (regular) 1 on 1 meetings with members of the TSYS board of directors and advisory board. I have been getting high quality feedback, perspective, analysis.
|
||||
The overall message is to be outcome focused. Delegate as much as possible. Focus on being CEO (get out of the COO/CIO/CTO aspects).
|
||||
The immediate action that I&rsquo;m taking, is to update this blog on a regular basis, with Daily Standup posts.</description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/howiorganizemyresearch/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/howiorganizemyresearch/</guid>
|
||||
<description>How I Organize My Research Archive Introduction As (acting as of 04/14/2021) CTO of an incredibly complex product/services portfolio, I have a large amount of research material. I am writing this note on how I organize it and make it fully available to the world without any overhead on my part.
|
||||
Short version:
|
||||
Documents This means PDF, print to PDF of web page, other file types (doc/xls/whatever)
|
||||
Bookmark the link where&rsquo;er is appropriate in my taxonomy.</description>
|
||||
</item>
|
||||
<item>
|
||||
<title></title>
|
||||
<link>https://reachableceo.com/posts/orientationtotsysgroup/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
<guid>https://reachableceo.com/posts/orientationtotsysgroup/</guid>
|
||||
<description>Orientation to TSYS Group For Executives and BoD
|
||||
Facilities PFV Cloud Systems Cloudron </description>
|
||||
</item>
|
||||
</channel>
|
||||
</rss>
|
||||
165
public/posts/orientationtotsysgroup/index.html
Normal file
165
public/posts/orientationtotsysgroup/index.html
Normal file
@ -0,0 +1,165 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="Orientation to TSYS Group For Executives and BoD
|
||||
Facilities PFV Cloud Systems Cloudron ">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/orientationtotsysgroup/">
|
||||
|
||||
|
||||
<meta property="og:title" content="" />
|
||||
<meta property="og:description" content="Orientation to TSYS Group For Executives and BoD
|
||||
Facilities PFV Cloud Systems Cloudron " />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://reachableceo.com/posts/orientationtotsysgroup/" /><meta property="article:section" content="posts" />
|
||||
|
||||
|
||||
|
||||
<meta itemprop="name" content="">
|
||||
<meta itemprop="description" content="Orientation to TSYS Group For Executives and BoD
|
||||
Facilities PFV Cloud Systems Cloudron ">
|
||||
|
||||
<meta itemprop="wordCount" content="13">
|
||||
<meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content=""/>
|
||||
<meta name="twitter:description" content="Orientation to TSYS Group For Executives and BoD
|
||||
Facilities PFV Cloud Systems Cloudron "/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="flex-l flex-wrap justify-between mw8 center ph3">
|
||||
<header class="mt4 w-100">
|
||||
<aside class="instapaper_ignoref b helvetica tracked ttu">
|
||||
|
||||
Posts
|
||||
</aside>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<div id="sharing" class="mt3 ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<h1 class="f1 athelas mt3 mb1"></h1>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
<div class="nested-copy-line-height lh-copy serif f4 nested-links mid-gray pr4-l w-two-thirds-l"><h1 id="orientation-to-tsys-group">Orientation to TSYS Group</h1>
|
||||
<p>For Executives and BoD</p>
|
||||
<h2 id="facilities">Facilities</h2>
|
||||
<h3 id="pfv">PFV</h3>
|
||||
<h3 id="cloud">Cloud</h3>
|
||||
<h2 id="systems">Systems</h2>
|
||||
<h3 id="cloudron">Cloudron</h3>
|
||||
<ul class="pa0">
|
||||
|
||||
</ul>
|
||||
<div class="mt6 instapaper_ignoref">
|
||||
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<aside class="w-30-l mt6-l">
|
||||
|
||||
|
||||
|
||||
|
||||
</aside>
|
||||
|
||||
</article>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
10
public/posts/page/1/index.html
Normal file
10
public/posts/page/1/index.html
Normal file
@ -0,0 +1,10 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<title>https://reachableceo.com/posts/</title>
|
||||
<link rel="canonical" href="https://reachableceo.com/posts/">
|
||||
<meta name="robots" content="noindex">
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="refresh" content="0; url=https://reachableceo.com/posts/">
|
||||
</head>
|
||||
</html>
|
||||
35
public/sitemap.xml
Normal file
35
public/sitemap.xml
Normal file
@ -0,0 +1,35 @@
|
||||
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
|
||||
xmlns:xhtml="http://www.w3.org/1999/xhtml">
|
||||
<url>
|
||||
<loc>https://reachableceo.com/posts/dailyschedule/</loc>
|
||||
<lastmod>2024-05-15T09:26:11-05:00</lastmod>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/posts/</loc>
|
||||
<lastmod>2024-05-15T09:26:11-05:00</lastmod>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/</loc>
|
||||
<lastmod>2024-05-15T09:26:11-05:00</lastmod>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/posts/2024-monthly-objectives-key-results/</loc>
|
||||
<lastmod>2024-01-05T08:18:51-05:00</lastmod>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/posts/annotatedapplicationlist/</loc>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/posts/annotatedapplicationslists/</loc>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/posts/docker-setup/</loc>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/posts/generalworkstationsetupnotes/</loc>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/posts/holdingmyselftoaccount/</loc>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/posts/howiorganizemyresearch/</loc>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/posts/orientationtotsysgroup/</loc>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/categories/</loc>
|
||||
</url><url>
|
||||
<loc>https://reachableceo.com/tags/</loc>
|
||||
</url>
|
||||
</urlset>
|
||||
120
public/tags/index.html
Normal file
120
public/tags/index.html
Normal file
@ -0,0 +1,120 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en-us">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
|
||||
<title>ReachableCEO Homepage</title>
|
||||
<meta name="viewport" content="width=device-width,minimum-scale=1">
|
||||
<meta name="description" content="">
|
||||
<meta name="generator" content="Hugo 0.120.3">
|
||||
|
||||
|
||||
|
||||
|
||||
<meta name="robots" content="noindex, nofollow">
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="stylesheet" href="/ananke/css/main.min.css" >
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<link href="/tags/index.xml" rel="alternate" type="application/rss+xml" title="ReachableCEO Homepage" />
|
||||
<link href="/tags/index.xml" rel="feed" type="application/rss+xml" title="ReachableCEO Homepage" />
|
||||
|
||||
|
||||
|
||||
|
||||
<link rel="canonical" href="https://reachableceo.com/tags/">
|
||||
|
||||
|
||||
<meta property="og:title" content="Tags" />
|
||||
<meta property="og:description" content="" />
|
||||
<meta property="og:type" content="website" />
|
||||
<meta property="og:url" content="https://reachableceo.com/tags/" />
|
||||
|
||||
<meta itemprop="name" content="Tags">
|
||||
<meta itemprop="description" content=""><meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="Tags"/>
|
||||
<meta name="twitter:description" content=""/>
|
||||
|
||||
|
||||
</head>
|
||||
|
||||
<body class="ma0 avenir bg-near-white">
|
||||
|
||||
|
||||
|
||||
<header>
|
||||
<div class="pb3-m pb6-l bg-black">
|
||||
<nav class="pv3 ph3 ph4-ns" role="navigation">
|
||||
<div class="flex-l justify-between items-center center">
|
||||
<a href="/" class="f3 fw2 hover-white no-underline white-90 dib">
|
||||
|
||||
ReachableCEO Homepage
|
||||
|
||||
</a>
|
||||
<div class="flex-l items-center">
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
<div class="tc-l pv3 ph3 ph4-ns">
|
||||
<h1 class="f2 f-subheadline-l fw2 light-silver mb0 lh-title">
|
||||
Tags
|
||||
</h1>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</header>
|
||||
|
||||
|
||||
<main class="pb7" role="main">
|
||||
|
||||
|
||||
<article class="cf pa3 pa4-m pa4-l">
|
||||
<div class="measure-wide-l center f4 lh-copy nested-copy-line-height nested-links mid-gray">
|
||||
|
||||
</div>
|
||||
</article>
|
||||
<div class="mw8 center">
|
||||
<section class="ph4">
|
||||
|
||||
</section>
|
||||
</div>
|
||||
|
||||
</main>
|
||||
<footer class="bg-black bottom-0 w-100 pa3" role="contentinfo">
|
||||
<div class="flex justify-between">
|
||||
<a class="f4 fw4 hover-white no-underline white-70 dn dib-ns pv2 ph3" href="https://reachableceo.com/" >
|
||||
© ReachableCEO Homepage 2024
|
||||
</a>
|
||||
<div>
|
||||
<div class="ananke-socials">
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
11
public/tags/index.xml
Normal file
11
public/tags/index.xml
Normal file
@ -0,0 +1,11 @@
|
||||
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Tags on ReachableCEO Homepage</title>
|
||||
<link>https://reachableceo.com/tags/</link>
|
||||
<description>Recent content in Tags on ReachableCEO Homepage</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
<atom:link href="https://reachableceo.com/tags/index.xml" rel="self" type="application/rss+xml" />
|
||||
</channel>
|
||||
</rss>
|
||||
11
static/CIO-RDIT-PickNPlace
Normal file
11
static/CIO-RDIT-PickNPlace
Normal file
@ -0,0 +1,11 @@
|
||||
# RdIT: PCB Assembly/rework workflow
|
||||
|
||||
## Pick N Place Machine
|
||||
|
||||
- <https://www.priority1design.com.au/DIY_pick_and_place_machine.html>
|
||||
- <https://mcuoneclipse.com/2018/06/26/building-a-diy-smt-pickplace-machine-with-openpnp/>
|
||||
- <https://dzone.com/articles/diy-smt-pick-and-place-machine-with-openpnp>
|
||||
- <https://hackaday.com/2015/02/06/a-diy-pick-and-place-you-can-build-right-now/>
|
||||
- <https://docs.indexmachines.io/docs/>
|
||||
|
||||
Some combination of the above is arriving (currently projected) in March 2022 from a kickstarter campaign.
|
||||
Binary file not shown.
Binary file not shown.
54
static/DiscordMove.txt
Normal file
54
static/DiscordMove.txt
Normal file
@ -0,0 +1,54 @@
|
||||
#################################
|
||||
|
||||
Outreach capture
|
||||
|
||||
|
||||
https://www.reddit.com/r/sysadminjobs/comments/p51mu1/pre_revenue_bootstrap_flo_startup_coop_seeking/?utm_source=share&utm_medium=ios_app&utm_name=iossmf
|
||||
|
||||
|
||||
|
||||
## Locate and move to Nextcloud:
|
||||
|
||||
https://git.turnsys.com/TSG/PitchDeck/src/branch/master/SbirPitch
|
||||
https://git.turnsys.com/TSG/PitchDeck/src/branch/master/RFIResponse-W56KGY-18-R-AISR.pdf
|
||||
https://git.turnsys.com/TSG/PitchDeck/src/branch/master/SBIR-STTR%20Submitted%20Project%20Pitch.pdf
|
||||
|
||||
|
||||
https://arstechnica.com/information-technology/2021/08/excerpt-the-history-of-android-as-written-by-a-longtime-android-developer/
|
||||
https://www.cnx-software.com/2022/02/21/low-power-satellite-iot-soc-works-with-totums-low-earth-orbit-leo-network/
|
||||
https://newsletter.spacedotbiz.com/p/starship-really-going-revolutionize-launch-costs
|
||||
|
||||
|
||||
#################################
|
||||
|
||||
|
||||
#################################
|
||||
|
||||
Subo devlog capture
|
||||
|
||||
https://www.openfoam.com/
|
||||
https://www.google.com/search?q=open+source+wind+tunnel+&rlz=1CDGOYI_enUS945US945&hl=en-US&sourceid=chrome-mobile&ie=UTF-8
|
||||
https://sourceforge.net/directory/science-engineering/mechcivileng/
|
||||
https://github.com/jetsonhacks/installGrinch
|
||||
|
||||
https://github.com/TomasTT7/Heat_Sealer
|
||||
https://github.com/TomasTT7/Pre-Stretching_Rig
|
||||
https://github.com/TomasTT7/SuperpressureBalloonsNotebook
|
||||
http://tt7hab.blogspot.com/2017/04/the-superpressure-balloons.html
|
||||
http://flatcam.org/
|
||||
|
||||
https://connectivity-staging.s3.us-east-2.amazonaws.com/s3fs-public/2019-03/Pre-Scan-White-Paper-v1_0.pdf
|
||||
https://erainstruments.com/
|
||||
http://eor.berkeley.edu/wp-content/uploads/2011/09/p004.rbradley.pdf
|
||||
|
||||
https://www.instructables.com/Thermal-test-chamber-for-edge-of-space-testing.-D/
|
||||
|
||||
|
||||
https://github.com/osqzss/gps-sdr-sim
|
||||
|
||||
https://cpham.perso.univ-pau.fr/LORA/RPIgateway.html
|
||||
|
||||
|
||||
|
||||
https://github.com/INTI-CMNB/kicad_auto
|
||||
|
||||
316
static/DiscourseMove.md
Normal file
316
static/DiscourseMove.md
Normal file
@ -0,0 +1,316 @@
|
||||
- [Discourse-Mov e](#discourse-mov-e)
|
||||
- [Target : Handbook CIO](#target--handbook-cio)
|
||||
- [Camera](#camera)
|
||||
- [SSH to systems](#ssh-to-systems)
|
||||
- [SSH config snippet](#ssh-config-snippet)
|
||||
- [access tester script](#access-tester-script)
|
||||
- [Factory as Product](#factory-as-product)
|
||||
- [Supporting infrastructure](#supporting-infrastructure)
|
||||
- [Inventory](#inventory)
|
||||
- [Component Inventory](#component-inventory)
|
||||
- [Tool Inventory](#tool-inventory)
|
||||
- [Equipment Inventory](#equipment-inventory)
|
||||
- [Bench top Equipment List](#bench-top-equipment-list)
|
||||
- [Target: KNEL Discourse](#target-knel-discourse)
|
||||
- [Target: Nextcloud](#target-nextcloud)
|
||||
- [Target : Handbook CTO](#target--handbook-cto)
|
||||
- [Avionics Mock up](#avionics-mock-up)
|
||||
- [Avionics Test bed](#avionics-test-bed)
|
||||
|
||||
# Discourse-Mov e
|
||||
|
||||
|
||||
## Target : Handbook CIO
|
||||
|
||||
### Camera
|
||||
|
||||
(screen cap of the stream)
|
||||
|
||||
admin/subodev
|
||||
click server push mode
|
||||
|
||||
you’ll have access to the live lab cam. this is useful for working on hardware remotely when you need to checkout antenna movement, parafoil movement etc
|
||||
|
||||
it’s also infrared, so works in the dark (i keep a few constant low light sources going in the garage as required by code)
|
||||
|
||||
plus the camera has infrared led that auto activate/de-activate with light off/on
|
||||
|
||||
### SSH to systems
|
||||
|
||||
If you are working on suborbital development for tsys, this article contains all the access particulars.
|
||||
|
||||
## SSH config snippet
|
||||
|
||||
```
|
||||
#######################################################################################################
|
||||
#Development systems - Suborbital Systems/MeetMorse
|
||||
#######################################################################################################
|
||||
|
||||
#######################################################################################################
|
||||
#raspberry pi units for groundstation/avionics test/etc
|
||||
#######################################################################################################
|
||||
|
||||
Host subopi1
|
||||
Hostname 10.251.10.4
|
||||
User pi
|
||||
|
||||
Host subopi2
|
||||
Hostname 10.251.10.5
|
||||
User pi
|
||||
|
||||
Host subopi3
|
||||
Hostname 10.251.10.6
|
||||
User pi
|
||||
|
||||
Host subopi4
|
||||
Hostname 10.251.10.7
|
||||
User pi
|
||||
|
||||
|
||||
Host subopi5
|
||||
Hostname 10.251.10.8
|
||||
User pi
|
||||
|
||||
|
||||
Host subopi6
|
||||
Hostname 10.251.10.9
|
||||
User pi
|
||||
|
||||
|
||||
#######################################################################################################
|
||||
#support systems for lab equipment control, dev/qa/prod infra
|
||||
#######################################################################################################
|
||||
|
||||
Host subobench
|
||||
Hostname 10.251.10.3
|
||||
User pi
|
||||
|
||||
Host subodev
|
||||
Hostname 10.251.10.240
|
||||
User subodev
|
||||
Host suboqa
|
||||
Hostname 10.251.10.241
|
||||
User subodev
|
||||
|
||||
Host suboprod
|
||||
Hostname 10.251.10.242
|
||||
User subodev
|
||||
|
||||
Host buildbox
|
||||
User localuser
|
||||
Hostname 10.251.30.82
|
||||
|
||||
```
|
||||
|
||||
## access tester script
|
||||
|
||||
```
|
||||
#!/bin/bash
|
||||
|
||||
IFS=$'\n\t'
|
||||
|
||||
suboNodeList=(
|
||||
"subopi1" #MorsePod m6
|
||||
"subopi2" #seeduino lora gateway hat
|
||||
"subopi3" # no hat
|
||||
"subopi4" #dragino hat
|
||||
"subopi5" #pi sense hat
|
||||
"subopi6" #pi sense hat
|
||||
"subodev" #develop workloads
|
||||
"suboqa" #test workloads
|
||||
"suboprod" #run actual workloads here
|
||||
"buildbox" #build all the things
|
||||
"subobench" #benchtop computer
|
||||
)
|
||||
|
||||
for suboNode in ${suboNodeList[@]}; do
|
||||
#COMMAND="$(ssh $suboNode md5sum .ssh/authorized_keys)"
|
||||
#echo "Testing ssh authorized_keys on $suboNode" $COMMAND
|
||||
#COMMAND="$(ssh $suboNode date )"
|
||||
#echo "Testing on $suboNode" $COMMAND
|
||||
COMMAND="$(ssh $suboNode uptime)"
|
||||
echo "Testing load on $suboNode" $COMMAND
|
||||
done
|
||||
|
||||
```
|
||||
|
||||
### Factory as Product
|
||||
|
||||
In the spirit of :
|
||||
|
||||
1) reproducibility
|
||||
2) factory as product
|
||||
|
||||
We are documenting the TSYS shop/lab in detail, so that others can build out a lab. We hope this document becomes the premier internet "one stop shop" resource for lab builders . It took us quite a bit of time/experimenting/reading/working on projects to figure out what was needed. We have documented the results of all that here, to save you the effort!
|
||||
|
||||
Below please find the individual articles on various sub module topics that we've written.
|
||||
|
||||
|
||||
#### Supporting infrastructure
|
||||
|
||||
* https://community.turnsys.com/t/tsys-electronics-lab-supporting-infrastructure/155 (was just an outline, deleted the topic and will re-create from scratch in handbook)
|
||||
|
||||
#### Inventory
|
||||
|
||||
|
||||
##### Component Inventory
|
||||
|
||||
TODO
|
||||
|
||||
* https://community.turnsys.com/t/tsys-electronics-lab-component-inventory/156/2
|
||||
|
||||
Ah yes.... this is probably the most controversial topic in our lab series. What components to stock. The short answer: depends on what you are doing. However many projects need common items. So we will only include things we consider essential for a wide majority of projects. We will do separate posts in a separate series for anything suborbtial prototype/production specific.
|
||||
|
||||
(link to nextcloud hosted spreadsheet here)
|
||||
|
||||
|
||||
##### Tool Inventory
|
||||
|
||||
TODO Add pics of all the drawers
|
||||
|
||||
|
||||
Inputs we used to build the list:
|
||||
|
||||
* https://predictabledesigns.com/electronic-lab-setup-tools-and-equipment-requirements/
|
||||
* https://www.engineersgarage.com/tutorials/articles-beginners-guide-to-setup-electronics-lab/
|
||||
* https://www.instructables.com/Electronics-Workbench-Equipment-List/
|
||||
* https://www.jaysonjc.com/diy/how-to-set-up-an-electronics-labworkshop-at-home.html
|
||||
|
||||
and just a general google of "electronics workbench setup" "electronics lab build" etc.
|
||||
|
||||
Our list contains everything in common between the above lists, as well as the unique items from each list, and a few additional items we've found to be useful.
|
||||
|
||||
This is a wiki post, and will be updated by everyone as we go forward. Since I did the initial build, I am doing initial documentation.
|
||||
|
||||
* Fire Suppression : https://www.firstalert.com/fire-extinguishers/ez-fire-spray/
|
||||
* PCB vise: https://www.panavise.com/index.html?pageID=1&page=full&--eqskudatarq=503
|
||||
* Hand Tool Storage (see next section for documentation of contents)
|
||||
|
||||
|
||||
from bottom drawer to top drawer (with toolbox last) (we consider the drawers/toolbox a single unit) (see next section for the links to the drawers/toolbox containers we use)
|
||||
|
||||
Optics Drawer:
|
||||
|
||||
* Handheld standard magnifying glass
|
||||
* Headband LED magnifier: https://www.jensentools.com/eclipse-proskit-ma-016-headband-led-magnifier/p/711in016
|
||||
|
||||
Screwdriver Drawer:
|
||||
|
||||
* Precision screwdriver set: https://www.geekbuying.com/item/JVMAC-2408A-16-in-1-Toolset-Screwdriver-Repair-Tools-Kit-Set-For-Mobile-Phone-Electronics-366037.html
|
||||
* Misc screwdrivers (jewelers set, pen multi tip screwdrivers)
|
||||
|
||||
Cut / File / Strip Drawer:
|
||||
|
||||
* Hand file set: https://www.homedepot.com/p/Husky-Multi-Purpose-File-Set-10-Piece-H10PCFS/206313272
|
||||
* Utility Shears: https://www.harborfreight.com/6-inch-utility-shears-67145.html
|
||||
* Hole Punch Set: https://www.walmart.com/ip/Hyper-Tough-Ht-6pc-Pin-Punch-Set/17325866
|
||||
* Wire Strippers: https://www.walmart.com/ip/Hyper-Tough-6-Inch-Wire-Stripper-with-Non-Slip-Grips/296832054
|
||||
|
||||
Precision Tools Drawer:
|
||||
|
||||
* Precision Knife Set: https://www.harborfreight.com/56-piece-precision-knife-set-36410.html
|
||||
* non esd tweezers: https://www.harborfreight.com/6-pc-fine-point-tweezer-set-93598.html?_br_psugg_q=tweezers
|
||||
|
||||
* esd safe tweezers:
|
||||
https://www.adafruit.com/product/421
|
||||
https://www.adafruit.com/product/422
|
||||
https://www.ifixit.com/Store/Tools/Precision-Tweezers-Set/IF145-060?o=3
|
||||
|
||||
* Flush cutters: https://www.altex.com/xuron-micro-shear-flush-cutter-with-lead-retaining-clip
|
||||
|
||||
Measuring Drawer
|
||||
|
||||
* Tape Measure: https://www.walmart.com/ip/Hyper-Tough-12-Foot-Tape-Measure-with-Large-Markings/792496412
|
||||
* Level: https://www.walmart.com/ip/Hyper-Tough-9-Inch-Level-with-90-Degree-Quick-Check/624249115
|
||||
|
||||
Soldering Drawer
|
||||
|
||||
* Solder: https://www.altex.com/mg-chemicals-4900-18g-21-gauge-lead-free-solder-pocket-pack
|
||||
* Soldering Flux: https://www.altex.com/caig-rosin-soldering-flux
|
||||
* Liquid Soldering Flux: https://www.altex.com/gc-liquid-solder-flux-2-oz.
|
||||
* No clean flux paste: https://www.altex.com/m.g.-chemicals-no-clean-flux-paste-10ml
|
||||
* Paste Flux: https://www.altex.com/qualitek-paste-flux-2-oz.
|
||||
* Hakko 599B : https://www.hakko.com/english/products/hakko_599b.html
|
||||
* Digital Calipers : (don’t remember where mine came from. Frys?. Available from many retailers).
|
||||
|
||||
|
||||
Prototyping Drawer
|
||||
|
||||
* Breadboards: https://www.amazon.com/gp/product/B07DL13RZH/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
|
||||
* SOIC Clip: https://www.amazon.com/CPT-063-Test-Clip-SOIC8-Pomona/dp/B00HHH65T4/ref=sr_1_3?dchild=1&keywords=soic+clip&qid=1612814963&sr=8-3
|
||||
* BS1 Serial Adapter: http://www.efx-tek.com/topics/bs1-sa.html
|
||||
|
||||
Test Leads/ESD (some moved to Craftsman toolbox for space reasons)
|
||||
|
||||
* Anti ESD Mat / Strip : https://www.ifixit.com/Store/Tools/Portable-Anti-Static-Mat/IF145-202
|
||||
* Multi meter leads http://www.extech.com/products/TL831
|
||||
* Bitscope leads: http://my.bitscope.com/store/?p=list&a=list&i=cat+probe
|
||||
|
||||
Toolbox (1,2,3) on shelving above bench
|
||||
|
||||
* Screwdriver set: https://www.altex.com/eclipse-62-piece-security-bit-set
|
||||
* Multi meter: https://www.harborfreight.com/11-function-digital-multimeter-with-audible-continuity-61593.html
|
||||
* Screw Gun: https://www.harborfreight.com/48v-14-in-cordless-screwdriver-kit-56544.html
|
||||
* Test Leads: https://www.harborfreight.com/18-inch-low-voltage-multi-colored-test-leads-66717.html
|
||||
* Non contact voltage tester: https://www.harborfreight.com/non-contact-voltage-tester-63919.html?_br_psugg_q=voltage+tester
|
||||
* Pliers set (stored to right of bench): https://www.harborfreight.com/pliers-set-with-comfort-grips-5-pc-64136.html (stored in : https://www.harborfreight.com/15-compartment-adjustable-plier-rack-56399.html) (a bit fiddly to adjust, have to sweet talk it a bit)
|
||||
* Hook/pick set: https://www.walmart.com/ip/Hyper-Tough-4-Piece-Hook-and-Pick-Set-with-Soft-Grip-Handles-9909/42350189
|
||||
* Rivet: https://www.walmart.com/ip/Hyper-Tough-9-5-inch-Rivet-Tool-with-40-Assorted-Rivets-TN12556J/812577370
|
||||
* Drill bits: https://www.homedepot.com/p/DEWALT-Black-and-Gold-Drill-Bit-Set-29-Piece-DWA1189/205952650
|
||||
* Wrenches: https://www.harborfreight.com/hand-tools/wrenches/12-piece-stubby-combination-wrench-set-97383.html
|
||||
|
||||
Shelving to right of bench
|
||||
|
||||
* Small Fridge (solder paste long term storage) : http://www.walmart.com/ip/Frigidaire-Portable-Retro-12-Can-Mini-Fridge-EFMIS462-Black/279103768
|
||||
* Personal Cooler (solder paste immediate/short term use): http://www.walmart.com/ip/Personal-Chiller-Mini-Fridge-Small-Space-Cooler-Black-K4105MTBK/641746796
|
||||
* Lab Power Supplies (couple of high volt/amp donor wall warts, and multiple RocketFish AC/DC with tips)
|
||||
|
||||
Closet storage
|
||||
|
||||
* Storage Bags: Plastic (scavenged)
|
||||
* Storage Bags: (scavenged)
|
||||
|
||||
Storage on wall/Containers
|
||||
|
||||
|
||||
* Tool drawers: (container store, tracking down product link)
|
||||
|
||||
* Shoebox Totes:
|
||||
|
||||
* Component Storage Drawers (large): https://www.lowes.com/pd/CRAFTSMAN-Bin-System-9-Compartment-Plastic-Small-Parts-Organizer/1000578349
|
||||
* Component Storage Drawers (small): https://www.lowes.com/pd/CRAFTSMAN-Bin-System-30-Compartment-Plastic-Small-Parts-Organizer/1000578345
|
||||
|
||||
|
||||
|
||||
##### Equipment Inventory
|
||||
|
||||
###### Bench top Equipment List
|
||||
|
||||
* Small circulation fan (solder fume removal): (Standard USB 5v , available from many retailers)
|
||||
* Large circulation fan (solder fume removal): (9v dc barrel jack or battery operated, I bought it at HomeDepot, cant find the product on the website now, of course I'm sure many retailers sell desktop fans)
|
||||
* Rework / solder station: http://www.aoyue3d.com/en/pro/default.asp?id=52
|
||||
* Bitscope USB oscilliscope : https://www.bitscope.com/product/BS05/
|
||||
* Lumens Document Camera (great for looking at PCB on screen and doing documentation) : https://www.mylumens.com/en/Products_detail/41/DC172
|
||||
* Multimeter: https://www.cnx-software.com/2014/10/19/50-uni-t-ut61e-digital-multimeter-supports-data-logging-to-a-windows-computer/ and https://www.uni-trend.com/meters/ (take your pick for price/features) (we have the https://www.uni-trend.com/meters/html/product/NewProducts/UT61%20161%20Series/UT61E+.html )
|
||||
* Bus Pirate (jtag and other low level bit twiddling) : https://www.sparkfun.com/products/12942
|
||||
* USB microscope: https://www.adafruit.com/product/636
|
||||
* DC Power Supply: https://usa.banggood.com/KORAD-KA3005D-0~30V-0~5A-Precision-Adjustable-DC-Power-Supply-DC-Digital-Control-with-Test-Leads-p-944574.html?cur_warehouse=CN&ID=43101&rmmds=buy
|
||||
* Desktop magnifying lamp: https://www.harborfreight.com/desktop-magnifying-lamp-60642.html
|
||||
* Windows 8 PC , running various software packages (cheese, sigrok, openocd, etc etc ) Docs on bench top computer soon. TODO document the software load out
|
||||
|
||||
|
||||
|
||||
## Target: KNEL Discourse
|
||||
|
||||
### Target: Nextcloud
|
||||
|
||||
## Target : Handbook CTO
|
||||
|
||||
### Avionics Mock up
|
||||
|
||||
TODO Pics/text
|
||||
|
||||
|
||||
### Avionics Test bed
|
||||
|
||||
TODO Pics/text
|
||||
BIN
static/EmailFolder.png
Normal file
BIN
static/EmailFolder.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 27 KiB |
Binary file not shown.
Binary file not shown.
41
static/OrgDesign20.txt
Normal file
41
static/OrgDesign20.txt
Normal file
@ -0,0 +1,41 @@
|
||||
|
||||
Organizational Update:
|
||||
|
||||
|
||||
Board Of Directors (putting board candidate book together Tuesday and will host an initial meeting very soon ) .
|
||||
|
||||
Committes:
|
||||
|
||||
|
||||
TSYS Wide C-suite:
|
||||
|
||||
|
||||
Chief Fundraising Officer
|
||||
Chief Investment Officer
|
||||
Chief Marketing Officer
|
||||
Chief Revenue Officer
|
||||
Chief Commons Officer
|
||||
Chief Technology / Product Officer
|
||||
Chief Science Officer
|
||||
Chief Research Officer
|
||||
Chief Operations/Finance Officer
|
||||
Chief Information Technolgy / Security Officer
|
||||
|
||||
The C-Suite will be equal footing and will report to the board directly (into various BoD committees).
|
||||
|
||||
No CEO. No central power broker.
|
||||
|
||||
Each C exec will have a single VP reporting to them for day-to-day decision making and overseeing the 100% computerized middle management system (Redmine).
|
||||
|
||||
The middle management system is fully public by the way: (with exception of ITAR restricted information, TS/SCI material, all things envelope as that's our trade secrets).
|
||||
|
||||
https://projects.knownelement.com/projects?query_id=8
|
||||
|
||||
All company communications will happen via Discourse (and to a certain extent via Redmine in ticket discussions)
|
||||
|
||||
https://community.knownelement.com/
|
||||
|
||||
I need to update the handbook: https://handbook.turnsys.com/ to reflect the new reality.
|
||||
|
||||
We will do everything in the open. Stakeholders of every level can participate. We are not our customer. The more that we have community interaction on a constant basis at every level
|
||||
of the organzation, the better.
|
||||
BIN
static/ReachableCEOAvatar.jpg
Normal file
BIN
static/ReachableCEOAvatar.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
106
static/ScratchNotes.txt
Normal file
106
static/ScratchNotes.txt
Normal file
@ -0,0 +1,106 @@
|
||||
|
||||
|
||||
# Charles Scratch notes
|
||||
|
||||
Land here before perm capture to Dendron
|
||||
|
||||
|
||||
|
||||
### Server room power expenses
|
||||
|
||||
|
||||
outlet 1 (compute load)
|
||||
|
||||
Uptime 30T02:15:42
|
||||
Total power consumed: 1458.674 kWh
|
||||
Curent: 8amps
|
||||
|
||||
AC load was 8 to 13 amps. I will be conservative in my estimate and say 8 amps sustained and same kwh (1458).
|
||||
|
||||
1458 *2 = 2,916 kwh
|
||||
|
||||
|
||||
Reliant per kwh cost: $0.090942/kWh , so let's call it 10c comes to 291.60
|
||||
|
||||
12 months at 291.60 is $3,499.20
|
||||
|
||||
I am going to round up to 300.00 per month for $3,600.00
|
||||
|
||||
|
||||
|
||||
```
|
||||
|
||||
|
||||
## att reverse dns
|
||||
|
||||
prov-dns@att.com
|
||||
|
||||
## brendan public key
|
||||
|
||||
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHwZmYKM1NrlX4maWvvB53SQ5QqeZLc6aAvzcgGd7WRL brendan@tsys-work
|
||||
|
||||
|
||||
|
||||
Central HVAC: Goodman GSZ130601AD
|
||||
|
||||
|
||||
This app is set up to authenticate with the Cloudron User Directory. Cloudron users can login and use it immediately.
|
||||
|
||||
This app is pre-setup with an admin account. The initial credentials are:
|
||||
|
||||
Username: admin
|
||||
Password: changeme123
|
||||
Email: admin@cloudron.local
|
||||
|
||||
Please change the admin password and email immediately.
|
||||
|
||||
Users from Cloudron have to be synced into Dolibarr manually by running sync-users.sh in a webterminal into the app, those can use Dolibarr but the pre-setup admin account has to be used to delegate rights to those users.
|
||||
Please see the Dolibarr documentation for helpful information and common topics on this app. If you need further help, refer to Cloudron's Dolibarr forum section.
|
||||
|
||||
Missing Parts List For Ballon Manufacturing Prototype
|
||||
|
||||
##########
|
||||
BOM review conducted 1/15/2022
|
||||
|
||||
########## Vaccum chamber
|
||||
|
||||
* Qty 1: Diode 1 amp
|
||||
|
||||
########## Heat Sealer
|
||||
|
||||
Check Stock and/or order/review:
|
||||
|
||||
12 2 Yageo MFR-25FBF52-100K Digikey 100KXBK-ND (100K) RES 100K OHM 1/4W 5% AXIAL $0.10 https://www.digikey.com/en/products/detail/yageo/MFR-25FBF52-100K/13473?s=N4IgTCBcDaIIwAYEGkAaAhZBaAcgERAF0BfIA
|
||||
|
||||
|
||||
15 1 Don’t buy yet ARCOL / Ohmite Mouser 284-HS15-8.0F HSC100 100W, Power resistor Wirewound Resistor - Chassis Mount 15W 8.0 OHM1%
|
||||
|
||||
Needs review:
|
||||
* 14 1 HVR2500006983FR500 Mouser 594-HVR2500006983FR5 (380K resistor) Metal Film Resistors - Through Hole 1/4watt 698Kohms 1% $0.27 https://www.mouser.com/ProductDetail/Vishay-BC-Components/HVR2500006983FR500?qs=7DG%2Fna1Fp6uaZGlKK2m6Cg%3D%3D&mgh=1&gclid=EAIaIQobChMI_7jH84n98AIVrD6tBh2qfgucEAQYAiABEgJ5svD_BwE
|
||||
|
||||
Already delivered, however may be wrong item.
|
||||
|
||||
14 https://www.digikey.com/en/products/detail/nte-electronics-inc/QW3360BR/11650180
|
||||
|
||||
# RSS Feeds
|
||||
|
||||
https://www.sevarg.net/
|
||||
|
||||
|
||||
## CEO Todo
|
||||
|
||||
https://www.aha.io/blog/vision-vs-strategy-vs-roadmap
|
||||
https://online.hbs.edu/blog/post/what-is-value-chain-analysis
|
||||
https://www.cio.com/article/3526687/an-introduction-to-wardley-value-chain-mapping.html
|
||||
https://review.firstround.com/set-non-goals-and-build-a-product-strategy-stack-lessons-for-product-leaders
|
||||
https://www.reforge.com/blog/set-better-goals-with-ncts-not-okrs
|
||||
https://apps.dtic.mil/sti/pdfs/ADA589438.pdf
|
||||
http://www.nwlink.com/~donclark/leader/LMCC.html
|
||||
https://valeriefleonard.medium.com/what-is-organizational-capacity-and-why-should-you-care-e2b90255df52
|
||||
http://www.dodccrp.org/files/IC2J_v3n2_06_Alberts.pdf
|
||||
|
||||
|
||||
Re-install to D drive
|
||||
|
||||
go
|
||||
Storyboarder
|
||||
Binary file not shown.
56
static/TheCharlesWybleShow.md
Normal file
56
static/TheCharlesWybleShow.md
Normal file
@ -0,0 +1,56 @@
|
||||
- [The Charles Wyble Show](#the-charles-wyble-show)
|
||||
- [early years](#early-years)
|
||||
- [Tenant 1 - exclusive expert](#tenant-1----exclusive-expert)
|
||||
- [the first time](#the-first-time)
|
||||
- [the second time](#the-second-time)
|
||||
- [the third time](#the-third-time)
|
||||
- [Tenant 2 - Get comforable being right](#tenant-2----get-comforable-being-right)
|
||||
- [Tenant 2 - OODA is all](#tenant-2----ooda-is-all)
|
||||
|
||||
# The Charles Wyble Show
|
||||
|
||||
## early years
|
||||
|
||||
### Tenant 1 - exclusive expert
|
||||
|
||||
#### the first time
|
||||
|
||||
become an exclusive expert at something. it's key.
|
||||
|
||||
from 14 to 18 years old i spent 10,000+ hours develping deep expertise in the micrsofot file formats. excel specfically. i am a co-author of the only comprehesive documentation outside
|
||||
micrsoft. i was the very first person to request the formats after the consent decree.
|
||||
|
||||
|
||||
9/11/2001 was the first day of my senior high school year
|
||||
|
||||
less than a year later at 17 i was recruite by the department of defense to support global counter terrorism operations.
|
||||
|
||||
why? i was the worlds expert on microsoft file formats (specifically excel).
|
||||
|
||||
yes terrorists use excel. i supported sensitive site operations (SSE) pipelines that sourced, colated, processed, exploited intelligence
|
||||
in country to support industrial scale, stovepope counter terrorism ops
|
||||
|
||||
|
||||
#### the second time
|
||||
|
||||
I .... "helped people do stuff". We will simply say "offensive cyber" , but you know before 2010. No , it's not on my linkedin. Only people who are glorified metasploit operators put "NSA Cyber Ops" on linkedin. Because that's not useufl OSINT for our enemies. I was there in the beginning and I was an early pioneer.
|
||||
|
||||
#### the third time
|
||||
|
||||
This little balloon project. It's nothing big and profesisonal like (insert co name here) #TODO , just some 30/40 somethings in a garage with a dream and a world
|
||||
class leadership/founding engineering team drawn from our mid career rolodexes and relenteless pounding of the pavement.
|
||||
|
||||
### Tenant 2 - Get comforable being right
|
||||
|
||||
9 billion in capital spend for TWDC in 52 weeks
|
||||
Thre people being my gatekeepers and nothing under 10 million in rev impact was worth my time
|
||||
|
||||
I was 25 . It was scary and exhiliarting
|
||||
|
||||
Critical path shot caller for million/billon revenue/capex make/break decisions my whole career
|
||||
Took companies public. Lots of firing.
|
||||
Make decisions quickly and own em. YOLO is real. Fime only moves forward
|
||||
|
||||
|
||||
|
||||
### Tenant 2 - OODA is all
|
||||
BIN
static/TheCharlesWybleShow.pdf
Normal file
BIN
static/TheCharlesWybleShow.pdf
Normal file
Binary file not shown.
Binary file not shown.
29
static/community-rules-notes.txt
Normal file
29
static/community-rules-notes.txt
Normal file
@ -0,0 +1,29 @@
|
||||
Welcome to the channel!
|
||||
Please agree to the rules by clicking the green checkbox.
|
||||
You can view all the channels afterward.
|
||||
Welcome aboard and glad to have you here!
|
||||
|
||||
===Rules
|
||||
Chat, share, help each other. We're all interconnected.
|
||||
Ask or report about anything to a human janitor.
|
||||
Nothing here is financial advice. Do your research and due diligence.
|
||||
No hate, racism, or prejudices tolerated. This is a kickable offense. Please report to a human janitor.
|
||||
No scammers, spammers, or bots tolerated. This is a bannable offense. Please report to a human janitor.
|
||||
Don't interact with anyone asking you for your credentials. Janitors (moderators) will never ask you for your password.
|
||||
Don't give access to your private keys, download anything, or control your computer. Janitors (moderators) will never ask you.
|
||||
Watch out for giveaway, prize, or lottery scams. The Nydus channel does not have this.
|
||||
|
||||
===Channels
|
||||
#📌welcome - become a member by agreeing to rules.
|
||||
#📌announcements - janitor messages about important happenings for the channel.
|
||||
#📌new-content - releases of new content such as youtube videos, music, or platforms.
|
||||
---
|
||||
#💬general - chat about cool stuff.
|
||||
#💬defi - chat about cryptocurrency, dapps, dexes, etc.
|
||||
#💬cefi - chat about ETFs, IRAs, 401k, banking, etc.
|
||||
#💬refi - real estate hustles, shipping containers, international real estate.
|
||||
#💬coding - chat about web development, blockchain, etc.
|
||||
#💬jukebox - MEE6 can play music if you ask it nicely.
|
||||
---
|
||||
#💬general voice - chat and share screens with friends.
|
||||
#💬jukebox voice - listen to music and hang out.
|
||||
22
static/core-pitch-prefund.txt
Normal file
22
static/core-pitch-prefund.txt
Normal file
@ -0,0 +1,22 @@
|
||||
Seeking those who want to go on a grand adventure, help build the future we need.
|
||||
|
||||
I’m Charles N Wyble, founder of The TSYS Group and CEO of RackRental.Net and Suborbital Systems Development Company.
|
||||
|
||||
Do you want to connect the unconnected? Solve the digital divide? Bring internet to everyone for 5.00 a month per subscriber?
|
||||
|
||||
Then join us!
|
||||
|
||||
To be up front: We can't currently pay you. Hence we are posting in the volunteers section.
|
||||
|
||||
We are open to offering membership in the LLC , or contracting with deferred payment contingent on funding . We are actively working on our capital raise. What we can offer you is unparalleled control/delegation of authority/responsibility in your operational area. Seeking those who wish to have an outsize impact and have the skills todo so and want to shine! Seeking those who want to build resumes, practice skills, build infrastructure, do things the right way from the beginning.
|
||||
|
||||
We are hard at work getting our key IT/business systems deployed into production, and are preparing to scale up/out.
|
||||
|
||||
Please visit our forum (which is our sole corporate information repository) at: https://community.turnsys.com/
|
||||
|
||||
And feel free to join our discord: https://discord.gg/BzbsWque
|
||||
|
||||
We are a self funded, for profit LLC. Find more at : https://www.turnsys.com .
|
||||
|
||||
Our global headquarters is located in the heart of central Texas, with directors/advisors/volunteers/LLC members all over the world .
|
||||
We strive to actively cultivate and maintain a highly diverse , skilled, engaged set of LLC members and volunteers/associates.
|
||||
BIN
static/data-ownership-uuascMarch2010.odp
Normal file
BIN
static/data-ownership-uuascMarch2010.odp
Normal file
Binary file not shown.
BIN
static/data-ownership.odp
Normal file
BIN
static/data-ownership.odp
Normal file
Binary file not shown.
BIN
static/data-security-uuasc-Jan2011.odp
Normal file
BIN
static/data-security-uuasc-Jan2011.odp
Normal file
Binary file not shown.
BIN
static/slide-HFNOC.PDF
Normal file
BIN
static/slide-HFNOC.PDF
Normal file
Binary file not shown.
BIN
static/slide-Redwood1.PDF
Normal file
BIN
static/slide-Redwood1.PDF
Normal file
Binary file not shown.
1
themes/ananke
Submodule
1
themes/ananke
Submodule
@ -0,0 +1 @@
|
||||
Subproject commit 33fbda0e9d3e97c92af5d195be94e8eea8003239
|
||||
Loading…
Reference in New Issue
Block a user