7 ms·

So many courses demand you start in a text editor and I understand the rationale but I write almost everything in PyCharm and strongly encourage everyone to fin

by bshipp 4y ago

So many courses demand you start in a text editor and I understand the rationale but I write almost everything in PyCharm and strongly encourage everyone to find a comfortable IDE. If the intention of coding in Python is to get stuff done quickly, it seems a bit silly to handcuff yourself by avoiding one of the biggest time-savers.

DiggyJohnson 4y ago
> biggest time-savers I strongly believe there's a balance to be struck between getting started quickly and understanding how your code is run. Especially if it's an interpreted language like Python. If you do understand opening a terminal in your project's repository and executing `python3 ./mypythonfile` then this should be prioritized. Even for noobs.
- grvdrm 4y ago
  Completely agree with your last point. So many of my tools over the years have stuck with their simple command line initiation rather than wrapping into GUIs or other alternatives. Being able quickly write “python [whatever you are doing]” is awesome.
- mavhc 4y ago
  When teaching noobs I first have to tell them how to make folders, create files, what files are and where they are stored, modern systems abstract that all away. I want them to realise that code is just text files, same with html
- DiggyJohnson 4y ago
  Edit: :3s/do/don’t
- bombolo 4y ago
  I worked with "senior" developers who were absolutely unable to run the project they were working on from a terminal. It was either the "play" button in the IDE or nothing.
Stratoscope 4y ago
If I were teaching someone Python, or pretty much any programming language, the first place I would start is the debugger. I would have them write a program as simple as this: x = 1 print(x) y = 2 print(x, y) And then instead of just running it, I'd have them step through the code, line by line, and observe both the console output and the debugger variable display. Some developers seem to think that using a debugger is a sign of weakness, or that it leads you to write bad code. I see it differently: the debugger is one of the best tools not only for debugging, but also to help you understand a complex codebase that you are jumping into.
- zikzak 4y ago
  I end up helping developers when they get stuck all the time and it is really amazing to me how many people get to the "senior developer" point in their career with very little understanding of how to use SQL tracing (e.g. MS SQL server) and IDE debugging. Even the concept of the "print line" debugging into a lot file seems kind of foreign to them sometimes. They instead rely on running the code, changing something, running it again, etc. I am a big fan of reading through the code. That is almost always enough for me to find the issue and point it out to them assuming I understand the input and output context well enough. But if that doesn't work, add a debug point and fire it up. Not using a debugger seems like a massive waste of time in a situation like this. So much so that I have started asking "did you debug this" or "have you watched this happen in a debugger" before I will help out much. If they say "no" because they don't know how, I will teach them to do so.
  - bornfreddy 4y ago
    > ...of how to use SQL tracing (e.g. MS SQL server)... Never met this term before - IIUC, SQL tracing is MS-specific? If I may ask, in what kind of situations would you use it?
    - zikzak 4y ago
      Yes, I think it might be SQL specific but you can normally do this in any transnational db I have worked with (I am old, I don't use GraphQL or NoSQL dbs very often, if at all). Basically, it is just a journal of all queries (really ANYTHING going on in the db but for developers it is useful to limit to queries) and typically filtered by database and by keyword (e.g. table or stored procedure name). You can set up a trace to track long-running queries on a production server (DBA might do this) or on a dev server a developer might use it to capture SQL run from their code (e.g. a complex stored procedure with a lot of input params) so you don't have to try to assemble the SQL using a debugger, for example. A good example might be "I am doing everything right in code, but the data set is coming back empty" so you profile it and realize the SQL is being called with an empty string and not a null, or whatever. When reviewing the code you thought "it will be a null". That kind of thing.

by bshipp 4y ago

DiggyJohnson 4y ago

> biggest time-savers I strongly believe there's a balance to be struck between getting started quickly and understanding how your code is run. Especially if it's an interpreted language like Python. If you do understand opening a terminal in your project's repository and executing `python3 ./mypythonfile` then this should be prioritized. Even for noobs.

grvdrm 4y ago
Completely agree with your last point. So many of my tools over the years have stuck with their simple command line initiation rather than wrapping into GUIs or other alternatives. Being able quickly write “python [whatever you are doing]” is awesome.
mavhc 4y ago
When teaching noobs I first have to tell them how to make folders, create files, what files are and where they are stored, modern systems abstract that all away. I want them to realise that code is just text files, same with html
DiggyJohnson 4y ago
Edit: :3s/do/don’t
bombolo 4y ago
I worked with "senior" developers who were absolutely unable to run the project they were working on from a terminal. It was either the "play" button in the IDE or nothing.

Stratoscope 4y ago

If I were teaching someone Python, or pretty much any programming language, the first place I would start is the debugger. I would have them write a program as simple as this: x = 1 print(x) y = 2 print(x, y) And then instead of just running it, I'd have them step through the code, line by line, and observe both the console output and the debugger variable display. Some developers seem to think that using a debugger is a sign of weakness, or that it leads you to write bad code. I see it differently: the debugger is one of the best tools not only for debugging, but also to help you understand a complex codebase that you are jumping into.

zikzak 4y ago
I end up helping developers when they get stuck all the time and it is really amazing to me how many people get to the "senior developer" point in their career with very little understanding of how to use SQL tracing (e.g. MS SQL server) and IDE debugging. Even the concept of the "print line" debugging into a lot file seems kind of foreign to them sometimes. They instead rely on running the code, changing something, running it again, etc. I am a big fan of reading through the code. That is almost always enough for me to find the issue and point it out to them assuming I understand the input and output context well enough. But if that doesn't work, add a debug point and fire it up. Not using a debugger seems like a massive waste of time in a situation like this. So much so that I have started asking "did you debug this" or "have you watched this happen in a debugger" before I will help out much. If they say "no" because they don't know how, I will teach them to do so.
- bornfreddy 4y ago
  > ...of how to use SQL tracing (e.g. MS SQL server)... Never met this term before - IIUC, SQL tracing is MS-specific? If I may ask, in what kind of situations would you use it?
  - zikzak 4y ago
    Yes, I think it might be SQL specific but you can normally do this in any transnational db I have worked with (I am old, I don't use GraphQL or NoSQL dbs very often, if at all). Basically, it is just a journal of all queries (really ANYTHING going on in the db but for developers it is useful to limit to queries) and typically filtered by database and by keyword (e.g. table or stored procedure name). You can set up a trace to track long-running queries on a production server (DBA might do this) or on a dev server a developer might use it to capture SQL run from their code (e.g. a complex stored procedure with a lot of input params) so you don't have to try to assemble the SQL using a debugger, for example. A good example might be "I am doing everything right in code, but the data set is coming back empty" so you profile it and realize the SQL is being called with an empty string and not a null, or whatever. When reviewing the code you thought "it will be a null". That kind of thing.