breeny592

8 ms·

31.
by breeny592 9y ago
>Another JIRA flaw: highly formalized process is usually a hindrance, especially considering who in your organization invents, applies and benefits from process. Hint: middle managers. This just reads as someone who hasn't had to ac
32.
by breeny592 9y ago
It's still used in quite a lot of enterprise production applications, would say it's on the decline but no where near dead.
33.
by breeny592 9y ago
I think pacala's point still stands - if you rent hardware, there is still a larger effort involved around running scalable services (DR, auto-scaling/load balancing, deployments etc). If you rent hardware, you likely will need a
34.
by breeny592 9y ago
Context: I work on a large CMS powered site We have a company wide rule of no IDs in styles - we actually lint for them. As a front end team, we can't be certain that there will only ever be one of a component on a page at a time. Some
35.
by breeny592 9y ago
And it does a poor job in that regard too. - CSS modules promote more re-use if structured correctly - BEM and the like exist to do the literal opposite, to isolate styles to minimise regression and site wide issues at scale. - Visual consi
36.
by breeny592 9y ago
Some developers at my workplace are very resistant to change ("why learn ES6 when ES5 works fine" is a classic line we used to get). Trying to move onto a module based CSS approach (whether thats CSS modules, CSS-in-JS etc), and l
37.
by breeny592 9y ago
CSS modules is pretty clean, but disagree that JSS/styled-components are "cringeworthy". They're very powerful, especially when combined with React component props - i.e. let's say when a component has a prop active
38.
by breeny592 9y ago
Among many other solutions as well (like JSS). CSS-in-JS !== inline styles, at all, yet seems to be a rallying call for people who fear "something different".
39.
by breeny592 9y ago
That's what got me with it - the author states as if it's fact that best practice for CSS-in-JS is copy and paste, but I've never seen anyone advocate for that. Especially with Webpack etc, it's trivial to just import JS
40.
by breeny592 9y ago
Except to their own companies bottom line, generating millions in revenue? Releasing less often is a way to guarantee that bigger bugs will get through at some point, requiring hotfixes etc. The more you release, the higher quality releases
41.
by breeny592 9y ago
I find a big thing too is building up that mindset of always roll forward. Bug in production means next production build will fix said bug. No hotfixing to say the release is done etc. Completely agree that from a tech side there is no excu
42.
by breeny592 9y ago
Exactly - releasing is the easiest part of the process. A lot of orgs don't have continuous deployment because of reasons such as: - they don't have a good enough automated testing suite (or at least don't trust it fully), an
43.
by breeny592 9y ago
On a more macro scale, places I've worked have had people set goals across a longer period of time (3, 6, 12 months) that are measurable and have direct actions. I've found those to be quite good for myself as a developer as a day
44.
by breeny592 9y ago
"The cull", aka death from alcohol poisoning on NYE.
45.
by breeny592 9y ago
One of the most valuable skills I always try to teach junior (and sometimes not so junior) developers is not only how to abstract your problems (as the author points out in this article), but also how to follow a related chain. For instance
46.
by breeny592 9y ago
HowToBasic's guide to creating a Todo MVC React App 1. Open editor of choice 2. Slap the keyboard with a raw fish 3. Crack a raw egg on the screen
47.
by breeny592 9y ago
Separation of concerns != splitting logic from presentation. SoC comes from MV* architectural patterns. In real world front end applications, people who separate based on the file extension often end up creating JS files that breach SoC - t
48.
by breeny592 9y ago
Different strokes for different folks - my thought to that is pretty much that I don't really care what the result will be on the grand scheme, but more specifically isolated nodes and how they will interact with my model/data etc
49.
by breeny592 9y ago
Not to mention that if a section of markup gets too big, you can break that down to it's own method that returns tiny snippets so you can have really simple methods that end up creating the more complex end result i.e. _renderXOrY = (t
50.
by breeny592 9y ago
Checklist: - [x] Working in a consultancy - [x] Government client - [x] No direct communication with the users - [x] Waterfall project - [x] Short timeline - [x] Understaffed - [ ] Clear requirements Was definitely delivered on time and on
51.
by breeny592 9y ago
I'm confused on how an employer is not a "jobs program" - they literally employee people, and are responsible for that employees growth and career opportunities (if they value having low staff turnover and achieving better ou
52.
by breeny592 9y ago
I think it's a pretty bad false equivalence to liken physical sports to ability in the workplace, purely because one is specifically _the peak of human ability_ and the other is outcome driven. Taking your example of say, sprinting - t
53.
by breeny592 9y ago
It's bit different if you work with them (or in the same company). Linus has a certain, style, to put it nicely, but in the broader open source community. The key point is that this is likely the first time these two individuals had co
54.
by breeny592 9y ago
I would argue that the world has moved on to expect more open APIs - events like Google I/O and event Facebook F8 reveal quite open technologies that encourage open innovation in a web context. WWDC, at least from a software side, is t
55.
by breeny592 9y ago
I'd propose a hypothesis that yes it does, for a couple of main reasons: 1. Concentration of job market - a lot of industries only exist (or at least, in a large enough volume) in the larger cities (e.g. financial services, tech). I&#x
56.
by breeny592 9y ago
Anything where the customer and their real needs is not the focus. If a product places sales or money above the people it's dealing with, I'm not interested. Ironically, I now work for a bank - just luckily a bank that has very go
57.
by breeny592 9y ago
I think you left the /s off your comment
58.
by breeny592 10y ago
Not to mention it's something that when making custom components etc., you will be able to do if so desired. A good component structure and composition enables you to handle Android versus iOS, but still have a large amount of sharing
59.
by breeny592 10y ago
A note on the require issue: this makes sense if you think of requiring as it's compiled equal - importing. You can't dynamically import dependencies - so if you're wanting to load JSON dynamically you should be using other m
60.
by breeny592 10y ago
Someone in the comments of the post suggested the same thing - people who criticise React (or any framework really) of "taking too long to set up" says one of two things to me: 1: they're too picky in what they want to use g

More ›