tetek

Quick dirty copy of Slack, bundle it ("for free") with the Office which people already pay for. Adjust the bundle price few months later...

Nice price to value ratio, I think the screen is the biggest downside, but that's only in comparison to my MacBook.

There's just a lot of other activities that Systems Engineer does (and still consults them with the team, but is at the end responsible for doing them). (all the bullet points in "The realization")

For 'simple' systems, Systems Engineer is not needed. Typically Software Engineers share architectural responsibilities.

I recommend listening to this https://youtu.be/pSfZutP9H-U?t=386 from 6:30 to 10min. I find it very valuable.

> I find the larger problem is how most engineers define "smart people" - they typically only mean someone with a high technical aptitude when really things like communication skills, collaboration, motivation, etc. are better indicators success on a software team.

I agree 100%.

it was easier to blog when I was a teenager, but I like to keep a personal website

Actually I've wrote about couple days ago: https://audiobased.app/articles/screen-time-and-headphones-t...

btw. I would be happy to learn what setups have you seen

"Send me a link to a news story that turns out to be a video, or an audio file, and I’ll close it unconsumed: I haven’t got that kind of time. Send me a transcript: I’ll finish reading in half the time it would take me to passively sit there while it played, and I’ll more clearly remember it."

The author is ok with sitting and staring at the article because it's faster. What he misses is that it forces you to actually be in a position / context where you can read from the screen.

Personally I have been giving a lot of though about balancing how I consume content. Text vs audio. Walking / exercising or whatever instead of reading.

I don't believe we should optimise on "time to consume" but rather "healthiness of consume".

For eg. One feature require backend & frontend work, after a week of work engineer says that this is done. So you ask him to demo, and it turns out he is doing a backend demo with some dev tools.

From a product perspective nothing has changed. Top engineers understand, that no one cares that only one part is working, they know the end user and will not bother managers/product owners with partial solutions.

2. Are willing to help with getting proper requirements

3. Don't need a JIRA task for everything

4. Don't say they are done if something is untestable

5. Are willing to do stuff other than their skill (eg. one of the graphics required for the project is too big, top engineer opens up gimp, resizes and continue. Bad engineer will report to manager that design team did shitty job, reassign JIRA ticket, write two emails and wait for new a graphic)

6. Top programmers deliver well packed, documented software, keep repository clean with easy setup steps accessible for everyone.

7. Top engineers enjoy what they do, and are making the project enjoyable for everyone, keep high morales and claim responsibility

I've been doing my master's degree there. Although I've never finished the final paper, I consider it to be one of the best decision / time well spent.

Great staff. Professors are just awesome (some of them are also lecturing at abroad universities). Students as well. You will find the brightest polish minds there (the entry exam is not that easy, and big part of the students are math Olympiad finalists).

Courses:

1. Logic - Poland has produced some of top logicians, you can see the inheritance during the lessons. Loved it.

2. Compilers - you will be able to compile in head and on paper. JVM/LLVM/Assembly, you will learn how to write parsers, compilers etc.

3. Cryptography - there are a lot of crypto enthusiasts in the department, you will learn anything you need.

4. Parallel computing - access to super computers, programming Nvidia, verification.

5. Seminars aka what you want to focus on, there's a long list from which you can pick from. My main focus was on game theory, and I've learned a ton and had a great support from professors.

Perks: FAAMGS companies line up couple times a year recruiting for internships and work (always seducing with free pizza). Some of the students I know spent every summer in Bay Area, and would accumulate enough money to live in Warsaw for the next academic year.

Also don't do that (social login etc), if you want low maintenance.