Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
engineerDave
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
31.
▲
by
engineerDave
5y ago
If you have a good framework behind your project, e.g. Rails, Phoenix. You probably don't need it. I'm a primarily a ruby/Rails developer who is slowly switching to Elixir/Phoenix, and I find myself reaching for React wh
32.
▲
by
engineerDave
5y ago
Greenfield coding projects are very rare, except in consultancy, but even there you'll have to maintain what you build. Refactoring however can be the same type of thing. IMO use this opportunity to write tests and learn to refactor. M
33.
▲
by
engineerDave
5y ago
internet 1.0, post AOL, pre dot com crash. You had to roll everything and could even run a server with little fanfare from your home because ISPs allowed you to run your own servers. Now most prohibit or outright block it without a higher t
34.
▲
by
engineerDave
5y ago
I would bet the angle is that programmers in their 20s are less likely to push back against things like on working conditions and demands on their time. Basically get them while they’re young and dumb
35.
▲
by
engineerDave
5y ago
All banks AFAIk not just EU banks.
36.
▲
by
engineerDave
5y ago
The problem as I've experienced it is they hire you based on the code example from the interview and then the actual job requires you to know all the orchestration components (puppet, chef, kubernetes, package manager and system settin
37.
▲
by
engineerDave
5y ago
They're his words not mine. Go fight with him if you think otherwise https://www.youtube.com/watch?v=Of1phFsC4ZI&t=3290s
38.
▲
by
engineerDave
5y ago
When I say copy I don't mean implementation but inspiration. They may not have copied it exactly in implementation, it is FP vs OO, but stimulus.js was a direct response to LiveView. I don't think there is anything wrong with that
39.
▲
by
engineerDave
5y ago
Not a knock on you but maybe you're too new to Rails too. I've been using Rails for 10+ years now and setting up a phoenix app is very intuitive. A lot of "oh this is like X in Rails". IME most of the complexity was arou
40.
▲
by
engineerDave
5y ago
This is the correct answer.
41.
▲
by
engineerDave
5y ago
Elixir Phoenix. It’s what rails copied for the Hotwire stuff. With distillery you can compile all of it, css, js, images, html, down to one tarball that you unpack and run as a service placed behind a forward proxy for complex setups or sta
42.
▲
by
engineerDave
5y ago
Not trolling. Since others have handled the H1-B visa stuff, I'll just say your first sentence tells you the exact problem. > I'm a 20 y/o bootcamp grad with no college degree and 6 months of professional experience Six mo
43.
▲
by
engineerDave
5y ago
this x1000. My main frustration with imperative programming has become the devops plumbing and defensive nature in code that was needed to get something done. Switching to Elixir - learning what OTP brings to the table, e.g. observers, gen
44.
▲
by
engineerDave
10y ago
I was being tongue in cheek on that one, sorry if it didn't come across that way. Although I've been a Rails dev for 6 years now, I've come to hate the TDD approach and am a convert of FP and types, & compilers a la Haske
45.
▲
by
engineerDave
10y ago
true but even staying current across small SemVer changes can be a relatively large burden
46.
▲
by
engineerDave
10y ago
I think your memory of the 2 -> 2.1 -> 2.2 -> 2.3 (if you were lucky to get bundler running) to 3 to almost immediate 3.1 with massive changes (asset pipeline) upgrade is a little fuzzy. It was the suck. A lot of companies I know o
47.
▲
by
engineerDave
10y ago
Yes. Being forced to push changes to production with zero test coverage, and hence zero confidence in your code on a Friday night. (true story) After that you always make sure test exist before even pondering a push of potentially breaking
48.
▲
by
engineerDave
10y ago
Fair points all. But the breaking changes I'm referring to are items like changing method names, most likely because OCD, and helper methods, etc. While good/great tests will catch this type of stuff in your code, it will still be
49.
▲
by
engineerDave
10y ago
In cases like this when I ask why TDD isn't done the answer is usually some variant of "its working" to which I usually reply "how do you know?". :P
50.
▲
by
engineerDave
10y ago
The main problem I see in the ruby community, in this regard, is the willingness to make breaking changes and justify it via Semantic Versioning. While on the surface this seems ok the underlying problem, as I see it, is the old version isn
51.
▲
by
engineerDave
11y ago
LOL using the root of the word you're looking up to define the word you're looking up, classic!
52.
▲
by
engineerDave
12y ago
here is a podcast where they cite error handling stats of C++ vs Erlang. http://mostlyerlang.com/2014/11/19/049-supervisors/ starting at 28:45 although you might want to listen to the whole podcast
53.
▲
by
engineerDave
12y ago
We also don't have police helicopters here in Madison at least to the best of my knowledge
54.
▲
by
engineerDave
12y ago
FWIW He wasn't really in the bush. He was in a suburb of Madison called Middletown where there are corn fields on the outskirts of residential neighborhoods and the weather was fairly mild last weekend. Low humidity and 80ish F.
55.
▲
by
engineerDave
12y ago
When I read this I couldn't help but think it emphasizes the core problem with creation waste, meetings and communication lag, e.g. time between emails, IMs. I think we can all learn from that part.
56.
▲
by
engineerDave
13y ago
That might be the best pro Scala (your "Why Scala?" blurb) statement I've heard yet. :)