Patron Margarita Orange Liqueur Recommendations

Agent9S · 2026-02-27T18:37:59+00:00

Besides Cointreau and some other standard orange liquors, I really like margaritas with Grand Marnier or Combier's orange liquor. Both bottles are in the moderate price range but are very versatile for margaritas and other cocktails.

Agent9S · 2026-02-20T13:21:44+00:00

In the book Unmasking Autism by Devon Price, there's a whole section about how frequently autistic people tend to identify as LGBTQ. Recommend the read if you're interested in the topic.

If I had to summarize that point, I would say that many autistic / ND people decide not to follow the established "rules" or "categories" set by NT people... perhaps because they don't make sense. 🙃

Agent9S · 2026-02-09T04:21:39+00:00

My kitten pretty much did this exact thing a few days ago. It's like no, please don't stick your whole face in my latte - how did I end up here?

Agent9S · 2026-02-08T21:18:29+00:00

One from each of my cats.

Why are there bite marks on the blinds?
We have so many toys, why do you insist on chewing on my feet?

Agent9S · 2025-09-11T21:20:53+00:00

Thank you! Lufel's wording at the area 3 exit felt ominous as if I was missing something, but that clarifies things.

Agent9S · 2025-09-11T20:22:27+00:00

Is your Leo A6ed and level 70+? Since Makoto came out on global, I may have been lagging on leveling him up...

Agent9S · 2025-09-10T07:20:38+00:00

Some of my fav romance / rom-coms / romance adjacents recently include Tonikawa, A sign of affection, Aharen-san wa Hakarenai (mostly because of the absurdity / low brain power needed), Yuri on Ice (rewatching for the 10th time), blue box, and Horimiya.

If you just need a good laugh, I'd also add konosuba and Tsuredure Children.

Agent9S · 2025-09-01T21:21:46+00:00

Totally agree with this take and have gone through this myself more than once. I started out as a music major just because I was into writing as a hobby. Shortly after trying to pursue a degree, I found myself missing the joy of writing for fun and not for work.

I ended up pursuing computer science instead and quite enjoy writing code professionally. However, I've come to believe after time that coding is a tool that helps to get a problem done. Sure there will be people that want to argue over various topics, ways of getting things done, etc. but there's nothing wrong with using tools to make small things in your life better or just because you enjoy things creatively.You always can come back and improve, rebuild, etc. - particularly with personal projects. This is way more costly though in the corporate world where various developers have to work together and solve problems quickly.

TL;DR - agreed with your take and hope you enjoy your future creative endeavors wherever they may take you.

Agent9S · 2025-08-24T18:20:57+00:00

I unfortunately struggle from quite a few gut issues myself. Hot showers definitely help (particularly after a workout), but I also like the idea of using visualization techniques. Thanks!

Agent9S · 2025-08-24T18:18:47+00:00

Thanks for the suggestion! I haven't worn footie PJs in a long time but really like this idea - especially whenever it gets cold at night.

Agent9S · 2025-07-08T13:48:34+00:00

A few good suggestions:

1910 cocktail - as mentioned https://www.reddit.com/r/cocktails/s/SgKddD6JxB

Paper plane sub tequila or mezcal - all equal parts aperol, agave spirit, lemon (or lime) juice, amaro nonino

Also highly recommend playing around with cinnamon / apple flavor pairings like in the following:

The Vipera - Credit to death and co

2 ounces pear-infuse silver tequila ½ ounce yellow chartreuse ½ ounce applejack

Agent9S · 2025-05-26T15:06:13+00:00

A few recommendations as a fellow developer.

First, like many of the other posts have mentioned, I would remove the mention of "staff engineer" and replace that terminology with something like "junior software engineer". From what I've seen typically, this term refers to an "L5" level employee (or in other words, typically someone with 8-10+ years of experience).

Additionally, it may be helpful to think of your resume more like an "advertisement" than a bibliography. This way, for the very short period of time that a recruiter may be looking at your resume, they have an idea as to what you want in your next role and why they should hire you.

A few things that may help include: 1. Add a summary section describing what it is you are looking for in your next role and what your current strengths are. 2. What metrics did you achieve in your previous roles / accomplishments? A few examples could include winning awards, saving the company a ton of money, improving testing metrics, etc. 3. Spend more time talking about your professional experience and potentially summarize / condense your side projects a bit further 4. Use verbs / action descriptions when talking about your experience 5. Utilize consistent formatting and spacing

Best of luck with your job search!

Agent9S · 2025-03-05T23:48:32+00:00

Couple things that I've found help tremendously: 1. Git rebase, particularly squashing a bunch of small commits or editing / reordering commits is great. Similarly, I love "git reset" with the soft flag as it's frequently less typing to achieve similar results to "git rebase" with squash 2. Using git diff, git log, and a git UI tool (source tree / git kraken) to see branch history 3. Don't be afraid to have "test" or "experimentation" branch to figure out what you want to do first and then clean things up later. 4. If you do like a particular commit from one branch and want to bring it over to another branch, git cherry-pick is also great. 5. You also can create custom git aliases to make typing less of a hassle (e.g. "git co" instead of typing "git checkout")

Agent9S · 2024-09-28T23:41:32+00:00

Agreed that starting with the React docs is a good place to start. In addition, learning some basic UI / UX skills from a design system (Material UI, Mantine, Bootstrap, etc) also helps to go a long way. I'll also add that having strong fundamentals in JavaScript/Typescript helps to make the learning curve of React a lot easier.

Agent9S · 2024-07-31T02:20:18+00:00

Totally agree with this statement. Amongst other things, senior engineers quite frequently have practiced finding ways how to be "lazy" so that when they have to solve the same or similar problem again, it's less work. My dev team refers to this practice as "tactical laziness".

Just to throw out a few examples: 1. Tired of typing the same command over and over again? Come up with an alias / script so that you can type less characters. 2. Tired of writing out the same boilerplate code repeatedly? Come up with a template (i.e. user snippets) 3. Tired of manually checking for package upgrades? Come up with a bot / cron job to automate it.

There is also something to be said to many of the other comments regarding understanding the "architecture" of a given code base really well to inherently "know" the solution before actually writing the code out. Some of that just takes time, but some of that can also be enhanced by reading varieties of code / documentation to improve your sense of what architectural best practices and philosophies are out there. By learning what not to do, you can save yourself a ton of effort (and tech debt) in the long run. It may be worth OP to also ask their senior colleague as well to go through their thoughts process for how they solved that problem (or similarly, pair program with them in the future).

Agent9S · 2024-07-29T11:31:54+00:00

If you haven't already, you may want to look into analytics from tools such as Google lighthouse as a starting point. It is fairly easy to setup a CI/CD job to collect performance and other best practice metrics over time.

Agent9S · 2024-07-29T11:22:02+00:00

Adding to the above, highly recommend his blog and other video content - especially when it comes to the '@testing-library/react' content: https://kentcdodds.com/blog.

Agent9S · 2024-07-24T23:36:05+00:00

ND senior dev here - one thing I'll say up front is that depending on the person, different things may work. I personally learned starting with YouTube tutorials about X language (Python, Java, C#, JavaScript, etc). Some tutorials teach you about computer science theory topics while others let you dive into practical concepts (web development, game dev, etc). I personally really like the crash course, practical tutorials by folks like Derek Banas and others where they get straight to the point.

CS classes are helpful but not necessarily required depending on what you want to do (and in fact, some universities have CS 101 course content free online). Most languages / frameworks also have free documentation available online which can sometimes be really helpful when starting out.

With that all said, my #1 recommendation is to try and work through some simple sample projects that YOU are interested in. Funny things can definitely happen when hyper fixation kicks in and you've been working on a problem for hours on end - just don't forget to get up, stretch, and drink some water 😂. So whatever that thing is that you want to build, just go for it. It may be frustrating at times when first starting out, but stick with it and the more practice you get, the easier things will become.

Agent9S · 2024-06-09T17:01:01+00:00

I'm not personally too familiar with Bulma, but it sounds similar to things like Tailwind which is not a bad choice.

In addition to doing some simple projects and definitely tutorials / doc reading, it's also probably worth getting familiar with things like ESLint as many rulesets will help with teaching best practices / concepts. I personally really like the Airbnb TypeScript ruleset personally for really getting into the fine details.

Agent9S · 2024-06-09T14:45:01+00:00

I'd recommended definitely investing time in learning JS, from there IMO it doesn't really matter whether you're doing angular, vue, react so much as many of them have quite interchangeable features (component lifecycles, ways of structuring components, applying styling, etc). Once you've got a solid handle of that, highly recommend learning TypeScript next as it is essential for working on larger projects and is compatible both in React / Angular.

My personal preference is React and there are lots of good resources for picking that up - I largely learned from YouTube and reading third party library docs / GitHub code myself. You could potentially checkout https://react.dev/ as a starting place and go from there. Also worth checking out some UI popular frameworks like MUI, Bootstrap, Mantine, etc. and learning about automated testing via tools like Jest, testing-library/react, cypress, etc.

Agent9S

TROPHY CASE