atla5 / blog Goto Github PK
View Code? Open in Web Editor NEWSeries of markdown entries regarding me work which I hope to include on my personal site later.
Series of markdown entries regarding me work which I hope to include on my personal site later.
tags: ["scrum", "aristotle", "philosophy", "virtue", "process", "software engineering"]
when i first began learning about scrum in school, the position of scrum master seemed superfluous, and the methodology itself appeared undirected, imprecise, and even sloppy to me. The fixation on workplace 'culture' seemed distant and almost
as i learned more about it and worked within it, however, and truly started practicing continuous integration and deployment, it has become the only way i see myself wanting to work.
--
a large part of software agility is the establishment of processes which 'bake in' testing, code quality, retrospectives (pulse checks and process improvements), planning, etc. in a way not unlike Aristotle's conception of cultivating beneficial habits of virtue in order to promote health, happiness, and character.
--
extending the <data>
tag:
src=""
)cache="10m"
)The importance of separating your cleanest possible data and its myriad export formats.
Export to formats should be done upon request and be populated by your data at that point in time. (e.g. atla5/resume). ...
Whenever possible and/or appropriate, you should store this data in json, and provide a documented API (automatically like with swagger) to it directly, so your other internal services and external consumers can permute it to their exact need.
...
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>#SoftwareEngineering is a truly incredible field. that open source/access is such an infrastructural component, that understanding and contributing to it is so simple (open by default), that source control/provenance is solved. how do we share that with other human endeavors?
— Aidan S (@Aidan_KS) November 9, 2017
Software engineering has solved, seemingly subconsciously, some of the most perplexing and ground-breaking problems in LIS, publishing, open access science, etc. partially by making (and/or realizing that) the most honorable, ethical, productive, and valuable methods the easiest, most productive, and effective paths towards affecting the change you want and creating/sharing the solutions most critical to the task at hand.
outline:
microservices brought about a sea change over the last decade in how we architect backends
we're experiencing the same pain points from monoliths on the front end that triggered the backend change
being stuck in the same repository/stack using pre-built middleware has a detrimental effect on developers ....
... and creates a disconnect between front-end and backend devs and projects, even within the same team.
conclusion:
resources:
present them with a basic maze with two points on alternate corners and no additional rules.
subtitle: JSON is love, JSON is life.
so, there's no real reason you'd pick up on this, but a large number of my projects have a significant portion of their data stored in json, and almost all of those related to my site have tags
values:
project | json files |
---|---|
resume | about, additional, education, experience, projects |
blog | hidden in (almost) every .md entry (e.g. semantic-file-system) |
FeedReader | listing of feeds in feeds.json |
lib-re/crosswalk | language encodings (e.g. dc.json) |
the thing is, i didn't entirely do this with the plan of having all of them displayed on my site (someday, lol). i just really love reusable data that is just data. i also didn't know much of anything about react, or how great it is at dealing with remote data.
in the future, a part of my site i've been planning for a while, will collect all of the tags in particular and display them all on one page within their given header (ideally even with their given components [v3.0]):
Tagged 'Library Science':
Blog Posts (from /atla5/blog/entries/)
Projects (from /resume/projects.json)
- lib-re/dublin-core-text-parser
- lib-re/lib-name-parser
- lib-re/organon
Work Experience (from resume/experience.json)
- ITHAKA - JSTOR
- Wallace Library
Courses (from /resume/education.json)
- MUSE-340: Introduction to Archives
- MUSE-359: Cultural Informatics
- ...
Feeds (from /feedreader/feeds.json)
- Lost in the Stacks
- Cataloguing Matters
- Thingology
- ...
The difficulty will come with writing some sort of aggregator in each repository to surface these tags in the cleanest way possible. Since I don't want a single repository responsible for interpreting the schemas all the others (way too complex), i'll likely have to house that in each repository.
Even with this, though, I'll end up having to watch out for any changes and potentially make edits to 4-5 repositories to get it working. I'll have to think on this more.
resume
that i had no direct use for in exporting to pdf.A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.