tyurok

As a general content I agree it's a bit off putting, but I find it a lot of fun when generating content among friends like internal jokes and educational content. I got my kid to drink some meds by generating an image of a hero telling him it's important to take.

They're not getting their nickelback.

It seems it comes back every year or two, coincidentally on market downturns.

Yes but it seems the order is taught is important. Without actual industry experience, it never occurred to me it could be useful.

After some years working, it's clear it's useful in some capacity but it's easy to overdo it (like require every detail of the system to be in those formats) or misuse it (sequence diagram improperly documenting async flows).

It's a thing because inheritance got out of hand.

Inheritance x composition is orthogonal to OO.

I didn't go through, but have seen quite a few. It's indeed a less advertised position since it might be more common in smaller companies (less money/reach) and it might be a founding opportunity (less pay, higher risk), so it goes under the radar compared to very specialized positions.

Yeah, poliglots are difficult to find as well, maybe not as in actual difficulty to be but more of a preference for a subset of techs.

It's a fairly rare set of skills. People in these positive usually are bad in most of them and it becomes harder to ramp up the team later (mentoring, quality).

Generalist can be a specialization in itself. Imagine someone that can do a bit of front-end, backend, infra, design, would be a specialist in bootstrapping a startup.

Don't get too attached to market/industry defined roles.

Another way to raise rates is to take risks (like deadlines, promises) but every person had their own risk profile.

Art imitates life until life imitates art.

Jon Ronson has a good audiobook covering this[0] with a follow-up on a pornstar's death[1].

It covers a little bit of the MindGeek story but primarily how pornhub rebuilt the industry.

[0]: http://www.jonronson.com/butterfly.html

[1]: https://www.amazon.com/The-Last-Days-of-August-audiobook/dp/...

The annoyance over non-functional code is real.

I can't tolerate OOP stuff that `obj1.calls(obj2)` and changes `obj2` anymore. I didn't care before, now it makes me want to refactor everything or not write it at all.

Using Elixir kind of made me not want to use anything else.

I personally like a lot the help in the shell feature that is one of the awesome things in elixir's shell that is now on erlang.

That's where "works on my machine" comes from.

The further you steer dev environments from production, the more you'll have these kinds of issues.

Would you mind expanding on their explanation? The way you described doesn't sound like an argument at all.

I particularly like his silver rule principle as it indeed seems like a better version of the golden rule.

We had a friendly deal in our office for those kind of disturbances.

If you leave your phone ringing at your desk, you pay a round of drinks for the team.

I used to do something similar until I got a standing desk.

Now I just switch between standing and sitting and having a blast.

Second that.

Pain is constructive in the right dose, and it's also risky since you can lose trust if delivered incorrectly. It requires maturity to give honest feedback and recognize that it might be biased since we have a lot of limitations on how we perceive others.

I have experienced this.

The most brilliant programmer I've ever worked with wrote hardly comprehensible code since they could understand other's code easily, so they didn't feel the need to write readable code because, in their word, "What do you mean you don't understand it? It compiles, it runs, it works, you don't need more than that".

(I'll take a stab at this, but my knowledge is rather limited on this one so take it with a grain of salt).

Markets are a mix of locality. Some markets have more global reach than others.

The car mechanic example is a mostly local one, with the car parts being shipped from somewhere else, maybe in the same country or outside, which might take some influence on the price. Operation cost is local (rent, labor, other supplies) and customers are local, so the prices on mechanic services are stable and location based.

Software engineering has more global reach. It can be done remotely, but the labor is a mix of local and global (learning online, but also local universities, conferences, meetups), which justifies the pay gap between a local to the company (excluding timezone and culture differences, which makes the process and supply size smaller). It's also hard to evaluate the quality of work (see difficulties in hiring, analyzing performance).

The strongest argument I see is the cost of comfort (made somewhere else on this thread). Wages are largely decided on what other companies are paying and remote is a fairly new thing, so it's still highly unstable.

Pricing on products are also notoriously difficult. Some apps have prices adjusted by region.

It's mostly used in the kanji version (積読 or 積ん読) (7m+ results).

I've worked on an open plan startup and was a slack admin.

90+% of the messages were private, and we had pretty good activity on public channels.

In Brazil, it's "sequestro relâmpago", roughly translated to "lightning kidnapping"

It's also the problem that software is not strictly a product, but a mix of service and product. There's the core product that you are selling (say e-commerce) and there's the customization service that's been sold to increment the product per-customer basis.

Traditional sales knows how to sell either a product or a service, hardly the mix of them, which makes software special (but not unique).

EmCasa | Rio de Janeiro, Brazil | Several Positions | REMOTE We are a real estate company changing the way you buy and sell real estate in Brazil. Speaking portuguese is required. We're looking for several positions:

- Backend Engineer (Elixir) - Frontend Engineer (React, Next, React Native) - Data Engineer - Data Scientist

https://jobs.emcasa.com

Greg Young - The art of destroying software

He has a few talks that he barely uses any presentation material and it's very good.

EmCasa | Several positions | Rio de Janeiro, Brazil | REMOTE

We are a real estate company changing the way you buy and sell real estate in Brazil. We're looking for several positions to grow our team.

Our stack:

* React + Next.js

* React Native

* Elixir, Phoenix and Absinthe (GraphQL)

* Postgres, ELK

We're looking for:

- Frontend Engineers

- Backend Engineers

- Data Engineer

- Data Scientist

And also operations, sales, HR and finance openings as well.

Speaking portuguese is required.

https://jobs.emcasa.com

iex runs smoothly because of erlang's console and ExUnit runs in parallel leveraging BEAM, so it's considerable. The foundation was pretty much there from the beginning.

I use boostnote[0] for my personall stuff and slab[1] at work.

Boostnote can sync my notes with dropbox and supports markdown and code snippets with a nice desktop app and is free.

Slab has a collaboration functionality similar to google docs and it's easy to share notes with my team, with ok pricing.

[0] https://boostnote.io/ [1] https://slab.com/

We are trying to use https://slab.com/ to share those kind of stuff, it's been a great addition.