Pittsburgh's community for passionate coders. Videos for people interested in computer programming. We build software with Ruby, Python, Elixir, Clojure, Rust, JavaScript, Swift, and more.
Really appreciate this talk, thank you for posting it. As someone with reduced ability to hear the large jumps in volume make this very challenging to listen to. I hope future videos avoid this because Im a big fan of all you guys do.
Correction: Positive amounts are debits. Negative amounts are credits. Whether or not such amounts increase or decrease an account balance depends on the type of account. You’ve known it for years already, just by other names. Remember your basic algebra classes where you learned what was done to one side of the equation was also done to the other. Well, the bookkeeping world has fancy names for the left side and right side of the accounting equation. The left side means debit. The right side means credit. That’s it! You also learned in algebra about formulas and variables. You understood what the variables meant and which formula to use, you plugged in numbers and solved the equation. Well, know the accounting equation! Assets = Liabilities + Equity Equity = Owner Contributions - Owner Withdrawals + Net Income Net Income = Revenue + Gains - Expenses - Losses. If you prefer to think like a computer does when using accounting software, like any plain text accounting, let’s say, the formula is rearranged so that all debits are positive amounts and all credits are negative amounts. Assets - Liabilities - Equity = 0 Equity = Owner Withdrawals - Owner Contributions - Net Income Net Income = Expenses + Losses - Revenue - Gains
This whole talk boils down to: I'm most comfortable with Python, so I'm going to use Python for everything. Otherwise stated: Everything looks like a nail if you're holding a hammer. Imo, everything has it's place, including Bash, and not just for 2-line scripts. It can be a great way to quickly get to a full working prototype before moving onto Python, Node, or whatever else you are comfortable with. Python, Node, and other programming languages essentially just add more surface area (more data structures, modulation, etc.) to your code which makes it easier to do more things. Beyond that, if you need to optimize for performance, you can consider languages that add surface area for optimization like C, Rust, etc. The problem is that the more surface area you are dealing with the more difficult it is to prototype. Sometimes a prototype is all you really need, so you can avoid over-engineering in this regard. Having the ability to unit test without even truly knowing what the problem is is pointless. Having at least a bad yet working solution, like one written in Bash, as a reference will allow you to focus on writing good tests and following good practices in your language of choice instead of trying to do all that whilst figuring out what the actual problem is to begin with. Since Bash is effectively the Linux and MacOS CLI, it will always be the fastest prototyping language for these systems. Bash is not "fake" programming. Using sed is like using regex in any other language. Re-use of other peoples code is not "fake". It's the norm. Production code usually depends on loads of 3rd party dependencies. Your runtime with it's builtin modules is also reuse of code. There is no such thing as "fake" programming. If there was then you'd better start writing everything in machine code instructions. Why not build your own CPU architecture while you are at it? What Bash does for you when you learn it is that it gives you an intuition for dealing with file systems, streams, parallization and comfortability with the OS in general, which cannot be said for any other language.
your whole argument about surface area isn't wrong but its essentially just a restatement of the "too much code" whine which he does address in the talk python is already braindead easy to use so theres not much to be won from prototyping something in bash and then porting to python
The talk is amazing.. but I have a VERY BIG ISSUE.. with the presentation of the talk on Debit and Credit... where he says Positive Number is Credit, Negative Number is Credit... and the example used is completely misleading (or i could be wrong??!)... See 27:33 where Coffee 3.00 (positive) he says is Credit Expense.. and -3.00 (negative) he says Debit Expense.. This (for me) is totall wrong!!!! You Debit Expense and Credit Asset when you are spending in Accounting.... thus it should really POSITIVE NUMBER is DEBIT.. and NEGATIVE NUMBER Is CREDIT. No one seems to raise issue on this. So, is it only me? I really feel the speaker has got it wrong. Also, see his screen at 25:23 (where credit and debit is wrongly stated for positive and negative respectively) @code&supply
I think you might have a point, I think he mixed credit/debit up. When he buys the coffee his cash assets account goes down, and his expenses account goes up. Debit is money going into an account, credit is money going out of an account. So he credits his cash account, debits his expenses account. Yeah he has his words muddled.
Speaker here. Don't know how I missed these comments until now, years later! Sorry about that. I think I got things reversed in my speaker notes at some point and it stuck. I haven't given this talk in a few years but I've made a note to go back through it before I would give it again to correct the error. Thanks for watching and thank you especially for commenting constructively!
28:40 "I don't know why anybody would run on anything else than ZFS" Me neither. Being using it to store my data and backups since 2008. I was able to detect a controller issue, and later a bad connection/cable thanks to the scrubs.
hello the video was soo good , i just did a drone with pixhawk flight controller, so i just want the information about how much current and voltage is used by the 4 esc and the 4 motors and the whole pdb connected to a battery so how can we calculate it so i can estimate my flight time using a 3300 mah battery.
May i suggest design a solenoid lock on the gyroscope, or maybe logicrythmic function to set base 'zero' recalibration when velocity of angular momentum is reduced within a nominal range of noise?
I blame the Google eggheads for all of this. They have never designed a great tech product. Their last good product, search, hasn't worked well in over a decade. Angular, GAE and Golang are all a failure. I personally have had investors privately tell me it has become totally unreasonable.
My success rate on live coding is only about 50% and I have been coding 38 years. Since age eight. I wanted to see how well I would do. Many times... the test have errors in them. Live coding is a complete waste of time. Just ask for a code sample and be ready to explain it.
Interesting angles on the interview process so I would wonder what an ideal technical interview process would be based on this feedback. I wish that had been covered also. I understand that I can infer what this could be. By understanding the don'ts, I can work towards to the do's. However leaving things to interpretation might not be the best approach. So yeah...end or rant.
I love the work Jon has been doing. I saw him at Midwest UX 2019. It is an interesting question on what our responsibilities are as marketing and technology professionals.
Heya! The laparoscopic surgery was the appendectomy; as I explained, the Meckel's stones were found in an exploratory laparotomy -- which is a large incision, not a small one. They are not done frequently -- for good reason! ;)
Thank you so much Judy for the wonderful talk. Worth spending 1 hour to understand the application of Data Science in the Airline Industry and the challenges in implementation. It's the high time for Airlines to evaluate the impact of unpredictable/uncontrollable factors such as Pandemic and adjust all the ML models to fill up the gap in revenue in upcoming years.
First get lot questions/strings that contain basic entity information, train it with ner definitions, If required change. Prodigy and transfer learning is very easy though. Then you can simply build your application on top of these. The entity recognized can be returned raw manipulated as per your desires when questioned.
If you do a presentation on the final results, please move the speaker view window to a place on the screen where its not blocking any info. Thanks! Looking forward to the final report.
