HNHacker News
TopNewBestAskShowJobs

jskulski

170 karma · joined September 28, 2011

submissionscomments
jskulski··on I need structure in my life
Rituals can be important. I recently worked on a mostly daily exercise routine and it's life changing. I'm now focusing on a monthly/weekly/daily planning. If I try to even do two habits, I have much lower results.

Counterintuitively, there's requirements to have more slack time. It's has to be dedicated and active. I need time to waste. I just need that time to be intentional, timed and shamefree. One trick, I use is to set a timer, get myself a glass of water, and then turn down the bed like a hotel before a Movie.

jskulski··on Multitasking, something we copied from computers
This level of parallelism feels more like my brain is abstracting two tasks into one. It takes a little practice and then you gain that ability
jskulski··on Ask HN: What Is the Lisp “Enlightment”?
That was a great read, thanks for posting. Looking forward to sharing.
jskulski··on REPL Driven Design
Bob Martin is myopic in his view of software, in a way that I think is harmful to teams and the industry.

It is my experience that good software comes from teams working together well, teams that are in some sort of harmony with each other AND the system they are building/using. They understand it and each other. Good software is not derived from a singular technique.

I do like test-first approaches when I can, I like SOLID. I probably agree with Bob on a lot, actually. I think they are good techniques to employ.

However, it has not been uncommon in my career to find people (and myself) getting dogmatic about these things and arguing over them. There are half baked attempts to change everything to an Entity. There are flaky test suites with a lot of mocks because someone is hot on TDD, but does not have the bandwidth to maintain the suite for the whole team.

This blogicle is another example. As pointed out by other posters, REPL driven development can fold VERY well into a test driven workflow. However, that's not enough, he's actively saying it's not as good and you need to do The One True technique.

jskulski··on Joe Armstrong Obituary
Oh. I hadn't seen that he had died.

Rest in peace, Joe. I was just getting to know your work, but thanks for doing it.

jskulski··on The Now Habit (2015)
Sounds similar to the ones I've read. Good points, little else, repeated with anecdotes to substantiate the points. I like summaries of these.
jskulski··on Nnn – a terminal file manager for programmers
What is sunrise mode? Are you referring to https://www.emacswiki.org/emacs/Sunrise_Commander ?
jskulski··on Leo Editor
Has anyone used this, org-mode or other literate programming tools for a full team project at scale (whatever that means, non-trivial multiple months, lots of code)? Did the team have to buy in or were they already users? How did it go- did it improve.

I've used org-mode for about a year and a half and have found it helpful to to my productivity and feeling put together. I can see the potential for benefits to a team, but not many people want to learn emacs for a job if they don't already use it.

jskulski··on Ask HN: What you wish you'd known before getting into JavaScript?
For context:

- 2003, I needed to learn JS to move into a professional web developer position (from systems eng). I started with mootools/dojo/yui and jquery, when it came out in 2006.

- 2009, apps started to get very complex and hard to maintain. Or I got experienced enough to figure there'd be a better way so I started working with backbone, (some) emberjs, and (a little) angular.

- During this time, I also built a number of native javascript apps because frameworks and tooling were eating up a lot of my time. I also wanted to understand the language.

- Eventually, I found elm because I started getting interested in type systems. I _really_ liked elm but it was a hard business case to make for a team. I settled into redux/react these last few years because it gets pretty close.

- The first project I 'did in' redux/react' was actually just plain javascript. I naively implemented the react and redux api and patterns. This was _incredibly_ helpful. Not only did I quickly gain a fuller understanding of the tools I was about to use, I started to understand the muddier parts of JS: the event loop, async, hoisting, scoping, etc. I was aware of them before this, but I kinda just fiddled til things work. Afterwards, I knew what the computer was doing.

So, to answer you question 'what do I wish I'd known':

I wish I knew how much of JS is choosing a platform/toolset. I also wish I knew that that tool choice is just the start and doesn't guarentee anything. You can write a clear and easy to work codebase with JQuery. You can also make a hard as heck piece of junk in react.

I would suggest not too get hung up on it. It can be hard/impossible to choose the right tool if you don't have experience with the tooling or the problem.

So, get ready to jump around. I would get ready to pick a tool for a few months, then move onto another one. In my experience, there is not a great answer for questions like 'what is better, vue or react?' The answer is subjective, a choice that reflects personal and team preferences. You can be productive in both, so it's more about sticking to one.

JS, like every other software project, still benefits from core engineering principles: - team dynamic and trust are !important! a framework will not help if a team member feels they are not trusted/growing/learning/producing - prioritize readability, code is read more than it is written, - prioritize simplicity, break complicated stuff into small, composable pieces - with all due respect to the thousand of work hours put into webpack, it is still a pain in the butt ;)

Good luck!

jskulski··on Show HN: IsServiceUp – Monitor the status of all your cloud services in one page
Very cool!

I did a similar project a few months ago! One day after lunch people were starting to run around saying our system was down. I checked a few of our dependencies and realized it was out of our hands. (Still our problem, but nothing we could fix, only mitigate).

So Snu was born, take a look! Looks like we had a similar itch!

https://github.com/jskulski/snu

jskulski··on Announcing TypeScript 2.0
A bit off-topic, but I'm curious what your experience with Smalltalk was professionally.

I've always viewed it with rose color glasses. It looks like a wonderful environment to work in, but I'm sure I'm missing something. It seems like Smalltalk was lightyears ahead with it's tooling.

What do you work in now, do you find lack of tooling to be challenging?

jskulski··on To tell someone they're wrong, first tell them how they're right
I agree, insincere flattery (maybe even condescension?) will be read and figured out.

To me, this is sort of inline with How to Win Friends and Influence People. Taken at face value and just following the motions will be ineffectual at best, offensive at worst.

I do think there is value to be gained, like with HTWFIP, that if done sincerely I very valuable for both sides. If I actually have to understand your view, that opens my mind.

jskulski··on Visual Studio Code 1.5
It was for many years (because the others didn't exist)
jskulski··on Ask HN: Best daily practices u've come across to design-code faster and better
I try to setup a feedback loop as soon as possible. I spend time setting up so i can do some simple action (hit a button, run a command, or automatically watch some files) to see if I'm on target it.

I found this saves immense time and keeps me on task pretty well.

This is from: - GOOS book https://www.amazon.com/Growing-Object-Oriented-Software-Guid... - https://www.youtube.com/watch?v=nIonZ6-4nuU

jskulski··on Giving Up on TDD
> This mindset fails to take into consideration the fact that tightly coupled things are often simpler to understand and reason about

You're right on a small scale. With teams or feature changes, tightly coupled things quickly breed incidental complexity.

I like what you said about decoupling not being unqualified positive. It's not, it's very good, but it's costly (with a high return). It's all about trade offs. Testing, and specifically testing-first, is expensive compared.

If I'm working on a critical piece of my system? Yep, worth it. TDD. Do I need to refactor something so I can reduce complexity with this change? TDD. Am I writing a quick workaround for better UX that will be removed after two days? TDD isn't appropriate.

It's a essential skill to have, but not the only way to practice.

jskulski··on Ask HN: What is your trusted system for GTD?
Everyday, I write things down and then I do them and then I cross them off. It's really hard.
jskulski··on A website for testing your app ideas
"Elevtr IO is an app for testing your minimum viable product or supporting ideas you like."

A MVP isn't a description of something that doesn't exist. An MVP is the cheapest way to get value to your users. Interesting idea for a site, but I wish they wouldn't use the phrase MVP.

jskulski··on Conceptual Debt Is Worse Than Technical Debt
Exactly. The important part of these phrases aren't Technical or Conceptual, it's the 'Debt' part.
jskulski··on DHH on the immediacy of PHP (2008)
This also leads to the rise of single tons and creating objects wherever you need them. It's hard to grok Dependency Injection when your objects live and die all the time.

It makes reasoning about state easy because you don't have to consider it. In my experience (which involves several large and mature PHP codebases), that's not a good thing.

You're right about the benefits, but the downsides are glaring too.

jskulski··on React/JavaScript fatigue
Exactly. My experience with JS (which is entering non-trivial amounts) has been this:

Either get a boilerplate, generator or spend frustrating afternoons configuring to the start line. Then once you start work spend hours reading docs to figure out what all that stuff you installed actually does.

OR

Build from scratch, build the simple stuff, then when your brain says 'hey someone must of done this', look for a library and plug it in. Then at least you understand a general idea of what you're installing.

An over simplification, of course, but building rudimentary routers, event managers, mvc structures etc helped me immensely.

jskulski··on Mind-wandering: the rise of a new anti-mindfulness movement
It's referred to as the monkey-mind.

https://en.wikipedia.org/wiki/Mind_monkey

Zen is where I encountered it.

jskulski··on Mind-wandering: the rise of a new anti-mindfulness movement
I'm a big fan of day dreaming, and set apart time in my day for it. I guess mind-wandering is the new term.

But I think the article is protecting the very stressful cycle of thinking about the same things over and over and over without being able to let go. The old

"I should go to grocery store to get food" leading to "I should cook more at home" to "That one time I tried to make tikka masala it came out bad" back to "I should go to the store"

cycle.

I'm all for the embracing of day-dreaming, but that comes from mindfulness. A calm, clear place where thoughts are free to bubble up as freely as they are able to go.

Mindfulness meditation practice is, for me, the gym. It helps me put my mind to that place, to focus and put 100% into whatever I'm doing, whether that's chopping carrots, programming, or day-dreaming.

jskulski··on The End of Dynamic Languages
def some_function(some_obj): ...

How does any IDE or editor know what some_function would be passed without a severe amount of inspection?

I might be wrong on my definitions, but almost by definition, there's just not enough information before runtime in dynamic systems to infer enough to do any real refactoring or smart completion.

I use PyCharm everyday, and I like it, but it's refactor menu is limited, can fail, and pales in comparison to my uses of java w/ IntelliJ or even a well hinted php app w/ PHPstorm.

jskulski··on The End of Dynamic Languages
I think the main point is that its very convenient to the IDE/developer, not for the performance. You know what things are before runtime. You can explore and have discoverable APIs much easier.

Most dynamic languages I've used in my career (javascript, python, php) have either metadata to typehint, a hinted superset of the language or new language support for typing.

jskulski··on Writing code doesn't mix well with oration
Live coding doesn't mean a poor presentation. Thought bad live coding generally does. I don't want to see someone stumble around, but Jim Weirich's live coding of katas turned me on to a lot. Not only katas, ruby, but how he coded- refactor menus, etc. Extremely valuable.

https://www.youtube.com/watch?v=WBJ3hdcM7G8

jskulski··on Writing code doesn't mix well with oration
Thanks for the video, looks interesting.
jskulski··on Stripe – Outage postmortem
Agreed. It looks like this was caused not because the application developer or DBA caused an error, but because the system didn't allow for ticket dependencies.
jskulski··on Why I wouldn’t use Rails for a new company
I've worked in PHP since 2000 or so.

It's amazing what it's turned into. That said it's still very painful and the ecosystem has a very long way to go in terms of build tools, etc etc.

I bet there's a lot of money to be made in being able to turn old legacy php codebases into nice well factored systems in the next few years.

jskulski··on Why I wouldn’t use Rails for a new company
Talent that comes in because a stack is hot/trendy are there by virtue that they lack the experience to know it's nothing knew. They haven't seen other hot/trendy stacks fail yet.

Meaning they probably also lack experience to make decisions that avoid turning greenfields into a muddy hell. No thanks.

jskulski··on Ramda-cli, a jq-like CLI tool for processing data with functional pipelines
From the js perspective you use it all over the place so it's nice to have a one letter name:

var my_sort = R.compose(R.first, R.sort, R.prop('id'))

← PreviousPage 2 of 3Next →