HN user

JoshCalbet

31 karma
Posts2
Comments34
View on HN

Lots of content which I actually enjoy reading. Advise regarding career path. Last but not least, ability to see people who shares my point of view without having to engage in an endless feed.

I'd say look for good funding and someone who is willing to provide plenty of freedom on your research program (the ones who people say they are always busy are good candidates for advisors) make sure that this person is well connected and can get you some contact to help whenever you are stuck.

There is so much inertia in a big organization if you want to do something, it is better not to ask and work on it and keep pushing things forward until someone explicitly ask you to stop. It is not productive and possibly dangerous to be waiting for approval or even guidance, when there is so many things to do and no one offer to help, stop looking for guidance, dive deep into the code, solve the problems and make a defense of your solutions.

That was a life changing lesson. I became more productive I got rejections a couple of times, but the rate of success was way more than I expected.

Build a portfolio that speaks for your work and experience. Take those projects and make them worth to be shown. That way you can show concrete examples of your work with programming. Make them open source, show them on your github account, that way the interviewer will know that you have an idea of the workflow. Even better if you can get some issue on an already existing project you'd like to contribute, fork the repo, fix it and get it merged (repeat).

That will help a lot, if you fail in a couple of programming questions they can relay on your ability to learn and get things set up and running as your previous projects.

Regarding the "Eat better" thing. It helped me when I heard some lecture advising to be careful with what you eat because what you eat is what you become. Like literally, because everything you eat will be broken into pieces, the pieces that will replace the exhausted cells on your body :)

It helps the realization and be mindful of your emotional state. I have felt the same and I just say to myself "It is Ok. Just keep doing it" I remember something from someone saying "Don't compare yourself to others, just make sure the one you are today is a little bit better than the one you were yesterday" and the process is incremental.

I take a break whenever I feel stuck or that my work is useless. It may be useless (for other people and for myself sometimes) but at the end of the day is that I enjoy the process what really matters.

I'd suggest to go trough the fundamentals. Make sure they understand the workflow on Django and a project that they can actually take into production, don't make it too broad but care about the fundamentals, so they'll be able to solve their own problems in the future. It doesn't pay well in the long run to make a project too broad. I'm not sure if Django is the right thing to start but that depends on your motivation. Think about python notebooks, for instance how to connect to a well known API, to grab some data and play with it using data structures, plotting. Things that they can see without investing too much time in server configuration. Most probably you already know it, but colab.research.google.com is a ready to code python notebook

You are either creating or consuming content at a given time. Yes I have long breaks (I haven't used facebook in 10 months or so) I realize the negative impact on how the algorithms are designed to keep away things that you "dislike" and makes you thing that "everyone" thinks like you (to keep you engaged right?), the internet bubble so to say. Don't let these things take away your time. Just remember, things like that will most probably be there for a long time (if not always) but your time, health, and learning capacity are fading away as the clock ticks

I'm sorry, I stopped reading when I found:

From a billion events, this “trigger mechanism” keeps only one hundred to two hundred selected ones. … That CERN has spent the last ten years deleting data that hold the key to new fundamental physics is what I would call the nightmare scenario.

These words show their opinions come from someone that does not know/understand the technology behind these systems and behind the computing power and capabilities at CERN. Of course, they have limitations, but are the kind of limitation that keeps pushing technology forwards. Using quotes on the trigger mechanism is saying how strange those concepts are for them.

The trigger system is a fine tuned filter that allows the electronics to work, otherwise they will be overloaded and will crash as they will be receiving a rate of data that simply can not be handled. How this trigger is being set depends on the specific physical process that is being studied and is supported by theory and simulation, the scope that can be tested is also limited so the selection is highly scrutinized and reviewed

What makes it absolutely necessary for users to sign up before they can try your app?

Offer some kind of reward, like cashapp, paypal, etc...

Why do I have to give my email even for apps that should be able to work perfectly fine without an internet connection?

Number of users lead to monetization ad a way to reach them a channel to do it.

Do you track how many potential users are disgusted by this, i.e. by comparing the number of total downloads versus signups?

You should definitely do this. These numbers are vital to create strategies for growth

To improve codebase is harder than building from scratch, as you have to get familiar with it first and understand what other developers have done with it. Now you have experience you have a feeling of how to make things ~right. But as other mentioned the way to get better is actually to build stuff. Take a project/idea you'd like to see alive and chunk it into small/workable pieces that on the first place make a set of "deliverables" that keeps you engaged in your progress (you probably didn't have to do this with previous codebase). Then start the action! I'd suggest to focus first on the list of "easy" deliverables so you can get started and get confident as you connect pieces together. In the process you'll see how the list of deliverables grows but also you have to know where to stop (as most people from Academia do not know), for this ask yourself what is the minimal set of features that your project need in order to work? once you have gone through this minimal set you build from there and you can even return to see what can be improved (just as you did with improving codebase).

To get a projects/ideas look at your own needs and think what you would like to be improved to make your life easier or make some tasks less annoying or ask other people, there are a lot of people with ideas around there but very few people willing to invest time to implement them