done at last. the f*king read_body didn't work as in the video. I had to pass in a stringvar to it. the block form didn't work. It read parts of a json string that didn't parse well. Anyway.. on to the next video. Also, this was great. seeing u stumble, but not give up.. makes this job tolerable.
Um it doesn't matter what your gender/race is...if you want to make a podcast then make one...We're all just human bro, why do you have to do this cringe shit lol
Pretty well! The biggest barrier was that the amount of context tokens needed for a large number of rows was far more than GPT-4 could handle. This week's announcements of GPT-4 Turbo, however, have me thinking this could work a lot better with the latest improvements (JSON mode, 160K context, etc)
In case the forest looks familiar, it was the inspiration for the lead artist of Studio Ghibli's epic Princess Mononoke en.wikipedia.org/wiki/Princess_Mononoke
Another really enjoyable and informative episode Justin. I brought Tailwind to my team about 6 months back and got a LOT of push back from our CTO who literally said “I know I’m going to hate this” with all the usual complaints about verbosity and “this is just CSS inline styles” . But alas, a few months later he started to get it and now we use it across all our projects. It was also me who brought BEM (block element modifier) CSS to the team a few years earlier but that just never really stuck the way Tailwind has now stuck. I’m all for separation of coding and styling but to me, the styling is so closely coupled to the document (HTML) that it makes sense for it to live there. If we were writing a letter, would we want a separate file for the text and a separate file for the styling? No, of course not. On the soft-skills side, I love that you express the vulnerability you clearly feel while putting yourself out into the world. Please know that there are many of us who know that feeling and appreciate the efforts you are going to. You are really good at this so please keep the content coming! I kinda want our product/project managers to watch some of your videos because I think it would be very informative to observe the process of software creativity as it unfolds. Hopefully it won’t freak them out that we’re all drinking whiskey while we’re coding! 😂 どうもありがとう. 🙇♂
so intro'd speed up fell back into walks down the rabbit holes. i still prefer it that way. again, one can always jump ahead - or stay and learn from the tidbits. but if they wouldn't be there, it would just be "another tutorial". moving on to 4...
this is just the right speed. remember that you probably won't do a lot of these kind of series, so rather keep the slower pace. viewers could always fast forward, but you can't add content that's not there...
i'll be that guy, but you can use the tailwind language server in vim/neovim. just as good of an experience. but, took a while for them to extract it out of the vscode extension for use in other editors.
I appreciate this! I tried my damndest (back in ~August 2022) to get this to work, and it led me from being told I had to give up vim in favor of neovim to trying to adopt neovim and running into a bunch of other hurdles (where the tl;dr from the community was basically "prepare to maintain your own configs for a lot of stuff") I get that progress has probably been made since then and I should've acknowledged it, but boy it left a bad taste in my mouth. Enough to adopt an Electron app editor just to have something batteries-included
Right? I mentioned this later on but the nature of duck typing is that if you hear something quack enough it's hard not to eventually refer to it as a duck
one thing regarding the style: might want to think about a microphone that has a slightly wider recording angle. as you get more easy with the back and forth of your head, you tend to move in and out of that recording room. this should be accommodated by the mic, please don't try changing the body language :D
Yeah, I think for now I'm just going to gently increase the gain so less stuff gets lost that volume smoothing can't get back and make a point to not move around so much.