Hacker Newsnew | past | comments | ask | show | jobs | submit | malort's commentslogin

Including, unfortunately, this usage of "literally."


You're literally being a like, linguistic pervert rn


I read this in a Moon Unit Zappa voice.

https://en.wikipedia.org/wiki/Valley_Girl_(song)


What other use of literally is there?


Were you not aware what hapoened to the word several years ago?


Malort implied butlersean’s use of literally is incorrect, which it doesn’t appear to be.

I am aware that groaning about incorrect usage of literally is a meme but that seems to also require being wrong about the usage being incorrect.


> the author’s complaint that he doesn’t get to spend 100% of his workday coding/testing/documenting

The author's complaint was that he only gets to spend 12-25% of his time on these tasks on a good day.


Wishing he had chosen a path in life like most of his drone buddies who settled down, mated with a queen, had their genitals explode, and then died immediately after?


You make it sound like a bad thing


You can see a classic example here (around 2:20): https://www.youtube.com/watch?v=U5vnpOp0U_g


Can you elaborate on "contracting through recruiters"? Did you respond to recruiters who were reaching out to you with full-time positions and say "no thanks, but what about a contract instead?" If so, do you have any particular strategies for getting to a "yes" with that approach?

Or did you mean that you reached out to recruiters and worked out a finder's fee arrangement if they brought you contracts? If so, how did you find recruiters to work with who weren't already engaged with clients and might therefore have a conflict of interest?


I live in Australia so it might be a bit different in your country. The work started for me as shorter term contracts e.g. a recruiter would say "I'm looking for someone on a 6 month react JS project". I would provide them with a day rate and go work for the client as a standard employee. Overtime this has led to me meeting a lot of people, getting a lot of experience and building a client roster of my own.


I’ve found some recruiters just default to W2 because it’s less headaches (and potentially more money) for them. Sometimes it’s a requirement for the contract. You don’t know unless you ask


The first versions of Anki (ca 2006) were based on spaced repetition algorithms developed for a piece of software called SuperMemo, which came out 21 years earlier in 1985 [0].

Piotr Wozniak, the author of SuperMemo, writes a lot about spaced repetition and memory in general. What you're describing are basically items 1 and 2 of his "Twenty rules of formulating knowledge" [1]: "Do not learn if you don't understand," and "Learn before you memorize." It's an extremely useful article if you're a heavy Anki user.

0: https://supermemo.guru/wiki/SuperMemo_Algorithm:_30-year-lon...

1: https://www.supermemo.com/en/archives1990-2015/articles/20ru...


This is exactly what Shopify does with their monolithic Rails app [1]. I worked at a company with ~200 engineers that used the same general architecture and I really enjoyed it. We got a lot of the benefits (clear interfaces, teams able to work on their system without having to understand the whole platform, build optimization, etc) without any of the operational headaches that come with microservices.

[1]: https://shopify.engineering/shopify-monolith


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: