phillipwills

Working on a similar thing that uses toml to define pages... But closed source, for now...

I like toml because it's easy to read and write as a human, even without text editor help...

This, 100%. I wrote about this exact thing a while ago. In my opinion, it's how developers truly get to 10x.

https://got.phillipwills.com/10x-as-an-individual-contributo...

Try to start contributing to some open-source projects, if you don't mind working for free. It will help you to start working with others, more. Not necessarily next to others, but checking into the same codebase as others, and getting your code reviewed. Even reviewing others code.

Pretty sure they do this by taking over the domain... Not sure if that would work in this case...

But it does reduce the cost of research and development coming out of the company's pocket. That said, in a capitalist society, the production price helps to set where companies will stop making it.

The price is actually set to where profit is highest, meaning it's a function of: how many people will buy at various prices and how much does it cost to produce at various quantities.

One of the strong arguments for single payer healthcare, IMHO.

I used the aws sdk to write a simple NodeJS script to pull logs for a date range, then I can grep the output...

We have a 2 story house where the bottom story is a daylight basement. When it gets hot, it usually stays pretty cool downstairs, so we hang down there during the day. In the evening, as soon as it's cooler outside than upstairs inside, we open the back door, both downstairs and upstairs, and turn on a high powered fan blowing air up the stairs... It is really effective at cooling the house.

Always assume any communication on your work network can and will be monitored... If you want a private discussion, best to do it in person or on your own devices, not using any company resources.

I don't know... There's a lot that's not being said in that article... As is the case in all articles about court cases... Or court cases, in general. I feel a very real, "burn the witch" attitude when it comes to hackers and coders mixing with the justice system...

- Attention! Installing cmus-osx will prevent you from opening iTunes until it is uninstalled!

This sounds like reason enough to install...

Pretty sure you can edit a lot of these session settings in putty while it is running. It's in the menu, I think (been a while since I used putty).

I've posted random ~. in irc because I did it in the wrong order...

Or worse, I spent 1 hour writing it, so 15 minutes refactoring... And done, no more refactoring...

Notably, not by the hacker... Accidentally aired in Spain...

Been using Firefox mobile for a while now with uBlock Origin... Creating rules to hide annoying elements on sites that I use a lot.

Most times when I try to browse pages on a family members phone I want to throw it... Guess I really don't know how bad things are most of the time.

I'm usually just bitching about the sites that are sniffing for webkit UA's and therefore don't show me a mobile experience.

Nice... Didn't Google before posting... Busted. :)

Also, XP was released in 2002, so it should work rather well on the previous year's hardware...

chmod is that way because ambiguity... -r is take away read...

Shouldn't have any effect... Long time vim user... I still do it all the time. Especially when returning to the terminal from another app.

I also mapped jj and kk (and other direction combos) to esc for when I forget to hit escape...

Even when that does happen... and I'd argue that it often does not, if you've done the work to make your interface pretty, and write a precise, accurate test suite, you've usually done the work to make the actual functions neat and orderly...

Even when you end up with a black box full of entropy, it's segregated from the rest of the system. You can feel free to change the rest of the system around it and know that the black box will keep doing it's job, as long as you keep using the well-written API within spec.

But, that's not all you get... because you took the time to write the tests, you can refactor this entropy box to your heart's content... until it starts looking more approachable. You've got your tests around the API, right? Then you don't even really need to change them to do the refactor work. The only reason to change the tests would be if you want the function to do something else (or you missed something, of course).

Take small steps... refactor out a couple lines at a time... run the tests with each iteration. Based on previous experience, you're going to end up with a fairly clear and concise implementation... not to mention performant.

I wouldn't say that this article is describing a correct way to do things. It's more of a set of guidelines to follow, and I'm glad someone wrote them down.

I've been doing these things, but I generally have a hard time concisely describing it. Of course, these aren't hard and fast rules. More of a guide to thinking about problems to help programmers be more efficient and accurate... More precise...

I don't really know how to describe it, but one day, you find yourself doing these things more... Stuff gets easier... Things just start to click.

I'd like to add one more, though maybe it's really just another way of putting one of the other statements.

Stop worrying about all the unknowns in the project. Work on what's known, usually the unknowns will become more clear as you progress.

That's the thing, right? Most of us have plenty of bandwidth and storage space and everything we need to host a site sitting in our living room. It's still too complicated for most people, though. It should already be as easy as Facebook...

This site crashes Firefox mobile after being open for a few minutes... Sad...

I feel like I shouldn't be testing that the dependencies' api's didn't change, that's for integration tests, which don't need to run as often as unit tests. Therefore, they can be slower and more complex. Mock or spy everything external and nothing internal.

It can feel a little dangerous, but as long as the integration and e2e tests are kept up and run on build, i think I'm covered. I've definitely been bitten before, but I've been bitten more by over complicated and long running tests.

I try to keep my unit tests focused on the api of the unit I'm developing. If I'm refactoring and keeping the api the same, I shouldn't have to change any tests. Since I started writing my tests this way, I've felt I have to change my tests far less... Sometimes I add more tests, when a bug is found and needs fixing, but missed tests are better than wrong tests IMHO.

Just because you don't understand the JavaScript this, doesn't mean it's broken. It behaves exactly the same way every time you use it... It refers to the object that called the function (unless, of course you or someone else overrode it).

With casual speaking, you place emphasis and pauses, naturally... With writing, nobody can read your body language... hear your pauses... notice your _emphasis_... unless you s.p.e.l.l. it out...

Quickly check crontabs for all users on your systems:

cat /etc/passwd | cut -f1 -d":" | while read line ; do sudo crontab -u $line -l ; done

There's a magic font-size that prevents this... I think it was around 19px, but I'm not sure...