|
It depends on the laptop, most newer laptops have very good trackpads (the bigger multitouch trackpads).
I don't use a mouse with my laptop, I've configured 2-finger-taps to middle click, 3-finger-taps to right click which is really helpful.
Also in VS I've configured F1 = goto definition, shft+F1 = all references (ctrl+. and ctrl+, are really helpful keys also [try them out])
The only time I need a mouse is for fine grained form/picture positioning/editing which is much easier with a mouse.
|
|
|
|
|
Thanks for some very good tips! I've taken notes and will try some of them out next week. I'm off to a labor day college football game and am leaving the laptop behind!
"Go forth into the source" - Neal Morse
|
|
|
|
|
I'll be in a plane on my way to Estonia
Staying in Estonia for a week and then I'm off for a few days of Saint Petersburg before coming back home.
Coming back on a Thursday and starting work again on Monday.
Vacation be good
|
|
|
|
|
Wishing you a very happy vacation ! cheers, Bill
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
|
|
|
|
|
Thanks Bill
|
|
|
|
|
I've been to both places and loved each of them
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
have a great time - I'd love to see St Petersburg .. I didnt think it was the sort of place one casually flew to though - visa requirements etc
|
|
|
|
|
Thanks!
Garth J Lancaster wrote: I didnt think it was the sort of place one casually flew to though Yeah, we'll be staying there for three days and I think that's also about the time it took to get allowance for entering Russia
|
|
|
|
|
|
I'll remember his lessons...
|
|
|
|
|
Had a simple audio edition task, and of course, used Audacity[^].
This piece of software has been constantly amazing in at least the last decade. Easy, lightweight, intuitive. I had my editing done in no less than 2 minutes. Awesome.
|
|
|
|
|
I know what you mean - good kit!
Now, if only there was the same for video - I have about eight different tools for that, each of which is good at one thing and weaker at the rest. And none of them work the same way, and some of them won;t work with this format, or that size, or won't output the other, ...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
The gopro studio is good and easy to work with, but very, very limited with the file formats...
I also use windows movie maker and I have used adobe premiere to some extend. But indeed 1 good tool, I have not found yet.
|
|
|
|
|
I find it just a little ironic that we have programmers complaining that there's no decent software available for a given task.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I was not complaining, I just wanted to say that the programmers really did a good job there.
As for programming SW that I need, well, even if I think I am a decent programmer, it would have taken me at least two months to programm a draft of something like audacity vs. 2 minutes with using it. So...
|
|
|
|
|
I use it to sample the cassette tapes from my old computer. Then I run a program over the samples and reconstruct the original binary data. It works even with tapes that don't load anymore.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
|
I can even write new programs comfortably on the PC and then generate a WAV file from binary which can be played to and loaded by the old computer.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Audacity is amazing! I use it for compression, removal of pre/post recording noise, fade in/out and ducking of raw tracks that I've record on my multi-track recorder. I then bring the Audacity processed files back to my recorder for mixing, effects and mastering. Here's[^] one result - if you're into classic rock.
/ravi
|
|
|
|
|
For me, Audacity is the best software when it comes to audio making, editing etc. Been using it for years and it has every feature that I need.
|
|
|
|
|
What are your tips for showcasing Back-End Dev. work? Especially work where I only did the back-end. Front-End is easy: You just show them the website or photos of it, which illustrate the UX/Photo/CSS/HTML work... However, with me doing BACK-END dev, the site can look like ass but my work is actually quality work (making it more secure, faster performance, scaled, designing the DB, etc...) because I only did the back-end of things...
Not to mention, clients who view my LinkedIn and other Portfolios may not understand or want to understand the actual coding part. Front-End appears at first to lend itself to easier marketing techniques due to this, but I am sure there are workarounds for this that I haven't thought of. I am open to suggestions! Thanks!
|
|
|
|
|
If you are able to, throw the work on github. Then in the readme file on github write a high level outline of what the code itself is/does that is fancy with little snippets and why it is quality code/what the current "normal" way of achieving the functionality you've implemented on the backend is, then why the way you went about it is better.
This way those that want to dig into your repository and see all of your code can do so while others who are satisfied with the readme don't have to figure out why your backend code is fancy.
|
|
|
|
|
TheOnlyRealTodd wrote: Front-End is easy: You just show them the website or photos of it, which illustrate the UX/Photo/CSS/HTML work... Unless you're in the medical industry and it's heavily regulated and they don't want screenshots available to the public.
Jeremy Falcon
|
|
|
|
|
Or the banking industry, which makes even getting the source onto github nigh impossible in the first place. One major bank (JPMC) won't even let employees reveal they work there.
|
|
|
|
|
Coming from the standpoint of someone who's given tech interviews... I'd agree with the github or equivalent thing. But rather than release your old company's IP to the wild, why not just build a side project to showcase your skills? Then during an interview just talk about your projects and also mention that if you haven't already. That would work for me.
Jeremy Falcon
|
|
|
|