emerongi

Sure, but if an interviewer phrases it in this way, they should also fully expect to be shut down. I don't see any reason to not just go "talk me through the projects on your Github profile". To me it signaled that they minimalized my work, especially because there's at least 3 projects on my profile that I'm more proud of than any non-public work I've done in my professional career. Maybe I'm sensitive, but I guess it just signals that there won't be a fit.

I think if your resume goes through HR or automated filters first, they will filter out any personalized CVs. It would need to land directly on the table of an engineer for it to be appreciated.

A diligent employee who gets the job done in an efficient way because they want to get home to enjoy the money they just earned?

I think none of my coworkers in different jobs have had Github profiles with public code.

I have a Github profile with multiple public repos, but I don't think it helps with anything. I once had an interviewer say "it seems like you don't have much on your Github profile".

> that they would write me a short answer about what piqued their interest

Honest question: do people actually apply to jobs because it piques their interest? I pretty much just... need a job. I'll assess whether I want to join based almost purely on the team - if the team doesn't feel right, I'll skip.

I don't apply for any jobs that require a cover letter. There's already enough information asymmetry and the effort required from the candidate is a lot higher than from the company as the company can distribute the work across multiple employees. A cover letter is a way to shift even more work to the candidate.

I barely know Erlang and life has been fine. I do know the runtime characteristics of the Beam VM and occasionally I need to read Erlang docs, but compared to other stacks the experience has been significantly more pleasing.

People are of course different and I fully acknowledge that things that seem normal to me may seem odd to others, so YMMV.

> Is there easy tooling for deploying to something like AWS ECS and having nodes communicate with each other?

libcluster[0] has a bunch of strategies to form clusters. It seems that ECS supports service discovery through DNS, so the DNSPoll[1] strategy should work.

[0] https://github.com/bitwalker/libcluster [1] https://hexdocs.pm/libcluster/Cluster.Strategy.DNSPoll.html

Sleep deprivation is not as dangerous as dying from an acute condition. If you're in the hospital for one night, you're being treated by doctors who want to make sure you're not going to die for the night. If you get admitted for a longer period, it's a different environment altogether. At least this has been my experience.

You get used to the beeping after one night anyway. If not, you can ask the nurse for earplugs or even sleeping pills (although sleeping pills are harder to get).

This is my most important lesson in the past few years. There is value in _not_ learning, building, doing all the time.

I like to work and study, but doing either of it for more than 8hrs is not sustainable for me. I expect to be writing the modern-day equivalent of Fortran when I'm 60. All the young bucks will look down on me for not advancing in my career, but I think I'll be happy. That's all I need.

Everyone has their own balance point. John Carmack can work 12hr days and improve at various subjects continually, so his balance point lies somewhere else. Don't try to be Carmack if you're not and you can still live a fulfilling life :).

> nor more maintainable

My humble opinion is that it is more maintainable. Additionally: more fun to use, has less warts than the other languages mentioned and provides really powerful tools out of the box in an easy-to-use manner. I'd be interested in a study observing work stress levels of employees using various languages - my assumption is that Elixir users have less stress.

The home row is the whole row of keys. jkl; are the home keys of the home row that your fingers rest on.

What I'm looking for in an API is convention and some common set of rules. As long as the API has an understandable structure and good documentation, I'm happy.

The first case would be preferred if the API is for e.g. general queries of companies in some region. The second case might be preferred if your API only deals with those specific companies and has a different structure for each one (for good reasons).

You can also provide both APIs - one for general data, and one for specific details.

Vim has soul. It is that chisel you inherited from your grandpa that you keep using. It fits well in your grip and is comfortable, even though it lacks the soft rubber that the new ones in the store have. It's a tool with its own history.

Reading the comments here, it seems that the hacker's mentality still lives on. The new young billion-dollar company will be replaced in another 10-20 years. Vim lives on. I wish to build a Vim of my own one day.

Although I use vim, I associate these letters more with the home row for touch typists.

Also in Europe and most doctors just want to get you out of the office. I've met only a few doctors who actually care and will work with you to figure out the issue. The equivalent in software engineering would be waiting for my client to tell me what line to change in what file.

To be fair, doctors are usually overworked and on a human level I understand that the system is a bit broken, but it's still infuriating when it's your health that is suffering.

If KDE isn't Desktop Linux, I don't know what is.

It's not "vanilla", but so isn't Ubuntu, Linux Mint, Fedora Sericea, or whatever else. The underlying stack is the same, there's just customizations on top.

It's also because the employer has invested a fair bit of time/money into you and would like to see you take more responsibility after doing so. This is most obvious with juniors, where besides the salary cost, there are hidden costs of training. The expectation is that it will pay off in the future.

I prefer either being in-office or being completely isolated and having complete freedom if working from home. Working from home and having to work by a schedule and do daily video calls feels like taking the bad parts of both options.

For what it's worth, there's many people who agree with you, myself included. Modern society has created unnecessary work, stressors and pressures that are quite artificial. Everybody goes along without questioning it, at least not aloud.

I will admit that I am by nature someone who takes the alternative path. It's entirely possible that the world is working just fine and I am unable to adjust to it. However, I can't change my nature and have to find a different way to live, because there is no other option for me.

You don't think $250k comes with high expectations as well? Salary doesn't always correlate with stress - min. wage workers are probably just as stressed, if not more -, but from my experience, my stress level has increased the more I earn. I also used to think that I'd do anything for that kind of money, but I now realize that I wouldn't.

This discussion probably reeks of "first world problems" to people who have different stress tolerance levels or preferences in life. However, be mindful of the people around you who are functionally capable of earning $250k, but mentally more fragile to the stressors that come with that level of responsibility. There's many of us who would turn that money down, happily.

I'm in my 20s and I've realized that there is little point in killing myself to retire early at 40. By that time, the best years of my life have passed. For what? All to earn a high salary and be proud, while hating my life.

> Greenfield projects are 1% of a SE job.

99% is dealing with the after-effects of the decisions made during the 1% ;).

I used to live in an apartment where the upstairs neighbour would just randomly start trampling super hard. If it had been a constant noise - like the cars driving outside - my brain would probably have gotten accustomed to it. It seemed to me like it was agitating because it was at random times, when I wasn't expecting it.

When I turn on the bass, I am in control. I can turn it on when I don't have anything important going on and I can always turn it off. That makes the bass enjoyable. If it's somebody else's bass, then I don't know when it starts, when it ends and whether it will interrupt me. That's the source of frustration for me.

I'm generally fine with monotonous background noise, as long as it's not too loud. There's probably still some subtle passive effect on my health, but I can live with that.

I noticed that if you drag a habit to the last position, but a little bit too far, the app crashes. Excellent app otherwise, I really like the simplicity! :)

> It has ways to indicate "things are in flight" but for distant deployments you probably still need to write JS to manage some in-page elements for reasonable feeling UX.

Most JS UIs behave like this: open a list view, watch a spinner until data is fetched from the server. There is practically no difference between that and showing a spinner first and then the list.

A plumber's house always has a dripping tap.

Companies that use newer or niche languages are more forgiving and understand that there's fewer specialists, therefore they are more accepting of people who don't have much experience in the language.

Competition is still high in companies with high hiring standards. I wouldn't say that it's easy to get hired. You just have many more chances to prove that you're good, even if your resume seems lackluster, as companies are more eager to talk to you.

I don't know enough about the market to suggest any specific languages.

> What should I do to get to a point where I feel confident enough to actually send in applications?

If you apply for a junior position: no need to do anything. Everything is relative to what kind of a job you want. LeetCode problems are only relevant in FAANG. I've never done LeetCode.

> Will the 4-year gap and my choppy CV be a major hindrance to my hirability?

The short stints don't look great.

> I feel like I have the best chance of getting hired in the kind of roles I used to work at and those are the ones I'm interested in as well but in doing so am I restricting myself to a limited number of positions?

When you specialize in anything, you restrict yourself. However, specializing makes it easier to get through the interview process. There's a bazillion Java developers, but not that many Haskell developers. Haskell shops can't just discard 70% of the applications, they actually can take the time to interview all the people that apply. A great Haskell developer has a way higher chance to get a job than a great Java developer, probably not that much difference for an average one though.

> Is my timing bad?

Does it matter? If you can't get a job right away, keep applying, but find some other way to support yourself in the meantime.

If you only care about the final image size, then `docker build --squash` squashes the layers for you as well.

You can think of maintenance as one sub-branch of software development, usually containing tasks that do not create immediate value for the business, but need to be done to be able to add new features. It's also a good way to make it clear to non-programmers that a certain amount of time needs to be spent on tasks that seemingly do not create direct value. Maintenance is a concept that everyone understands and is a good way to explain it.

Regarding the project vs product model, it fully depends on the business. Venture outside of the SaaS/FAANG/etc type businesses that HN seems to focus on and you'll see countless businesses that are very happy to just have a project done for X cost in Y time. After that, the project goes onto a maintenance contract, where the development team is just expected to keep the lights on, fix bugs and keep it secure. From my experience, it's a huge part of software development, considering the amount of systems that exist in this form is only increasing.

How to turn a 1x developer into a 10x developer? Stop using Hibernate.

I might still have psychological trauma from it.