x0hm

22 ms·

31.
by x0hm 7y ago
http://www.github.com
32.
by x0hm 7y ago
Mostly because the way we approach OOP is wrong, and so developers - who were taught to write software as "instructions given to a machine" (i.e., procedurally) - don't fully understand the paradigm. That leads to the belief
33.
by x0hm 7y ago
how dare you try to create value for your customers by engaging with them unbelievable
34.
by x0hm 7y ago
Whenever I feel like an impostor, I like to go to github and look at other people's code. Turns out, most of us are pretty bad at this job. You're a human with a cool brain and an incredible capacity for learning. Anything you don
35.
by x0hm 7y ago
> I find nothing interesting to me > I'm a real generalist with a lot of interests You say you have a lot of interests and aptitudes, but your entire post is about how disinterested and not good you are. Maybe you should identify
36.
by x0hm 7y ago
Ideally, the team. In practice, management and above.
37.
by x0hm 7y ago
'Most productive individual' 'Most productive team' Ahhh, developer poison.
38.
by x0hm 7y ago
It's the minimum set of requirements to have a fully functional, usable product. The MVP has to be customer-ready, so it has to be as minimally feature-complete as possible.
39.
by x0hm 7y ago
> Doesn't know how to write OO code. > Calls OO cancer.
40.
by x0hm 8y ago
The headline could have stopped at "Programmers take the easy way out"
41.
by x0hm 8y ago
Gross
42.
by x0hm 8y ago
You tell us.
43.
by x0hm 8y ago
What about a projector?
44.
by x0hm 8y ago
Apprenticeship - you'll learn exponentially more working alongside someone.
45.
by x0hm 8y ago
FTL
46.
by x0hm 8y ago
I'm 4 months into a new job. I was a C# dev. Now I am a Java dev. The hardest part isn't the language. Once you know a couple, picking up a language is easy. The hardest part is learning new frameworks and new tool chains. Intervi
47.
by x0hm 8y ago
When you have less code, you have less code to write, you have less code to read, you have less code to understand, you have less bugs, you have a smaller team, or, for the same budget, you have more time to do new features and bug fixes,
48.
by x0hm 8y ago
Again, those frameworks are written in php. They are not php. You're trying to apply the problems of a framework/app to a language itself.
49.
by x0hm 8y ago
If "people use it wrong" was a good excuse not to use a language, I can say that every language I've worked with is bad.
50.
by x0hm 8y ago
Wordpress is written in PHP. Wordpress is not PHP.
51.
by x0hm 8y ago
Build yourself a command line app that saves your tasks. Start small and iterate on it until it's what you need.
52.
by x0hm 8y ago
Yes. Any language in which you can be productive is worth investing time in. And since this question is stemming from something bigger: Please don't listen to the development community when it comes to things like "which language
53.
by x0hm 8y ago
If you don't trust a handshake and a "we'll discuss money when we start making it", I'd definitely get something in writing. But don't just write something and call it good. If you're serious about it, con
54.
by x0hm 8y ago
I'm 32, didn't go to college, and have been a programmer since I was 17. I suck at math. https://teachyourselfcs.com/ is a good resource, and they recommend (and have a link to the pdf for) Mathematics for Compute
55.
by x0hm 8y ago
If you're going to made broad assumptions, then using any framework is technical debt. Also, if a developer told me that using PHP for a project causes technical debt, I would fire him.
56.
by x0hm 8y ago
Because documentation is boring.
57.
by x0hm 8y ago
It's 2018 and people still use Joomla. TIL
58.
by x0hm 8y ago
Developers who move to management are bad developers.
59.
by x0hm 8y ago
Same - send us some info so we can do this too.
60.
by x0hm 8y ago
Taking care to do your craft well is never a waste of time.

More ›