> Or, the feeling of wanting to do high quality work wherever you are?
We have a word that literally translates as "professional pride." Now I'm not sure it has the right vibe in English, but it captures the idea that you do high quality work and you wouldn't do a sloppy job, even if the job sucks.
For example, I would like such a plumber, because I know they will be careful not to make a mess, and they will clean up after them, and they are careful and will double check their work to make sure it's fully done and solid and not going to leak.
I don't expect them to be passionate about working with clogged pipes full of literal shit. I'm OK with them not wanting to spend 16 hours a day doing plumbing; if they only do three days a week but perform a respectful job, that is perfectly fine. In fact I'd be a little concerned if they said they're passionate about plumbing..
> What do you all call the feeling around enjoying the work
Enjoying the work. That's it.
To me, passion is something much deeper and even intimate. If you devote your life to something and you'd do it even when it doesn't pay the bills, I could accept it as passion. Otherwise, it's just a job that you enjoy.
For soft contacts there's two primary types in use. Regular hydrogels and silicone hydrogels (SiHy's). Most doctors will prescribe SiHy's now as they provide some key benefits. Those being: better air permeability (dk/t number) and the ability to be used for continous wear (overnight).
The SiHy's had a bit of a tradeoff though, despite being able to let a lot more oxygen through (which the corneas need, they can directly absorb it), they are not inherently wettable. Silicone is hydrophobic, it naturally repels water. So 3 generations of silicone hydrogel are in use. 1st gen has an external wetting agent that rubs off over time. 2nd gen has an internal wetting agent that some people are allergic to. 3rd gen has the molecular structure arranged in such a way they are inherently wettable.
I wear 3rd gen SiHy's now. Cooper Biofinity is the name brand. These are approved for extended wear up to a week. I have done longer than this but risk of complications increase. However, these were a huge improvement over the regular hydrogels I used to wear. If I had them in over 17 hours or so my pupils began to dilate from my eyes being oxygen starved. They are a little stiffer (and hence, slightly less comfortable than my regular hydrogels were). They also have a slightly higher chance of feeling dry due to higher water content than most other SiHy lines.
Anyways, hope that helps. There's a lot of options on the market and for you it might be better to look for a higher water content with lower stiffness, if you need to wear them when sleeping that really limits you to 4 or 5 continuous wear brands. Don't wear a non-approved regularly for sleep, it'll screw up your eyes in a mess of different ways (vascularization and such).
The referenced idea of a 'human log' is great[0]. I started doing something similar 4 years ago and it eventually evolved from per-project notes into a full diary. Being able to search for 'August 24 2016' and know exactly what I did that day is quite powerful.
I encourage anyone to take 10 minutes(or 30...) at the end of the day to write up what they've done. Just a text file with minimal formatting has scaled to 2.6MB of hand-typed text. Though, after a bit, I've tended to shard out specific long-running topics into their own files.
I came to comment on the same thing, only that it reminded me of an old browser-based game called Archmage [1] which would allow players, with enough resources, to research and cast Armageddon to end the world and cause a full reset of the game.
"The Art of Electronics", by Horowitz and Hill, is a respected textbook for this. The ARRL Handbook has many explained schematics for radio.
For modern commercial products, mostly you'll have some big special purpose ICs plus some minor components for power and noise management. The schematic won't tell you much because all the action is inside the ICs.
Here's something of mine you can look at, a design on Github made with KiCAD.[1] The schematic is here.[2] All the files to make a board are there, and both I and others have had working boards fabbed from those files.
The application is unusual - it's an interface for antique Teletype machines that need signals of 60mA at 120V. There are no off the shelf ICs for that. So there's a custom switching power supply to make that voltage from a 5V USB port. The README file for the project explains how it all works. It has all the extra parts you need in the real world to handle USB hot-plugging, keep the switcher noise out of the USB connection, keep RF noise down, and protect the circuit against a shorted output or a big inductive kick-back from the load.
The data sheet for the LT3750, the controller for the switching power supply, is essential when reading the schematic.[3]
You can download KiCAD and play with the files. You can also download LTSpice and run a simulation; the files for that are in the repository.
This is complex enough to be non-trivial, yet simple enough to be understandable.
Infrastructure developers and web developers are worlds apart. We're all branded "programmers", but we couldn't know less about each other.
Moving from big data centers in Texas to small startups in San Francisco was, plainly, culture shock. Seeing Kube documentation not work in mobile, if anything, makes more sense than the alternative.
We're still in the stone ages. I can tune you one hell of a MySQL installation, but I would almost certainly also mess up making a page mobile-friendly. Half the people critiquing K8s right now don't know what OpenStack is, and half the people leading successful software startups aren't comfortable with sh. It's all madness, and on the other hand - is K8s documentation on mobile actually important?
Forgive the tangent. What knowledge is and isn't applicable, and when, is endlessly fascinating to me.
I'm not blind but here's an (unsolicited) project idea for you.
To be candid, I have no idea what it feels like to be blind and have never paid much attention to accessibility other than reading a tutorial or two and making sure I use alt tags on my images. The main reason for that is that I'm lazy and based on my experience, most developers are in the same boat.
Now, if there was a service which would spin up a remote VM session inside my browser (a bit like BrowserStack or SauceLabs do) with all screen reader software setup and no screen (only audio), it'd make it a lot easier for me to experience my software as a blind user. There should probably also be a walkthrough to help new users use the screen reader and help them get started. If you're lucky, you could turn this into a business and it could indirectly help you achieve your goal of making better software for the blind by exposing more of us to your issues.
Anyways, I know you probably have more pressing issues to solve and I hope I didn't come across as arrogant, just throwing the idea out there.
Re-reading this made me notice the overlap between the two posts. Most of the suggestions across both posts fall into a few common themes. I find having a shorter list of "keys to success" helps me keep them top of mind day to day. I see four main themes here across both posts:
1. Be internally driven. Gain energy by working on things you are excited about. Think independently. Don't get pushed around. Don't default to doing the same thing everyone else is doing. Don't chase status. Have almost too much self belief. You can only motivate yourself to work hard and sell your ideas to others if you genuinely believe in them and your motivation is internally driven.
2. Have clear goals. Have bold goals. Make them achievable by breaking them down by day, by week, by decade. Take advantage of compounding to make small daily accomplishments snowball to reach bold long term ambitions. Compounding works not just for financial wealth, but also for building knowledge, developing skills, relationship, and health. Taking new risks constantly will help you learn new things faster and speed up compounding in all domains. Try to create enough buffer to be able to take risks and experiment in all areas of your life.
3. Be focused and don't waste time on things that don't matter. Minimize cognitive load. Minimize personal burn rate. Being focused does not mean sacrificing exercise, eating well, and sleeping. Most people would gain by spending more time thinking about which critical priorities to focus on. Start by killing the most obvious bad uses of time like TV and twitter.
3. Work hard. Whether your goals are in business, family, fitness, or altruism, working hard at something that naturally excites you is not only easier than working half-heartedly on things you hate, but is also the only way to achieve your goals. Working hard goes beyond putting in hours - it also means being willful, pushing through rejection, being persistent to bend the world to your will. Being a doer not a talker is just the first step.
4. Surround yourself with smart ambitious people who may join your team, teach you something, energize you and give you ideas. Invest in relationships by putting others first: be quick to do favors, don't judge too quickly, be forgiving, do not burn bridges, pause to think before acting especially if you're angry, be nice to everyone including strangers.
I migrated all of my services to k8s in the last ~6 months. The biggest hurdle was the development environment (testing and deployment pipelines). I ended up with a homebrewn strategy which happens to work really well.
# Local development / testing
I use "minikube" for developing and testing each service locally. I use a micro service architecture in which each service can be tested in isolation. If all tests pass, I create a Helm Chart with a new version for the service and push it to a private Helm Repo. This allows for fast dev/test cycles.
These are the tasks that I run from a "build" script:
* install: Install the service in your minikube cluster
* delete: Delete the service from your minikube cluster
* build: Build all artifacts, docker images, helm charts, etc.
* test: Restart pods in minikube cluster and run tests.
This fits in a 200 LOC Python script. The script relies on a library though, which contains most of the code that does the heavy lifting. I use that lib for for all micro-services which I deploy to k8s.
# Testing in a dev cluster
If local testing succeeds, I proceed testing the service in a dev cluster. The dev cluster is a (temporary) clone of the production cluster, running services with a domain-prefix (e.g. dev123.foo.com, dev-peter.foo.com). You can clone data from the production cluster via volume snapshots if you need. If you have multiple people in your org, each person could spawn their own dev clusters e.g. dev-peter.foo.com, dev-sarah.foo.com.
I install the new version of the micro-service in the dev-cluster via `helm install` and start testing.
These are the steps that need automation for cloning the prod cluster:
* Register nodes and spawn clean k8s cluster.
* Create prefixed subdomains and link them to the k8s master.
* Create new storage volumes or clone those from the production cluster or somewhere else.
* Update the domains and the volume IDs and run all cluster configs.
I haven't automated all of these steps, since I don't need to spawn new dev clusters too often. It takes about 20 minutes to clone an entire cluster, including 10 minutes of waiting for the nodes to come up. I'm going to automate most of this soon.
# Deploy in prod cluster
If the above tests pass I run `helm upgrade` for the service in the production cluster.
There's a few things to note about myself though. I couldn't do a girly pushup in college. My beginner gains ended up on what most people's beginner gains start at. I can do a full pullup and dip now, but I couldn't previously in the last year. So my gains aren't really all that crazy impressive but I've been noticing a lot of incremental gains in the last few months.I still have issues controlling my dietary plans though.
I use reddit's recommended routine bodyweight fitness as a starting point. https://www.reddit.com/r/bodyweightfitness/wiki/kb/recommend.... ... I've done 5x5, 5/3/1, I used to follow it rigorously, but I find either it was too tiring to enjoy or just too hard to remember what exercise to do on what day.
This is what I use, I keep stuff simple. I use PPL (push pull legs) on a 3 day rotation.
- 1 day is legs / abs / form workouts (LEGS)
- 1 day is upperback / biceps (PULL)
- 1 day is chest, triceps, shoulders (PUSH)
I completely ignore working out on certain days like Monday for LEGS, Tuesday for PULL, etc. Because my schedule is kind of really varied, I just make sure I finish a full PPL before going onto the next PPL
For instance, if I do PUSH, I'll make sure I do PULL and LEGS on the following days. It could be over the next 2 days or next 5 days, depending on my schedule. Then I repeat back to PUSH.
I try to workout at least once every 3 days though
I aim for every workout to be 40 minutes long. This is from the start of warmup to the end with post foam roller massages. I usually hit this consistently.
I aim to do a grand total of 9 sets total max per workout day.
The first part of my routine is usually popping open anime / youtube / TV show. I usually prefer these videos to be 20 minutes long ,because that's roughly how long all 9 sets of rest periods total up too. This way I can be entertained while working out. Its a way to reward myself for putting hard work
The other alternative is to fire up rocketleague.
I have these habits intentionally because it baselines my psyche & adrenaline level when I go workout, so I have more consistent results
First 5 minutes I'll do some light jogging on my treadmill desk. Usually, 2.6 mph is what I find to be enjoyable
After that, I will start doing 3 light warmup sets with 1min30sec breaks inbetween
- PUSH -> On push day, I will just do standing pushup on my standing desk. Wide grip, diamond grip, and then shoulder presses with 3 lb dumbbells to practice deep forms.
- PULL -> On pull day, I will just take a rope, loop it around my adjustable bench. I will do standing rows, and then assisted pullups with my legs
- LEGS -> On leg day, I will do pike walks and L-sets as my warmups
## PUSH DAY
On the workout itself, my pushday is 9 sets total. It looks like this:
I don't use fancy apps. I am really lazy. I find that since I workout frequently enough, I'll know what where I'm at in terms of progress generally, because I'll have logged how much weight I used in previous workouts. Usually I won't change weights until at least 2 PPL cycles anyhow
I use a moleskin journal. Each page is divided up as follows
I use a journal mostly to just keep track of which workout I need to do. So I don't accidentally skip out on any specific exercise
I don't bother doing data analytics or use fancy spreadsheets. Just too lazy, it adds 0 value in the long run anyhow.
Really I should just be taking more video shots from early progression stages but I haven't which is a bummer. But I've been taking regular selfies though for progression updates
## PROTEIN
I use vanilla whey isolate + 50% soymilk original flavor + 50% water. It actually tastes pretty good and has low carbs / high protein, with fairly balanced nutritional content. Doesn't cost that much either
This is kind of like my soylent in the morning for breakfast as well
I'm on a cut-phase right now, I usually drink a lot more water to reduce my apetite.
When I bulk I take creatine and have to creatine load myself for a few days.
## OTHER / REASONING
I can't find the source, but there was an article on reddit detailing which fitness instructors were considered the most authoritative. Based on science and experience in shaping other's people's fitness goals. The gist I got off of it is that stretching is wasted oppurtunity cost and that doing light sets based on what muscle group you will work out is much better, as a warmup. Since you work on better form too.
I chose only to do 9sets at most per day because I think having anything over that adds too much friction to workout everyday.
I did not do any fullbody workout routines like https://www.reddit.com/r/bodyweightfitness/wiki/kb/recommend... verbatim, because that's too tiring for me. 3 full body workouts in a week will leave you really sluggish and tired all the time. Its good for starting off, but when you plateau its better off doing other routines later. I usually found following those routines that stated it was 40-60 minutes long, to be actually 1hr30min long on average. Some days I couldn't hit it consistently due to my busy schedule or lack of sleep, so it was really hard to upkeep.
I think the design your future actions is a big part of this.
I've had some success with framing two modes, Architect Mode and Implementation Mode.
Architect Mode is when you sit down and make a plan to achieve a long term challenging goal (losing a lot of weight, getting in shape, learning something new, etc.). It's where you set up a routine and plan for what you're specifically going to do each day in order to do this. Being able to separate this plan from when you're actually enacting it is important because it removes the choice and doesn't allow comparisons of an immediate reward with an abstract distant reward.
Implementation Mode has to follow what was set up by the architect and is not allowed to make decisions - this is because you're compromised and unreliable when comparing an immediate reward (do I eat that slice of cheesecake?) to a long term abstract reward and it's very easy to rationalize why what you want to do is actually okay (it's only an extra 400 calories anyway - today can be a cheat day etc.).
A big part of succeeding with implementation is stacking success (doing the thing every day without missing any day) and picking a small enough starting point. Another is not putting yourself in positions where you're easily tempted to fail (don't buy oreos and have them in the house). Once you get more in the rhythm of things you are safer in more difficult environments.
When Implementation mode fails it means the architect needs to reevaluate why and make changes - it doesn't help to ruminate or beat yourself up about the failure.
Even with this mindset things are difficult, but I've found it to be the most successful for long term goals when they're clearly defined - most of it is getting the psychology right - then the behavior can follow.
Lithuanians call tea as "arbata", and it's boiled in "arbatinis". It also has nothing to do with "herbs". AFAIK, there is no reference to the word tea or cha anywhere in terms of tea.
We have a word that literally translates as "professional pride." Now I'm not sure it has the right vibe in English, but it captures the idea that you do high quality work and you wouldn't do a sloppy job, even if the job sucks.
For example, I would like such a plumber, because I know they will be careful not to make a mess, and they will clean up after them, and they are careful and will double check their work to make sure it's fully done and solid and not going to leak.
I don't expect them to be passionate about working with clogged pipes full of literal shit. I'm OK with them not wanting to spend 16 hours a day doing plumbing; if they only do three days a week but perform a respectful job, that is perfectly fine. In fact I'd be a little concerned if they said they're passionate about plumbing..
> What do you all call the feeling around enjoying the work
Enjoying the work. That's it.
To me, passion is something much deeper and even intimate. If you devote your life to something and you'd do it even when it doesn't pay the bills, I could accept it as passion. Otherwise, it's just a job that you enjoy.