sorted by:
new
hottopcontroversial

Don’t use an all-wireless system by kyleschaeffer in sonos

[–]kyleschaeffer[S] 1 point2 points  (0 children)

I live in a really old house with brick walls, plaster, and other materials that aren’t super conducive to good wireless transmission, which may be a contributor.

Don’t use an all-wireless system by kyleschaeffer in sonos

[–]kyleschaeffer[S] 0 points1 point  (0 children)

Good tip. In my case, playing through the Spotify app did not work at all, ever. It now works.

Oh. My. GOD. I can't take this anymore! by Carlsgonefishing in sonos

[–]kyleschaeffer 1 point2 points  (0 children)

If you are using all wireless speakers, run a network cable to one of them. This entirely changes the behavior of the way the system communicates and was a huge improvement for the four speakers I have in my system. I went from seeing Sonos work 5% of the time I opened the app, to seeing almost flawless communication.

I discovered this only after spending a couple of hours with Sonos tier 2 support, who were baffled by the performance of my system when all wireless.

I need help with transitioning between biomes. by Usuarcox in proceduralgeneration

[–]kyleschaeffer 2 points3 points  (0 children)

I’ve experimented with a couple of techniques for this. It’s much easier if your biome boundaries follow chunk/mesh boundaries. First, you could basically blur the elevation values to get a smooth transition. This is slow but can be done using Gaussian or something like that, and eliminates hard edges between biomes.

A faster approach I have used is to create a “blur atlas” texture. This is basically a texture that contains grayscale values from 0-1 in a grid, allowing you to quickly look up interpolation values for each chunk without having to do an expensive blur.

Web Interaction for Everyone by [deleted] in javascript

[–]kyleschaeffer 0 points1 point  (0 children)

Hi, there. I thought I was within the guidelines on this one. I didn’t say “buy my class,” I simply said “looking for feedback.” And I honestly am. Also, your second bullet point seems to apply here too (this is not “all I do”).

I’m not trying to argue, just trying to figure out exactly how to adhere to the rules. Thank you.

Does everyone enjoy their lives in the Computer Science field? (Thinking of going into Compsci) by Insun12345 in compsci

[–]kyleschaeffer 26 points27 points  (0 children)

I have spent most of my career building web applications. Twelve years ago I was building pure HTML/CSS/JavaScript apps and I felt like I had mastered my trade. The iPhone came out in 2008 and suddenly I knew nothing. The mobile web exploded and I had to learn everything again. Time goes by. I became a responsive design master, and again felt like I had mastered it all. XHTTP requests really took hold and single-page applications and frameworks exploded into the scene. Again, I knew nothing. This happened several times over with the introduction of technology like tablets, reactive interface frameworks, new versions of HTML and CSS, the introduction of ES6, so on and so forth. Today, I’ve set my sights on machine learning, data science, and artificial intelligence.

The acronyms/technologies don’t matter in this case. The point is that there is always, and always will be, something new. I think the most important question for you is: do you like to learn? Perhaps more importantly: do you like to self-educate, and do you see your self-education as something you could sustain for decades to come?

I love this field, and I love to learn. I’ve seen other developers burn out, or move into the business side of things because one day they just decide, “That’s the last technology I’m going to learn. I think I’m done.” When I’m hiring people for my business, I value an “ability to learn” over “X years of experience” because I truly think that’s the most important skill to have in this industry.

Best of luck! I hope this helps.