Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Tommabeeng
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
Tommabeeng
3y ago
Dune was a 165M movie.
2.
▲
by
Tommabeeng
3y ago
Even beyond Dogme 95, the 90s were such a great moment for independent and low-budget films. And this was before the epoch of 24P and digital! So indie and very low budget films should be much cheaper to make today than in that era of film.
3.
▲
by
Tommabeeng
4y ago
Super excited about this. I've been using cljfx ( https://github.com/cljfx/cljfx ) to build a few apps and it's so developer efficient.
4.
▲
by
Tommabeeng
5y ago
Decoupling
5.
▲
by
Tommabeeng
5y ago
I find this such a shame. I think this reflects an increasingly consumer versus producer aspect of culture. I find that desktop apps support and foster creativity, and producing readily manipulable creative artifacts - with speed. Sass/
6.
▲
by
Tommabeeng
5y ago
I've made a few desktop apps in https://github.com/cljfx/cljfx (e.g., https://www.chronos-desk.com/ ), and cljfx (JavaFX + Clojure) is amazing and makes for rapid development, not to mention fun. I
7.
▲
by
Tommabeeng
5y ago
This is incredible. I’ve got two JavaFX apps to try this out with this week. Figuring out Mac codesigning for JavaFX apps was a pita.
8.
▲
by
Tommabeeng
5y ago
In prior talk(s) he’s famous for saying “IQ is a lead weight”.
9.
▲
Visualize a Stack Trace in Java
(jmolly.com)
3 points
by
Tommabeeng
14y ago
|
0 comments
10.
▲
Tracing and Drawing Hello World in Java
(jmolly.com)
3 points
by
Tommabeeng
14y ago
|
0 comments
11.
▲
by
Tommabeeng
15y ago
He does say about coupling & cohesion that "if used, they are pulling a fast one on you". That's wrong. I like the key to his talk but the plague of large complicated systems is exactly coupling and incoherence. Classes are NOT necessar
12.
▲
by
Tommabeeng
15y ago
Alan Kay expresses something similar: http://tele-task.de/archive/video/flash/14029/ "Knowledge is silver. Outlook is gold. IQ is a lead weight." (~00:30)
13.
▲
by
Tommabeeng
15y ago
"Improving the productivity of a software team is hard. It involves understanding the business, the team, the history, the obstacles blocking progress. It is a complex, context-sensitive problem." TRUE. Hiring more devs won't solve the comp
14.
▲
by
Tommabeeng
15y ago
It should be noted that code reviews, though useful for catching defects, are incredibly expensive. I think there are cheaper ways -- along the lines of automated testing and design reviews in lieu of code reviews -- to reduce risk and de
15.
▲
Toward a Criteria For Interviewing Software Developers
(jmolly.com)
1 points
by
Tommabeeng
15y ago
|
0 comments
16.
▲
Must You Really Search Your Code?
(jmolly.com)
8 points
by
Tommabeeng
15y ago
|
0 comments
17.
▲
by
Tommabeeng
15y ago
This is meandering rambling from someone who doesn't know how to write unit tests. He complains about bad unit tests ("many tests tend to...") as an argument against unit testing. Yes, there are bad tests out there. But there is a way to wr
18.
▲
by
Tommabeeng
15y ago
I like this. "The only weapons we have are simplicity and convention." Well said. I think we need to espouse a new software paradigm: DFS-oriented programming. (Dead F *ing Simple-oriented programming.)
19.
▲
by
Tommabeeng
15y ago
Layers of indirection (abstractions) aren't bad; bad abstractions are bad. A good abstraction should protect you from having to keep lots of implementation details in your head. And C and arrays are not the epitome of simplicity. An array i
20.
▲
by
Tommabeeng
15y ago
no, for just pandas
21.
▲
by
Tommabeeng
15y ago
glamour photos for pets
22.
▲
by
Tommabeeng
15y ago
Would a rewrite necessarily benefit the business? Can you make a strong case for that? If not, start writing tests, try small incremental refactorings, ask your manager to hire more people, maybe someone not as qualified as you but that can