Hacker News new | past | comments | ask | show | jobs | submit | lost_my_pwd's comments login

A few more more, depending on the nature of the project and one's goals:

  how do I report bugs
  how do I build from source
  how can I help/contribute


I think they are referring to this: https://www.urbandictionary.com/define.php?term=Soydev

Appears to be a derogatory term that, by diminishing the efforts and abilities of others, is used to make one feel better about one's self.


Long ago I was reading about Ernest Hemingway's approach to dealing with writer's block and one thing he said has stuck with me and proved quite successful for both "coder's block" and remembering where I left off from the last coding session:

  I always worked until I had something done and I always stopped when I knew what was going to happen next. That way I could be sure of going on the next day…


So glad you mentioned this! Back when I coded a lot more, I'd write a failing test with a note (e.g. "Fix date handling when converting from non-GMT timezones") letting me know where to pick up.

These days I keep a worklog for each day that I can flip through, and mark various items as TODO in the log. That allows me to track state over more days, which is useful when there are half a dozen projects to track.


I do the same. Additionally, I'll generally write an unexecutable bit of code where I left off. If I try to start again the program will error out on the line I left off on.


Yea, this is definitely the way. Stop at a logical stopping point. Leaving at the point where a task or sub-task is completed ensures the next time you come back there's a logical next step for you to begin.



Oh it can get even more ridiculous... yesterday I got yet another $300 bill for an ER visit from October 2017. Now I have figure out whether it will cost me more in lost billable hours than to just pay this bill, knowing that contacting my $1700/mo insurance company to help sort things out will prove to be fruitless.


Way down at the end of the page an "oh, by the way..." disclosure:

  After the program graduates pay 15% of their income for 2 years if they are earning over $40,000, capped at $30,000 total paid back to Modern Labor.
There is also the implication that a potential starting salary is $91,476:

  $91,476 The salary of an entry-level front-end developer (Source: PayScale, 2019)
Assuming that was somehow true...

  %15 * $92K * 2yr - ($2K/mo * 5mo) = $17.6K total cost of tuition
Looking around, ~$11.4K is the average tuition for a coding school, so this proposition works out to be a rather high interest loan (that can't be paid off early):

  $17.6K - $11.4K = $6.2K in interest
  $6.2K / $17.6K / 2yr = 17.6% APR


The important difference being that with this program, you don't pay if it doesn't work out for you. The 17.6% APR is in case of a success - they just helped start your career. Seems well worth the greatly reduced risk!


> The 17.6% APR is in case of a success

If making $40k/year is "success". With your $6k payment on the $40k you made, your $34k is barely above the poverty line.

> Seems well worth the greatly reduced risk!

No, it doesn't. Just seems like a 300% repayment rate. I bet the number of software jobs starting under $40k is in the bottom 5%, maybe 1% of job listings. So, you're basically only mitigating risk if you can't find a job.


> So, you're basically only mitigating risk if you can't find a job.

Which is.. everyone starting a bootcamp!! Lol.

Who are you looking out for? You seem really concerned about the biblical application of usury laws. Do you know anyone who has zero technical skill and would LOVE to make 40k? I have a feeling you live in a very, very small bubble.


Just because you think someone is so poor they should be grateful for a 3x loan doesn't make it legal or right. That's the definition of loansharking. It's been a pervasive problem that increases economic inequality because only the poorest would accept a loan with those steep terms. Just because it's related to something positive like teaching people to code doesn't make the 3x payback and less burdensome.

I'm not so worried about this company in particular, but if this business model works, imagine desparate people signing up for a $100k loan and having to pay back $300k, or getting $300k for a house and having to pay back $900k.

It's the payback rate that's the problem.

I also don't think it's a bad thing to be concerned about other people in our community.


(I didn't downvote you FWIW)

The difference here is that the incentives of workers and this company are aligned. Either workers start making some serious wages and the company gets their money back (with interest), or both lose - worker their time, company their investment. Given the risk I don't think this is even close to usury. In fact, I would assume they are getting paid by the companies too, for privilege of getting the suitable candidates (which is not a problem in my eyes, if true).

Edit: and if they ever move their operations to EU I know a few people who would probably grab such a chance with both hands.


i know a ton of people who would, as far as im aware the US is significantly cheaper than the UK in pretty much all areas, that $34k translates to about £25k which is not a bad basic wage. i imagine a lot of the people stacking shelves or cleaning toilets for minimum wage would much rather be coding for more money.


> If making $40k/year is "success". With your $6k payment on the $40k you made, your $34k is barely above the poverty line.

The poverty threshold in the US for a single person under the age of 65 seems to be $13,064[1].

[1] https://www2.census.gov/programs-surveys/cps/tables/time-ser...


It's also a high-risk lending operation, and high-risk lending naturally comes with high interest rates. Maybe someone takes 6 months to find a job, now the interest rate is under 7%.

I think that tying your own financial reward to the financial success of your graduates is perfectly OK, perhaps even desirable.


> Looking around, ~$11.4K is the average tuition for a coding school, so this proposition works out to be a rather high interest loan (that can't be paid off early)

You are paying extra in the hoped-for successful case in return for paying less if the whole thing turns out to be a bust. Or, equivalently, you are paying a lot extra for a portion of the tuition (which is, in fact, a straight $20,000—the $30,000 maximum minus the $10,000 stipend) to be due over time after completion, repaid on an income contingent basis, and foregone in part or in whole if after-program income isn't at least $200K over two years.


But that does not need to be paid if you do not get a well-paying job after it


I would not call $40k/year a well-paying software job.


Sure, but a loan you don't repay unless you get placed and make above a certain threshold. They're removing the risk for you and you pay for that once you're able.

I agree that the salary estimate is high, and I wouldn't hire a remote junior dev, but still; you're paying nothing up front and they're handing you $2k / month.


Any thoughts about making the client-side "seed" saveable?

Would love to be able to save/replay/share sections that I really enjoyed (e.g. bookmark the seed(s) + offset/range).


Caution: this just hung Firefox for a ~30s and then my MBP rebooted.


Same here.


Humans are not always the consumer of error output. Distinct error codes simplify parsing and eliminate ambiguity.

It also makes it easier for developers look up a specific error in the documentation, assuming it's been documented.


It's also easier for a (technical) user to reference they got error 1018 than copy & paste "An index signature parameter cannot have an accessibility modifier." Especially in titles and when referencing it multiple times within a body of text.


How does an error code make it easier to look up an error? The workflow is either “get error, google it”, or “get errorcode google it”. In both cases the docs will be the top hit.

If we where talking 20 years ago I might agree, but I really can’t see the argument with todays tooling.


Updates can improve on the error messages, making them more clear, the error code does not change but the message changes.

Also many times the error message is interpolated with your specific details like

"Syntax error at line 123 in file /home/user/myfile , symbol X is not allowed here" this is a silly example but often enough when i google this errors I have to first strip out my data from them.


Googling the text of an error often finds lots of unrelated results. So no, the docs might not be the top hit.


All errors are google-able?


There's a good Planet Money podcast all about the Jones Act: https://www.npr.org/sections/money/2016/08/05/488869138/epis...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: