vikingcaffiene

I have an OP-1 and love it. Its a mainstay in my recording and live performances and honestly my "main" synth despite it looking like a toy. I keep finding new uses for it. Example: I needed backup vocals for a part and none of my bandmates could do it. I sampled the backup vocals and just play them while I sing lead in that spot. Really cool.

As for this mixer, I would love this bit of gear but I just can't justify spending that kind of scratch for what essentially amounts to a mini mixer (which I already have). It seems really great though and it being battery powered and tactile like that is great.

Fair enough. I still think people should read stuff like this with a healthy measure of skepticism.

Gentle reminder to anyone reading this that your problems are probably not FAANG problems. If you architect your system trying to solve problems you don't have, you are gonna have a bad time.

Yeah you have to use the appropriate strategy for the interviewee. In the case of a junior, you are looking for potential and teachability as you said. You tailor your questions towards that angle. I've yet to see any take home or live coding challenge that answered those type of questions for me. All it told me is what I already knew: they were more junior and needed mentoring.

This is the right way to go. If I were looking for a job right now I'd be hitting you up. I've said as much in a few other threads but it's not only the right thing to do, its a competitive advantage.

I'm not sure a lot people know that Albini ended up washing his hands of his work with Nirvana. After the recordings were wrapped and the mixes were done, Kurt was really unhappy with some of the sounds. If memory serves it was the vocals and the bass. They ended up doing some overdubs and sharpening things up in the low end in mastering. The very thing Albini specifically said he didn't want them to do. I personally think the results speak for themselves. In Utero is a FANTASTIC rock record. I can't help but wonder what the original would have sounded like though...

While I see where you are coming from but respectfully disagree with your conclusions.

> My point is that there's less need to test people during their interviews for occupations with licensing, because they've already been tested before they even showed up for the interview.

I mean past job experience and education are pretty good indicators? Is there some facet to the accounting certification process I am unaware of that filters out under performers? If my past few accountants are any indication, then no. :)

All of that aside, I've not seen any data that suggests the hiring practices common in our field produce better outcomes than that which I am evangelizing for. Furthermore, those practices are common FAANG type companies which can offer much higher compensation packages than a typical startup. I assert that it's not only the right thing to do, it is also a _competitive advantage_ to have a streamlined, humane, hiring process.

> Hiring managers are timid about letting people go and it can take an extraordinary amount of time to part ways with unproductive people.

With respect, it sounds like you had a bad manager. Underperforming teammates are your managers responsibility. They should be working to address that issue with said teammate or part ways. Sucks. Not fun. It's the job though.

> generic backend principles are very easy to spew correct answers for without actually knowing how to code

I'm not sure I agree with this. IMO trying to get someone to explain the ins and outs of a particular facet of the technology your team works in is less effective than getting a sense of how a candidate architects their code and manages complexity. That type of "art more than a science" craftsmanship is not something you can easily fake in my experience. Maybe I'll be proven wrong. We shall see. So far I've had pretty good luck with the approach and gotten some really great teammates.

> Yea because we live in a place where everyone is super honest and no one is going to try and take advantage of that to make 500k a year.

You are right that there is more risk with this approach. I honestly think that its a better, more humane way to do things though. Anecdotally, I've hired a couple _really_ solid developers via this methodology. At least in my case, it's been working out well. As always, you try stuff and iterate.

> I'm an introvert, I suck at communicating orally.

I get it. So am I. Its actually very hard for me to reply to these comments b/c of my general aversion to putting myself out there! I don't think there's a one size fits all solution. At my company at least, being able to communicate effectively both orally and written, is important. We do a lot of pairing and documentation etc. Thats not for everyone. YMMV.

> Accountants have occupational licensing.

Forgive my ignorance, but is this during every interview? If I am reading this right this is a certification they'd need to get which would be on their resume. Do they need to re-prove those skills every time?

Thanks! So, I'll say that we are still tweaking and trying to get things just right but, as of the time of me writing this, here is the process:

- HR call 30 min.

- Talk to hiring manager (me) 30 min. Get to know each other and feel out if there is a mutual fit.

- Technical panel 1hr. Speak with several engineers on the team who share your discipline (front end or back end for example). Again no live coding. We just talk through stuff.

- Talk to the team PM. 30 min. Get a sense of how you collaborate with our product team partners to build new features in our application.

After that it's the usual comp negotiations, background, and reference checks. Assuming all that works out then hired!

We're hiring so, if anyone is interested in finding out more, contact info is in my bio.

Hiring manager here. IMO the current tech hiring norms are gross and not sustainable. It feels like a weird hazing ritual and with the current market, is the single biggest reason you can't hire. Why on earth would someone burn a weekend on a take-home test for your startup when they have 15 other irons in the fire? At my current employer we got rid of all that ridiculousness. No take home test. No live coding. We've gotten the whole process down to a few hours over a few days. I'd like to think it's a mutually respectful process.

I think it's time we accept that the person we are talking to is who they say they are on their resume. You don't see accountants balancing books before they get hired. Why should this be any different? If you aren't who you say you are, its either blatantly obvious in the interview or we'll find out when you join and we'll try to correct or part ways. This is like pretty much any other job out there.

I've never heard of this author. Anyone have any good recommendations on where to start? Specific book titles would be appreciated (its hard to find the starting point in a given series sometimes for example)

Modern Java is actually pretty good. It's taken great features from other JVM languages like Kotlin and Scala and is much better for it. The JVM is a wicked fast run time and its nice to have a mature ecosystem of libraries to work from and large pool of developers available who know it inside and out. You could do far worse when picking a language for your team to use.

I dunno man... I think that giving an entity the ability to perform operations upon itself and thereby changing it, looks neat in these examples but scales poorly in a sufficiently commplex codebase. You could express exactly the same thing but get a lot more bullet proof code if you separate out the thing doing the action from the thing you are acting upon. You could have the thing doing the action return the updated version of the thing you wanted to do said operation upon and its unambiguous what has happened. So something like (psuedocode):

    transferredEmployee = employeeService.transfer(employee, department);

IMO this forces a certain style of coding that ages better and requires keeping less stuff in your head.

My two cents. Have a good one!

Highly recommend Insync[0] as an alternative to these shenanigans. Native Linux support too.

[0]https://www.insynchq.com/

The best explanation of NFTs I’ve heard:

You are married. Your spouse is cheating on you right in front of you with multiple people. But you have the marriage certificate.

My entire household uses Apple products. A few years ago I got fed up and went all in on Linux and Android. I liked a lot of things about it but ultimately came back to Apple. When I switched back to an iPhone my wife told me "I'm so glad you're back on iMessage..." like she'd been holding this dark secret inside her the entire time I was out of the fold.

It's baffling honestly as messaging was the least of my problems. Sucky apps, weird driver issues, and just general friction with simple things like printing were what finally got me.

Heh. I have been at the butt end of that one a few times. Another favorite of mine is when they push back with Parkinson's law: work expands to meet time available for its completion.

These types of lists are nice and I appreciate the time and effort put into making them. I do wonder how much utility they provide though? I personally find it a bit overwhelming. Like is idea that I sit down and memorize all this stuff?

In the past when lists like this come up I read a bit, then bookmark for later. Later never comes and now I just have this bookmark lying around amongst the thousands of others I have made over the years.

Maybe a more useful way to present this stuff is figure out a better way to give you the law relevant to the context in which you are in? For the sake of argument I could see something like this being useful:

INPUT

I am a `_developer_` working at a `_start up_` who `_needs to give_` `_an estimate_`

OUTPUT

- see Hofstadter's Law

Probably a non trivial task and I'm sure there's a law in that list that describes this phenomenon!

I live in Cali. My wife was a teacher. Her salary was nowhere near 97k.

Not on topic but can I just say fuck Reddit for the way they purposely hobble the mobile experience on web? No I won’t install your shitty app Reddit. Ever. I might have considered it before but it’s personal now.

> scheduling on a calendar is not scaleable

> hyper scheduling

Um.. what?

I was a lot more interested in this product until I started reading the marketing copy. To me it reads like the worst of breed of Silicon Valley “solution looking for a problem speak”.

Think of it like this:

I am in injecting a function that returns a `User` type. That is the interface. I, the function accepting the injected function, don't care how it gets that `User` (that's the implementation). I just care that I am getting a `User`.

Now, knowing that, I can inject any number of function implementations that implement that interface. As long as a `User` gets returned it does not matter how the sausage gets made so to speak.

The author doesn’t mention it in the article but the pattern suggested is inversion of control (IoC) which is one of my favorites. Highly suggest looking into it if you’ve not heard of it.

I have a bunch of tattoos. My right arm is sleeved for instance. Not saying that to try to get coolness points here (tbh I don't think tats are even considered "cool" anymore...) but to just make the point that I've got some bad ones I'd rather not have. It's gonna happen if you get enough of them. For instance, I found a painting of a girl in Day of the Dead face paint that I _loved_. Got something inspired by it tattooed on me. A big one at that. The artist who painted said painting ended up being Sylvia Ji[0]. Her stuff is now adorning the bottoms of snowboards and displayed on t-shirts. Would I have gotten that knowing what I know now? Absolutely not. Do I regret it? Eh... not really. At the time that I got it, it was a really different thing to get.

I think the point of a tattoo, the thing that makes them so exciting, is the fact that you can in fact get one that was a mistake and that mistake is permanent. Its inherently a dumb thing to do to yourself and depending on how you look at it, that can either be exciting and life affirming or a reason to never ever set foot in a tattoo studio. Knowing that, you can definitely over think your first one and do something like the author is describing. IMO you just own it. Ok so you got something that someone else has. Whatever! Get more. Get a cover up or get it removed! To me it's kind of an analogy for life: messy, complicated, hard to get out of sometimes. Even getting a bad tat is a ballsy move IMO.

[0] https://www.amazon.com/Day-Dead-Other-Works-Sylvia/dp/099333...

Notion has no doubt taken note that a lot of people (myself included) use them as a quick and dirty wswyg web site builder. This new feature can be used for a lot of things, but it strikes me as particularly good for that use case. In fact, if I were a gambling man, I'd wager that their product roadmap is full of gems like this and are leading to them positioning themselves as a competitor to the likes of Squarespace and Wordpress.

I made the switch back to Apple Maps a while back. It’s great. I’m not sure what specific features you want to know about.

Man, for a dev with as much experience as you’re claiming to have, this comment ain’t a great look.

I’d argue that the more experience you get the more you write code for other people which involves adding lots of tooling, tests, etc. Even if the code works the first time, a more senior dev will make sure others have a “pit of success” they can fall into. This involves a lot more than just some “unit tests as an afterthought to keep the coverage up.”