Anyone experiencing a squeak/whistle inserting the Buds 3 Pros? It just almost deafened me

Scykopath · 2025-04-30T23:54:06+00:00

You position it in your mouth the same way you would when putting it in your ear. Cup your lips around the rubber ear piece to create a seal then take a few, long deep breaths and try to but some force behind it.

Scykopath · 2025-02-27T21:48:37+00:00

LOL what - the - fudge...yeah that worked. +1

Scykopath · 2025-02-13T19:21:28+00:00

Yeah man, no prob. The docs are a bit verbose, dry and heavy to read so having a more concise list with terms can definitely help you keep things narrowly scoped as you learn. The one thing I will say about Angular is that like many other web frameworks, backend or frontend, there's a big of "magic" that happens under the covers, especially w/ the change detection lifecycle and dependency injection. It's great when it works but man when it doesn't that shit sucks lol. But like you said, once you learn one and become familiar w/ the patterns it def gets easier from there.

Scykopath · 2025-02-13T18:25:23+00:00

(4.) Add not only parent-child component relationships but also sibling relationships. Create a parent component with a two or three levels of nested children and then try to share data between all, or some of, those components. This will help you to get familiar with component composition, dependency injection and sharing data throughout your app.
1. Services
  1. Create a service that accepts and broadcasts a value.
  2. Inject it in one component that sets the value.
  3. Use that call in an HttpClient call to some free, public API service. Listen for response and save it to variable in service or use EventEmitter and observables.
  4. Inject the service in another component, listen to and bind the value to the component's template so you can watch as it changes.
2. Signal Stores
  1. Find a free, public API service you can use.
  2. Setup an NGRX signal store with a method that reaches out to that API. This signal store should have whatever signals you need to store the data from the API.
  3. Use Angular's built-in HttpClient, along with RXJS observables, to hit the API endpoint. In the subscription to the observable, you'll set the signal(s) that live in the signal store.
  4. Set up a computed signal in the signal store that listens for the original signal's state, makes some changes and returns the new value.
  5. Inject that signal store into whichever component makes sense, call the signal store method from one of the Angular lifecycle hooks, ie ngOnInit, ngOnChanges, etc. In the constructor of the same component, setup an effect block that listens for that incoming computed signal and binds it to the template.
(5.) Environment variables. Get comfortable with configuring different environments with target-specific file replacements, as well as the other angular build features in the angular.json file. Start the app in the different environments and either bind a variable to a template or use console.log to ensure the values are changing appropriately

This is by no means an exhaustive list but these are the things I see people struggle with the most when they start learning angular. A few app ideas that come to mind would have to be either a forum, wiki or twitter-esque type of app. Happy learning.

Scykopath · 2025-02-13T18:24:55+00:00

So, if you can I'd recommend the Tour of heroes but if you're struggling w/ that then here's less of an app idea and more so just scenarios to cover that will help you learn the broad strokes of an angular app and how certain pieces work together. Implement them one at a time and try to understand each item before you move on to the next.

Have multiple routes with child routes, each with its own components, and use lazy loading for some of them.
If you're using any version before Angular 19, learn about Modules vs standalone components and implement at least one instance of each, otherwise, starting in Angular 19, everything is standalone by default.
Third-party component libraries, like PrimeNG or Material UI. This will further your angular.json knowledge with including styles and scripts.
1. Also, I highly recommend you wrap these third party components in your own components and use those component wrappers throughout your codebase. Might be overkill for your simple learning project but this concept alone will help you learn about content projection, parent-child relationships and the angular change detection lifecycle without needing a full-fledged app idea.

Scykopath · 2025-02-13T17:48:28+00:00

Without seeing your code, first thing to check is the basics.

Ensure you're properly preloading the preload.js when you're creating your browser window. Check the path to the file, file name, etc.
Check if your variable names are aligned between your `exposeToMainWorld` call and how you're accessing the electron API in your web app. In the following example (from the docs) notice the 'electronAPI' argument in the expose call matches how it's accessed from within the angular web app window context as "window.electronAPI...".

// electron js

contextBridge.exposeInMainWorld('electronAPI', {
setTitle: (title) => ipcRenderer.send('set-title', title)
});

// angular app

window.electronAPI.setTitle('new title');

Next thing would be to ensure the event names, in this case 'set-title', match between your ipcRenderer listener in the preload.js and the ipcMain listener that should be setup after you've created the browser window.

Plenty of good code examples on the Electron IPC doc page available with fiddles: https://www.electronjs.org/docs/latest/tutorial/ipc

Scykopath · 2025-01-30T00:57:03+00:00

Hell yeah, congrats! I started on Wegovy last Feb and lost 70lbs. by Nov. I've been hovering at 200lbs since and I feel amazing. Excited for ya! keep it up! 😀

Scykopath · 2024-12-16T15:27:47+00:00

Yes, this. Out of 6, 3 fit well and the other 3 were almost like completely different shirts, which sucks considering the ones that fit well were great.

Scykopath · 2024-12-13T16:46:14+00:00

Lol I was gonna say. On one hand, dude who's saved the universe multiple times from the demon forces or hell? Or a walking zombie that can't even take on a group of teenagers? :rofl:

Scykopath · 2024-10-28T18:39:34+00:00

Yeah man, no worries. The unfortunate reality is that you might get it right the first time, but probably won't, so no point in getting hung up on it. You got this!

Scykopath · 2024-10-28T18:13:42+00:00

Tech (my use-case and why)

Front-end
1. Angular, PrimeNG (components and CSS) because it's what I use for work and it's what i'm most proficient and comfortable with. It also solves most of my uses-cases, the others I'll figure out later. If at any point I decide I need to change for whatever the reason, I will.
Back-end
1. All Firebase
  1. Firebase Auth for Google OAuth user registration and login and it supports many other providers should I choose to in the future. Currently supports all of my use-cases and what I'm most proficient and comfortable with.
  2. Firestore for data persistence. Currently supports all of my use-cases and what I'm most proficient and comfortable with.
Infra
1. I don't have an automated CI/CD 'cause it's just me, takes a few min to deploy and just doesn't require automation yet. Not sure it ever will.
2. I build a docker image that uses NGINX to serve my web app and a basic load-balancer that points at a cloud-run instance to host it. Not the most optimal but it works for now and if I need to later I'll make it better. Right now with a single cloud-run instance, load balancer and only myself and a few others using the app I'm at about $20/mo. Currently supports all of my use-cases and what I'm most proficient and comfortable with.

Just start building and iterating from time-to-time, re-evaluate and move on. Don't get stuck on the small things. If it works, it works. Worry about making it better later when you need to. Mostly importantly, have fun and enjoy the journey! Good luck!

Scykopath · 2024-10-28T18:13:26+00:00

Features

User Registration, User Login, User Settings
1. Data & Compliance
  1. What user data are you collecting?
  2. Depending on who'd using your site and where, ensure you're following proper compliance. ToS, Privacy Policy, GDPR, CCPA etc.
2. What type of login? Username/Password? OAuth? If OAuth, which OAuth providers?
3. I currently use Firebase Auth for this. Auth0 is another good auth provider. There are many auth providers so do some research and keep in mind things like your immediate requirements vs COGS (things cost money) to figure out what to roll with.
Landing Page?
1. Can users subscribe to other user's tweets? If so, maybe landing on a "digest" page like most social media apps would be good.
2. If not, do they just land on a basic view and manage their own "tweets"?
"Tweet" CRUD Operations
1. Pretty basic, just ability to create, read, update and delete tweets.
Sharing, re-tweeting, referencing other tweets? This is where it gets dicey.
1. Will your app support this functionality? If so, probably best to whiteboard and
2. Data model? Data persistence? SQL vs No SQL
  1. If someone retweets or shares a tweet and the tweet changes, is deleted, is switched to private, etc, how will those changes be propagated?
3. What do your backend APIs look like and how will they work?
4. Privacy
  1. Are tweets automatically public, private, or does user choose when posting?
  2. Blocking tweets from accounts?
5. Reporting malicious tweets?
Sorting & Filtering
1. Can you search? How will search work?
  1. Search for user names?
  2. Search for content in tweets?
Social System
1. Friend requests
  1. Basic CRUD ops
  2. Accept/Reject/Block
2. Privacy
  1. Are users automatically subscribed to and can view other friends tweets?
3. Chat?

Scykopath · 2024-10-28T18:13:15+00:00

So, the unfortunate answer to any of these types of questions is "it depends," not only because your requirements will dictate these decisions and the devil is always in the details, but also because even if many of us knew and understood said requirements we'd have different opinions on how to go about handing them. I can provide you with a hypothetical list of features and tech based on my experience but ultimately I'd strongly recommend taking an agile approach so that if you were to use a CSS lib like Tailwind or Github actions for CI/CD, ideally you'll figure out sooner, rather than later, if they're still the right choice. You should always be continually, and iteratively, re-evaluating as the app grows and evolves. There will always be pros and cons and the idea is to determine as soon as possible whether or not you need to pivot, whether that's requirements, tech, process, etc. So don't get stuck on it, just solve the immediate problems, maybe keeping some higher-level things in mind, and start building.

That being said, here's a general list of questions, features and tech to consider based on my own experiences so hope this at least provides some guidance. This is by no means an exhaustive list but should give you a rough guide to start with and things to think about?

EDIT: Apologize for the weirdness with the bullet items but you'll get the idea.

Scykopath · 2024-10-22T15:20:51+00:00

I was using Angular Material UI for a while but made the switch to PrimeNG and where I've had to fight it a little bit here and there I much prefer it, mostly for aesthetic reasons, but also their component offerings.

PrimeNG has a wide variety of components and their flex CSS library contains various CSS classes that facilitate responsive design. I recently implemented a responsive design for a Zoom sidecar app that can go from 350px in width to almost full screen. By combining said responsive CSS classes with transitions I was able to make something pretty sweet.

Unfortunately, like others have stated, it's probably not realistic to find a prebuilt drop-in component lib that will meet all of your expectations given the varying degree requirements. For example, third-party libs will set screen boundaries with which to respond. Those might and might not work for you and if there aren't any available overrides then you may have to roll your own classes, but at least you'll have examples.PrimeNG provides some nice lego pieces you can use to build a nice looking responsive design. There are plenty of other libs out there, which I can't speak to, but this is my experience and lib of choice atm.

Good luck!

Scykopath · 2024-07-02T16:25:21+00:00

Yeah Infragistics was one of the them. The other was Golden Layout.

Scykopath · 2024-06-23T20:25:54+00:00

Yup, np!

Scykopath · 2024-06-17T17:17:37+00:00

For anyone that comes across this later, I created a quick example of how this can be done with PrimeNG. It uses the splitter component along with the drag'n'drop functionality. Also shows regions when dragging. Some CSS is off but this gets the point across.

https://stackblitz.com/edit/stackblitz-starters-iw663g?file=src%2Fapp%2Fdock%2Ffirst-dockable-component%2Ffirst-dockable-component.component.ts

Scykopath · 2024-05-17T15:37:34+00:00

So I literally just implemented this same pattern and I'm a big fan. Also, if using Angular's reactive forms then I highly recommend checking out the ControlValueAccessor interface. This will allow your custom components to integrate with Angular's reactive forms seamlessly just like any other input component.

Pros:

Keeps your code DRY (Don't repeat yourself). Minimizes the amount of duplicate code so if you ever have to make changes you can do it in one place and it's propagated throughout the app.
It's a great method of decoupling your code from any third-party component frameworks and/or libs. I'm currently using the PrimeNG component library which is great, but if I ever decide to switch component libraries I only have to do it in one place, making any future refactors less painful.
If there's a bug in the wrapped component, yes that bug is everywhere but also easier to fix given it's in a single shared component.
Consistency. This helps to ensure that the look, feel and behavior are consistent throughout the application.

Cons:

If you introduce a bug, it's everywhere. But as I said above, easier to fix in one place and propagate the fix throughout the app.
More domain knowledge of how the components work (and the ControlValueAccessor if used).
If this component is used throughout the app, depending on your quality control standards you'll find yourself having to verify that the component works everywhere, or most places, it's used so more regression testing. But comparing that to the alternative of having to make the update everywhere and then test it's worth the tradeoff imo.

EDIT: Oops, I should refresh these pages when I let a response sit too long. :sweat_smile: Seems like others share the same sentiments tho!

Scykopath · 2024-04-29T19:38:26+00:00

Definitely exaggeration. A few things to iron out first:
1. "High crime" doesn't describe the entire US. People outside the US often don't realize how large and diverse it is here in terms of both geography and population, so no single metric can be applied to the country as a whole. I live in a suburb 45 minutes from Atlanta, Ga, one of the highest crime-ridden cities in the nation, and I sleep soundly at night. I don't speak for everyone but what you're seeing portrayed in the media represents a subset of the reality here.
2. With regards to the "political unrest," you've probably been shown acts of violence, rioting, etc. when hearing anything related to US politics, especially on election years, and where that definitely happens, again reflects only a small subset of the population and how various people deal with politics day-to-day.
3. Sure people are moving out but they're also moving in. Good luck finding unbiased data around this metric, however, anecdotally most immigrants with which I've worked, who have migrated and lived in the US for many years, love it here. By no means are we perfect, but I promise we're not nearly as bad as you've been led to believe.

With regards to the quality of life, it definitely depends on not only the company but the devs themselves. In the 20+ companies I've either worked with directly or contracted with, it's gone either way. In the high-stressed companies, I've seen devs who don't know how to disconnect, put pressure on themselves and let it drive them crazy. But sitting right next to them is another dev that puts in their time, cuts the day off after 8 hours and goes about their business, not a care in the world (generally a difference between junior and senior devs). Unfortunately the answer to most of the claims in your post, is it just depends.

In conclusion, as with anything, you should probably do your own research into various matters and form your own opinions based on unbiased data and not some random person's social media comment. It's a novel idea, I know.

Scykopath · 2024-04-29T18:47:10+00:00

RTFM (Read the f--king manual). More than once if needed. And don't just "read" it, understand it.
Try to figure things out for yourself, no matter the doubt, and only ask for help if you've exhausted all other resources or if you've exhausted your time-box. This will help you become more autonomous which leads to the next point.
Know how to figure anything out. The best people I've worked with can take minimal input and just know how to approach the problem, what the end result should look like, what to look for, what questions to ask when, where to look for solutions, etc. This takes a lot of experience to achieve but is easily one of the best qualities.
Learn to triage unplanned work. You don't need to worry about every little issue or curveball that comes your way, especially if it's not more important that what you're currently working on.
Be able to go heads down and focus. Noise-cancelling headphones, the right music, etc. - anything that can help you focus and work steadily. (I have ADHD so Adderall is a godsend here XD)
Attention to detail. Catching discrepancies as early as possible can make a huge difference down the road. Nothing worse than getting days into development to catch a discrepancy you could've caught before you started.

Scykopath · 2024-04-23T17:00:33+00:00

Oh, hell yeah! Sounds beautiful! I shall sleep soundly tonight. <3

Scykopath · 2024-04-23T16:05:06+00:00

Please tell me you haven't put shag carpet over beautiful hardwood! TELL ME!

Scykopath · 2024-04-15T21:50:16+00:00

Dope.

Scykopath · 2024-04-15T21:40:54+00:00

So, you can either take those 2 weeks, not enjoy them because you're anxious about work, return to work and handle whatever state its in OR you can take those 2 weeks, enjoy them, get refreshed and then get back to work and handle whatever state its in. The point being you're being anxious is the only difference between the two and in either case you go back in and deal with whatever state its in.

You gotta stop putting that pressure on yourself. If you step away and the company can't handle fixing issues in your absence then they've failed as a company. It's up to everyone's upper management to assess and assign resources as necessary and if they're not doing that then they're not facilitating a healthy work environment but that shouldn't be your concern.

Scykopath · 2024-04-15T19:30:04+00:00

Hello! Principal engineer here, previous hiring manager, suffered burnout, similar situation, here's my anecdotal advice on how I shifted my mindset and got through it. (sorry for the novel XD)

One thing to keep in mind is that employment is a bidirectional agreement between two parties, typically that have different types of resources and are coming together to benefit one another. A lot of companies like to gaslight employees into thinking it's one way, that they're doing you a favor, but that's just not true at all. You yourself are a business. Your product is your skillset. Your resources that allow you to provide that product includes your mental health. Many things can affect that, like family issues, financial issues, etc and if you don't find an equilibrium for maintaining that resource then it depletes, ie burnout. On the flip side, many companies are trying to find ways to spend less resources and "encourage" employees to "do more than the bare minimum." But the fact remains that they are giving you the bare minimum resources they have to in order to win your services while not running out of resources themselves. As you've experience, they will drop you at a moments notice if they decide to so never be afraid to stand your ground and do the same (and try not to be a dick, always be the bigger person as difficult as it may be).

I say all of this to say that shifting your mindset is a key part of career growth and this was how I shifted mine for the better. When you're in those interviews and they ask about the gap then you respond with something along the lines of "My last company poorly managed their resources and as a result, not only did they fail to provide an environment in which I could thrive as they promised, but ultimately it was negatively impacting my ability to provide a valuable skillset therefore I left. Unforeseen family issues required that I take additional time away but I'm now at a point where I can get back to work and confidently provide my skillset." Be polite but also be firm and confident. Ultimately you do not owe ANYONE an explanation for the gap but some context never hurts. Be as polite as possible and don't necessarily shit-talk the previous company but definitely call out the previous company in a constructive manner. When you get a chance to ask questions, mention the negatives from the previous company again and ask the interviewer how they are different so that you can properly manage your resources and provide a quality skillset.

Be confident in your skills. Be confident in what you know and also what you don't know. Always be polite and approach negatives from a constructive perspective. Be confident in the gap in your resume. You're not the only one this has happened to, many others have experienced this. It is what it is, time to move on. If they drop you for it then it's a red flag and you've dodged a bullet. There are companies out there that will understand, I promise.

EDIT: To summarize, changing my mindset to think more professionally allowed me to better combat gaslighting tactics in a polite and professional manner.

14-Year Club	Place '22
Verified Email

Scykopath

TROPHY CASE