- May 2023
-
www.waubonsee.edu www.waubonsee.edu
-
Payment Information Centrality Revision Project "Ways to fund your education" (or similar) instead of "Minimize Financial Barriers". "Verified Sources" as a phrase is problematic for users. Desire is to provide assurance to users that there are individualized options yet still have those options located in a more streamlined, centrally located way.
These are the other pages that have similar content: https://www.waubonsee.edu/admissions/costs-and-payments/paying-tuition
https://www.waubonsee.edu/admissions/costs-and-payments/paying-tuition/payments-verified-sources
https://www.waubonsee.edu/admissions/costs-and-payments/paying-tuition/making-payments
https://www.waubonsee.edu/admissions/costs-and-payments/paying-tuition/payment-plans
https://www.waubonsee.edu/admissions/costs-and-payments/paying-tuition/tuition-refunds
https://www.waubonsee.edu/admissions/costs-and-payments/paying-tuition/tax-credits-education
-
- Feb 2022
-
Local file Local file
-
Only after aligning every single part of the delivery chain, frompackaging to delivery, from the design of the ships to the design ofthe harbours, was the full potential of the container unleashed.
Streamlining one's entire workflow from start to finish can unleash tremendous amounts of additional system-wide productivity. Starting out by tinkering with small things here and there is more likely to doom these smaller individual changes to failure with out associated global changes.
Once the overall system has been redesigned and reconfigured, then one can make and perfect smaller scale local changes.
Link this to the idea of kelp and sailing/rowing from The West Wing.
-
- Feb 2021
-
github.com github.com
-
While Trailblazer offers you abstraction layers for all aspects of Ruby On Rails, it does not missionize you. Wherever you want, you may fall back to the "Rails Way" with fat models, monolithic controllers, global helpers, etc. This is not a bad thing, but allows you to step-wise introduce Trailblazer's encapsulation in your app without having to rewrite it.
Tags
- leaving the details of implementation/integration up to you
- freedom of user to override specific decision of an authority/vendor (software)
- Trailblazer
- allowing developer/user to pick and choose which pieces to use (allowing use with competing libraries; not being too opinionated; not forcing recommended way on you)
- making changes / switching/migrating gradually/incrementally/step-wise/iteratively
- focus on concepts/design/structure instead of specific/concrete technology/implementation
- rails: the Rails way
- focus on what it should do, not on how it should do it (implementation details; software design)
- newer/better ways of doing things
- abstractions
Annotators
URL
-