vikingcaffiene

I'm a tech lead responsible for deciding stuff like what front end framework to use. I have a personal preference for Angular and svelte but earlier this year when given a greenfield project I still went with React (with TypeScript of course). As the author correctly states: always bet on boring.

I dunno man. Like you, I use vim for lighter text editing tasks and JetBrains stuff for times I need to get serious. Your comments make me think that maybe you haven't spent enough time with vscode to appreciate it though. I think for a lot of folks its a really good middle ground and I am pretty sure MS's long game on it is as a replacement for Visual Studio (that might be projection though. I've always hated that IDE...).

I guess I am saying that its a perfectly valid choice as a ones primary editor. I used it for a couple years and I have nothing but good things to say about it. I just happen to prefer vim + Intellij (with vim keybindings of course!!) :)

I recently migrated part of a platform over to a distributed architecture with a heavy reliance on serverless functions. We had very specific reasons for doing it that I wont get into, but I can confirm that its an unbelievably bad experience from a development standpoint. We tried all the usual tools like localstack and SAM local and it all just suuuuucked. Something that would have been a day or twos worth of work with a tranditional api endpoint would stretch out to weeks. We ended up getting fed up and put all the calls to our serverless functions behind interfaces. Then, when running locally, we swapped out the transport layer to call a simple webserver that can call the the functions directly. We've been leveraging that approach for a few months now and its smoothed out a lot of issues for us. The downside of course is that you aren't using the same networking as whats deployed but so far it hasn't been as much of a problem as I was afraid it would be and our velocity has increased quite a bit.

I would go as far as to say the unfriendly local dev experience is almost the point. They want to lock you into having to use their platform to get anything done. They want to make this stuff as difficult to abstract as possible. They want you to use their proprietary methods for code sharing (looking at you lambda layers...). All of it is designed so that you simply can't run your logic without tying yourself inextricably to their platform. It's a spiderweb that you don't notice until you are trapped in it.

The author makes compelling arguments but I respectfully disagree with their conclusion. Null exists for cases where you want to set the the absence of a value intentionally. It is literally the value of having no value. Undefined exists for cases where no value has yet been set. It's a subtle but important difference and allows a certain amount of nuance and expressiveness in ones code to communicate intent. I do think it's fair to say that a lot of devs don't use them that way. They _are_ for separate use cases though.

Everything I've heard about the panama papers suggests that it's a massive scandal that exposes how the rich and powerful are systematically fucking over society. The sad truth is that even though it's been exposed, the scheme is too complex for most people to grasp. Hell they even made a movie about it and no one paid much attention.

I stongly encourage anyone who uses a kindle for reading ebooks to back up their library via Calibre. If Amazon tried this rediculousness theres still a way to get all your content back via plugins that can convert them to plain epub. Unethical? Not if they steal from you first.

Currently migrating off a graph database and back to a relational one. It's been a bit of a nightmare. I think there are legitimate use cases for the tech. Yours probably isn't it.

My boss is a Linux lifer. The kind of guy who compiles his own kernel and knows this stuff in and out. I mentioned that I got my first Linux machine to him and that it had an integrated GPU. First thing he said to me was "that was a mistake". From what I've seen I would agree. My machine is way glitchier when I enable the Nvidia GPU. If I had the option to run multi monitors without it on, I'd probably never use it save when gaming.

IMO they should remove the number pad and use the extra space to add some decent speakers on this thing.

That said, they don't have as much control over the hardware as I would hope. As I initially said, this is a rebranded clevo so they are kind of stuck with whatever they source from them.

If I am not mistaken, Linux is known to problems with higher rez screens. Honestly this is the best looking laptop screen I've ever used. My previous machine was a retina screen too. Its bright and crisp and easy on my eyes. I have some complaints about this machine but the display quality is not one of them.

I own one of these as my daily driver. Its... fine.

Pros

- dead simple to upgrade the hardware. I was able to get 32GB of RAM and 3 1TB hard drives installed with no hassle or voiding of warranty.

- its a beast of a machine when you spec it out capable of any workload you throw at it.

- linux support is 1st class (obvs)

- all aluminum chassis

- the display is nice even tho its only 1080p

- the keyboard key action is nice. I have a thinkpad for work and they are similar feel.

- PopOS is amazing.

- the backlit keyboard is cool

Cons

- you cant use external monitors without the NVIDIA card enabled which requires a reboot. This is the single largest failing IMO and is more annoying than you'd think it is.

- you only get about an hour of battery life with the NVIDIA card enabled making it totally useless to keep on unless you plan on using this thing like a desktop all the time.

- its a rebranded Clevo laptop and kinda ugly. It feels cheap to me despite the aluminum chassis.

- the keyboard layout is weird. The number pad is unnecessary.

- the speakers suck. Seriously. Like my headphones lying on my desk sound better

- web cam is crappy

- the screen itself feels flimsy

- I dual boot into windows and its a second rate experience there.

My partner is a novelist and owns two of these. She's been drafting with them for a little over a year and swears by them. She says the appeal is that you can't go back and read more than a few lines so you just kind of go and then edit later. I also think the appeal is the keys themselves. Similar in feel to an old Thinkpad.

> I'd imagine Buzz would be pretty mad

He's already knocked one dude out. Might as well add me to the list ;)

I agree with your sentiment. My mind honestly can't wrap itself around the terrifying sense of wonder and vulnerability those guys must have felt being up there and looking back at earth. Incredible.

Saw a video of him responding to another skeptic by beating the shit out of him [0]. Honestly when people are that deluded a good knock on the head might be a more persuasive argument...

[0] https://www.floridatoday.com/story/tech/science/space/2019/0...

[Edit] Mixed up Neil with Buzz... oops. -_-

> played what he wanted to play > Didn't include most of his hits

I am always baffled when people expect a jukebox from artists of this caliber. When I go to see an artist I want a unique experience. Dylan is known to rework his songs on the fly live and you never know what you're going to get. He's got one of the best backing bands on earth who can go wherever he wants too. Sometimes it works sometimes it doesn't. Sounds like you might have caught the former which sucks but it's the nature the way he approaches live music. It's anything but safe and doesn't always work. That takes serious guts IMO and it's much more exciting that seeing some geriatric geezer punching out his hits and "collecting his fee".

As a musician who came up with the touring model, I've been struggling with not being able to gig and connect with people. There's a real visceral phenomenon that happens when you play live. I think it's fair to say those days were waning even before COVID.

I found the sentiment of this article comforting. It points to a way forward to make music and get some of that connection back. I don't know that there's any substitute for the real deal but that's probably because I'm old. ;)

I just switched from logic to reaper a few months ago. It's an incredible piece of software that does everything and more that I need from a DAW while also being able to load all my plugins etc.

It's lighting fast and completely customizable too. Oh! And the video tutorials with Kenny Gioia are incredible.

The only criticisms I'd level at it are that it's initial configuration is not that user friendly. You also lose a lot of software synths and stuff that you'll need to buy if you are migrating from logic (I already used Native Instruments stuff so it wasnt a big deal for me).

For $60 it's hard to beat. Way better than pro tools imo.

And NY never saw a single ventilator from him.

Thank you kind stranger :)

Yep! :) Sounds like you've thought it through and I see your point.

Thanks for the perspective. :)

IMO the only downside to your approach is that it couples your action creators to the calling component. That isn't necessarily a bad thing but it all depends on what your particular goals are. If you intend to have your action creators as a kind of "super prop" that is specific to your caller and disposable and single purpose in nature, I think that works. To be successful (again IMHO) you'd want to segregate your business logic outside of that layer into either the reducer (as the redux team recommends) or in a service layer that the actions can talk to (my preferred approach). As always YMMV.

I love Redux but I am very frugal about what I put into the store and have come up with a strong set of design patterns with my team to know what should and should not go there. That, in conjunction with hooks for any other stateful concerns we have, makes for a sane and pleasant dev experience.

IMO the biggest and best draw of Redux is how it allows you to completely separate your business logic from your UI layers. Your components only know about props and state and are rather trivial to test. Hooks are great for re-usable logic as well but my team made the choice to have hooks deal only with localized state concerns and have a robust Actions => Services => Reducer layer for everything that speaks to things outside that constraint. Its worked out wonderfully so far. Tests are a breeze and logic is highly portable. Our UI layer is thin and easy to change.

Its not all roses of course. The Redux store can turn into a rats nest of keys and values with no obvious structure (or worse, duplicated structures). It's something that requires actually sitting down and modelling out your data structures. Sadly that's something I don't see very often (and I am just as guilty as anyone else). The Redux team came up with some good guidelines on this point (too lazy to track the link down but its on the main site) and I think they have some really good ideas. I think more than anything its important to consider your store in the same manner you would a database and approach it with that kind of mindset. As with all things JS, its easy to dive in, hard to untangle yourself! :)

Lost me there too. FF has had a few foibles but has course corrected quickly. It's my daily driver and certainly haven't seen anything like that happening.

Every single one of these tools only connect to Gmail. It's kind of a bummer.

There are a few sure things in life. One of them is that speaking of OOP in a positive light will get an immediate comment on the orange site saying that it's garbage. Its almost comedy at this point.

IMO there's two ways to read this: either A) this is a baldly transparent attempt to "own the libs" and punish a company that the administration sees as a threat or B) they are too incompetent to understand the technical nuances of the case and are essentially morons. Maybe both? This administration can't be thrown out on their collective asses fast enough...

This is gatekeeping trash.

This dude isn't the authority on who gets to be a hacker and who isnt. I work with some bootcamp grads who have "earned" their skills every bit as much as the "real" hackers this dude's yammering about. This clubhouse bullshit needs to die. If that's what's getting killed I'm all for it.

Early versions of the Phoenix frameworks ORM would select every record if you didn't pass it an ID. I didn't know that and wrote a deletion endpoint forgetting to put said ID in. Tests passed (I mean it did delete...) and off to prod it went. Long story short: I deleted data for all our users. Thank God for backups.

In addition to being completely accurate, this is one of the funniest things I've read on this site in a long time. Thanks for the laugh.

Yep!