akullpp
But also that you need Raycast, caffeine, rectangle and many more shows you how f’d up software development is at Apple. Every software they produce is utterly awful without a single exception.
But of course fanboys continue to praise everything they do blindly because of one presentation in the 90s where Jobs mocked Windows.
Same goes for iPhone, the software development has no clue what they are doing. And Android software is light years ahead of anything that Apple produces in-house.
We are an autonomous robot orchestration platform already live and operating in the logistics and delivery domain and can offer the stability of a well-funded, semi-governmental incubation with the speed, culture, and upside of a high-growth startup.
We aren’t looking for a specialized ticket solver. We need a high-agency engineer to own critical pieces of our stack (currently Kotlin/Spring/Postgres/AWS/Next).
You will thrive here if you value pragmatism over perfection and autonomy over oversight. You don't wait for tasks; you identify what needs to be built next to move the needle. You are comfortable working in a high-velocity environment where you define the roadmap, prioritize the work, and see it through.
Skip the cover letter, send me your CV: [email protected]
alias df='duf'
alias ls='eza'
alias ll='eza -l'
alias cat='bat'
alias cap='bat -p'
alias man='tldr'
alias top='glances'
alias grep='rg'
alias ps='procs'
alias cd='z'
alias g='gitui'
alias gs='git st'
alias gp='git pull'
alias gu='git add . && git commit -m "Update" && git push'
alias check='shellcheck'
alias v='nvim'
alias len='wc -l'
alias uuid='uuidgen'
alias src='source ~/.zshrc'
12.5% Meetings
12.5% Documentation
50% Requirements engineering, i.e. talking and trying to figure out other people
Myself on the other side worked 2 years as a software engineer and that's as much as I could taake:
* politics
* too many artificial restrictions
* worst management I've ever experienced
* Work doesn't get valued at all, cancelling so many projects and ideas amounting to nothing
* lower reputation than "real" engineers, they still don't understand the value of software, like so many German companies, and treat us as necessary evil, which is also resulting in not competive salary
If you shut up and just come to work every day, you certainly "made it", but for me that's impossible.
Why not merge them and work with lists, I think a lot people would intuitively understand the following:
GET /users?ids=1
{ "users": [] }
GET /users?ids=1,2,3,4
{ "users": [ { "id": 3 } ] }
Transport the ids in any way you like, that's not my point.
If you want to go deeper in understanding the West, it's recommendable to also get a rough idea of it's philosophers, especially the Greeks and the important ones up to Kant, including Descartes' idea of the social contract.
If you still want to know more, you should read about the most important economic ideas, e.g. Smith, Keynes, Marx.
While I agree that it is a good idea to optimize chores, so you can focus on interesting issues, I often hit a wall of processes or humans.
One consequence, after a decade of professional work, is to actively dismiss the idea to optimize every part of my life. On the contrary, I value the time where I do nothing at all. It often allows me to clear my mind to be more creative afterwards.
So what I'm really missing, from this very basic article that does not provide any new information, is: Take your time off and do nothing.
Many people see their value directly tied to their career and one of the major ways to make you (feel) important is to be present. It also helps your career since many old companies value presence over other criteria.
I'm three weeks ill now and for the first time, I begin to understand that I've never been detached from work. In the first two weeks I actually became so depressed because I couldn't work. I need to do something, don't know what yet. This is bad for my relationships and for my mental health.
Awesome Java
Fresh out of university and having already finished projects for several companies, I asked myself what to do next in the big Java world to gain proficiency. The typical answers suggested to learn Java EE or a specific web application framework.In attempt to find important, good and inspiring libraries for Java, I searched and searched and finally saw that there was no concise list of...